Open monique2208 opened 1 week ago
The place to fix this will be in the schema:
I would add the following selector:
- (datatype != "meg" || entities.subject != "emptyroom")
Rather than matching on task-noise
, catching the meg/sub-emptyroom
seems better targeted to this case.
Would you be willing to open a PR over on the spec?
I am getting a warning EVENTS_TSV_MISSING about the noise task that is part of empty room data for an meg dataset. Since this is explicitly how this task should be labelled according to the specification, should there not be an exception for
noise
as there is forrest
?we are actually upgrading this warning to an error for our system, is there a way to avoid this error for the noise task specifically through configuration?