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 noticed that .tsv data without headers (for example this one) lead to warning [Code 82] CUSTOM_COLUMN_WITHOUT_DESCRIPTION
(see this PR for context).
A few modalities including motion (currently a BEP) and physio use these headerless tsvs as data format and it would make sense to remove this warning for files that end with *_motion.tsv or *_physio.tsv.
Could you have a look into this @rwblair? According to the PR comments thread linked above this shouldn't be a blocking issue for progressing with motion community review.
The text was updated successfully, but these errors were encountered:
I guess we should think through how this interacts with the schema. Right now, .tsv files have in-file headers, and .tsv.gz files have in-sidecar headers (sidecar.columns). Looking at the example above, it would seem to be associations.channels.name.
However, that assumes that this rule would be interpreted before any other validation that might need to associate data with headers or know the number of columns. Another approach could be to add new definitions:
Hi everyone,
I noticed that .tsv data without headers (for example this one) lead to warning [Code 82] CUSTOM_COLUMN_WITHOUT_DESCRIPTION
(see this PR for context).
A few modalities including motion (currently a BEP) and physio use these headerless tsvs as data format and it would make sense to remove this warning for files that end with *_motion.tsv or *_physio.tsv.
Could you have a look into this @rwblair? According to the PR comments thread linked above this shouldn't be a blocking issue for progressing with motion community review.
The text was updated successfully, but these errors were encountered: