You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to describe what these events actually mean. BIDS suggests to store this information as trial_type levels inside events.json (example copied from the BIDS spec):
{
"trial_type": {
"LongName": "Event category",
"Description": "Indicator of type of action that is expected",
"Levels": {
"start": "A red square is displayed to indicate starting",
"stop": "A blue square is displayed to indicate stopping"
}
}
}
Currently, MNE-BIDS doesn't provide an easy way to write this data.
Describe your solution
Allow users to pass a mapping from event names (trial_type levels) to an event description. I imagine something like:
event_name_to_code_map= {
"fixation": 110,
"cue/low": 120,
...
}
event_name_to_description_map= {
"fixation": "A fixation cross displayed in the center of the screen.",
"cue/low": "A visual cue indicating low intensity."
}
write_raw_bids(
...,
event_id=event_name_to_code_map, # existing paramevent_descr=event_name_to_description_map# new param
)
Describe possible alternatives
Users can update the JSON file manually after calling write_raw_bids(). However, this is cumbersome and error-prone.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
I'm storing data for an ERP experiment. We have events like the following:
I would like to describe what these events actually mean. BIDS suggests to store this information as
trial_type
levels insideevents.json
(example copied from the BIDS spec):Currently, MNE-BIDS doesn't provide an easy way to write this data.
Describe your solution
Allow users to pass a mapping from event names (trial_type levels) to an event description. I imagine something like:
Describe possible alternatives
Users can update the JSON file manually after calling
write_raw_bids()
. However, this is cumbersome and error-prone.Additional context
No response
The text was updated successfully, but these errors were encountered: