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 tried running csv2nidm on this tsv file and got the following output:
Variable participant_id age sex handedness automatically mapped to participant/subject idenfier
Label: participant_id age sex handedness
Description: subject/participant identifier
Source Variable: participant_id age sex handedness
---------------------------------------------------------------------------------------
Creating NIDM file...
1: participant_id age sex handedness
Please select the subject ID field from the list above:
which is not what I want (it's representing all column headers as a single column), but when I converted the file to a csv, csv2nidm worked as expected.
According to the bids specification, phenotypic data should be represented as a tsv, so I think the default behavior of csv2nidm should handle a tsv.
To change this behavior, I believe all that is needed is changing this line
or maybe some additional logic to try to guess the appropriate separator (or add a command-line option),
Depending on how important it is to not make backward-incompatible changes.
The text was updated successfully, but these errors were encountered:
dbkeator
added a commit
to dbkeator/PyNIDM
that referenced
this issue
Mar 15, 2021
I tried running
csv2nidm
on this tsv file and got the following output:which is not what I want (it's representing all column headers as a single column), but when I converted the file to a csv,
csv2nidm
worked as expected.According to the bids specification, phenotypic data should be represented as a tsv, so I think the default behavior of
csv2nidm
should handle a tsv.To change this behavior, I believe all that is needed is changing this line
PyNIDM/nidm/experiment/tools/csv2nidm.py
Line 104 in 2f48a8b
to:
or maybe some additional logic to try to guess the appropriate separator (or add a command-line option),
Depending on how important it is to not make backward-incompatible changes.
The text was updated successfully, but these errors were encountered: