[ENH] BEP 020 Eye Tracking

[mszinte]

Here is the specifications of the BEP 020 about eye tracking.

• it follows the main discussion initiated on a google document.
• it includes the different modification the group of maintainers suggested to us during our zoom meeting.
• it includes the macros as used in other modality specific extensions
• it includes links toward dataset examples.

Note

We meet regularly and everyone is welcome :
Next meeting January 23rd 2025 4pm UTC (EST 11am, PST 8am, CET 5pm, GMT 4pm) on zoom.
Note that if you consider joining but this time or day doesn't suits you, reach me (@mszinte) and I will arrange another appointment.

Notes of last meeting

Chat and discussions also happening on matrix

We are currently drafing a companion paper for this BEP, feel free to participate (GoogleDoc)

Tip

HTML preview of this BEP

Issues for:

• general todo list: To do list mszinte/bids-specification#1
• conversion discussion: Converter roadmap mszinte/bids-specification#4
• list datasets: eyetracking dataset examples mszinte/bids-specification#3

---

• implement macros
  • for filename templates ?
  • for examples ?
  • for metadata table
• add contributors to the wiki (so they can be added to the contributors page)
• end docmentation
• update examples
• update validator
• update list of contributors via the github wiki

[sappelhoff]

(NOTE: I'll cross-post this message across several BEP threads)

Hi there, just a quick notification that we have just merged #918 and it may be interesting to look at the implications for this BEP.

We are introducing "BIDS URIs", which unify the way we refer to and point to files in BIDS datasets (as opposed to "dataset-relative" or "subject-relative" or "file-relative" links).

If the diff and discussion in the PR is unclear, you can also read the rendered version: https://bids-specification.readthedocs.io/en/latest/02-common-principles.html#bids-uri

Perhaps there are things in the BEP that need adjusting now, but perhaps also not -- in any case it's good to be aware of this new feature!

Let me know if there are any questions, comments, or concerns.

[julia-pfarr]

Hi all - I lost track of the meeting schedule. Is there one scheduled in the next month?

Not yet! Please fill out to find a time for the next meeting: https://doodle.com/meeting/participate/id/b2OzP3jd. Times should be displayed in your time zone. I tried to choose times that are manageable in all the time zones.

[oesteban]

I would make this an enum and allow "custom" so the user can specify a system that is not captured by the enum.

[mszinte]

I agree with it.

[oesteban]

For some reason I can't see a comment where I would swear I followed up on this and asked @Remi-Gau to finalize this 👀

I also tagged @effigies, @tsalo and @rwblair for support about the schema.

I think I was proposing something of the sort of:

Suggested change

	StimulusPresentation_for_eyetracking:
	selectors:
	- suffix == "events"
	- intersects([suffix], ["eyetrack"])
	fields:
	StimulusPresentation.ScreenDistance: required
	StimulusPresentation.ScreenOrigin: required
	StimulusPresentation.ScreenRefreshRate: recommended
	StimulusPresentation.ScreenResolution: required
	StimulusPresentation.ScreenSize: required
	StimulusPresentation_for_eyetracking:
	selectors:
	- suffix == "events"
	- (suffix == "physio").PhysioType == "eyetrack"
	fields:
	StimulusPresentation.ScreenDistance: required
	StimulusPresentation.ScreenOrigin: required
	StimulusPresentation.ScreenRefreshRate: recommended
	StimulusPresentation.ScreenResolution: required
	StimulusPresentation.ScreenSize: required

The idea is that, for those events files matching tasks with physio files AND those physio files have the metadata PhysioType=eyetrack, then make these StimulusPresentation fields REQUIRED.

[oesteban]

Moved to bids-standard/bids-validator#143

[oesteban]

@mszinte (re: 77fd567) It'd probably best to point all the examples to the BIDS-Examples repo bids-standard/bids-examples#478. The main reason is that the BIDS-Examples PR is using our version of the schema (and therefore, the .bidsignore trick is not negating the intent).