Remi Gau

@michellewang I need to make sure the tests pass for this but I would not mind you having a review at this at some point because you have been changing...

hey @davidreydellet was there supposed to be a link to some data and code ?

Not 100% sure the warning and the errors are related. Can you tell us what function / line the warning is happening at? It seems to be more related to...

MATLAB is pretty strict as to what can be a valid variable or field name: can be an interoperability issue when creating tsv headers or JSON fieldnames that may work...

Relates to https://github.com/bids-standard/bids-specification/issues/1487 Unless I am mistaken enforcing this would depend on updating the schema (see https://github.com/bids-standard/bids-specification/pull/1492) for the deno based validator. I doubt the legacy validator will enforce this.

I think we had added this section in the spec, no? https://bids-specification.readthedocs.io/en/stable/common-principles.html#uniqueness-of-data-files But I need to get back to finishing the schema pr.

I tried to make sure that the tests of atlasreader would run with latest versions of its dependencies and so far this was not successful. Given I am not sure...

The atlasreader package was updated and should now run as expected so it would probably be worth to mention it in the doc and close this issue.

Kind of agreeing that the lack of definition / operationalization of "virtually" is a bit of a problem. I think that people may organize their dataset differently depending on what...

the participant.tsv is not formatted according to BIDS (participant_id should be `sub-something`), so I don't think this is a validator issue.