[ENH] BEP 020 Eye Tracking #1128
Conversation
correction of text
|
(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. |
for more information, see https://pre-commit.ci
src/schema/objects/metadata.yaml
Outdated
| EncodingTechnique: | ||
| name: EncodingTechnique | ||
| display_name: Encoding Technique | ||
| description: | | ||
| The encoding technique used during readout. | ||
| For example, `"Cartesian"`, `"EPSI"`, `"Spiral"`, | ||
| or `"Density-weighted concentric ring trajectory"`. | ||
| type: string |
There was a problem hiding this comment.
typo due to merge conflict resolution
|
|
We are eager to release our HBN dataset (2000+ subjects with eye tracking). I have provided several candidates on another thread matching the proposed format. When can we expect the format finalized? Tx |
To my opinion the BEP is ready, we are finishing examples and testing deeply our converter. I would then suggest you to take it as it is and keep an eye on this thread in case some reviewer makes important changes when we will open it to review. Best, |
| name: pupil_size | ||
| display_name: Pupil size | ||
| description: | | ||
| Pupil size or area of the recorded eye, in the |
There was a problem hiding this comment.
Are we recording the particular type of pupil size that's being recorded here ('diameter' v/s 'area')?
The data that comes out of Eyelink is always in 'arbitrary units' (Eyelink documentation: page 106, 4.4.3) and the actual data type is stored in the settings (Eyelink documentation: page 25 'Pupil Size Data').
There was a problem hiding this comment.
This could be another settings, do you feel like adding another entry to the table called something like pupil_type ?
|
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. |
| display_name: Coordinate System of the Gaze Position | ||
| description: | | ||
| Coordinate system of the gaze position recordings. | ||
| Generally eye-tracker are set to use `"gaze-on-screen"` coordinate system but you may use |
There was a problem hiding this comment.
| Generally eye-tracker are set to use `"gaze-on-screen"` coordinate system but you may use | |
| Generally eye-trackers are set to use `"gaze-on-screen"` coordinate system, but you may use |
| Coordinate system of the gaze position recordings. | ||
| Generally eye-tracker are set to use `"gaze-on-screen"` coordinate system but you may use | ||
| `"eye-in-head"` or `"gaze-in-world"` or other alternatives of your choice. | ||
| If you use the standard `"gaze-on-screen"`, it is RECOMMENDED to use this |
There was a problem hiding this comment.
I would make this an enum and allow "custom" so the user can specify a system that is not captured by the enum.
| selectors: | ||
| - suffix == "physio" | ||
| fields: | ||
| EnvironmentCoordinates: required |
There was a problem hiding this comment.
This one is very problematic if REQUIRED, what happens when "SampleCoordinateSystem" is not "gaze-on-screen"?
Does this make sense for "eye-in-head" or "gaze-in-world"?
Co-authored-by: Scott Huberty <[email protected]>
Here is the specifications of the BEP 020 about eye tracking.
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
Tip
HTML preview of this BEP
Issues for: