[ENH] BEP 020 Eye Tracking

[mszinte]

Important

This BEP is under community review from September 29 - October 10, 2025. Please participate at #2218.

Tip

HTML preview of this BEP

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 April 3rd 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)

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]

Just a thought on an alternative to ForeignIndexColumn:

  "OnsetSource": "timestamp",

  "OnsetSource": "n/a",

I like this. Do we need a third one, like

"OnsetSource": "index_physio",

to discriminate between totally random onset sources and referencing timestamps in physio.tsv.gz?

[effigies]

I like this. Do we need a third one, like

"OnsetSource": "index_physio",

to discriminate between totally random onset sources and referencing timestamps in physio.tsv.gz?

I don't think so? n/a indicates indices in physio.tsv.gz, timestamp indicates timestamp values in physio.tsv.gz, and there's no point in encoding totally random.

Outdated

[effigies]

Some more foreignindexcolumns

[effigies]

I have opened mszinte#12 to address the two comments in @yarikoptic's review. It is easily addressed in the schema with no validator changes necessary.

@gbezold1 @julia-pfarr @mszinte Would you have a look?