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
In the BIDS specification, column headers for .tsv files are not commented out, they are the first non-comment line in the file. This means that if fed to e.g. MR::load_matrix(), that function will fail.
What would need to happen is for, upon receiving an Exception (ideally one specific to receipt of non-numerical data, but only on performance grounds), the parser should make a second attempt at parsing the file, but stashing the contents of the first non-empty line. If parsing the remaining content of the file as numerical data works, then the contents of that first line should be added to the KeyValues instance under some prescribed key.
Unsure what should occur if the data are accessed via load_vector(), the data are stored specifically as a column vector, and the first row is non-numeric... should that be interpreted as a column label, or an error?
The text was updated successfully, but these errors were encountered:
Reporting based on bids-standard/bids-specification#352.
In the BIDS specification, column headers for
.tsv
files are not commented out, they are the first non-comment line in the file. This means that if fed to e.g.MR::load_matrix()
, that function will fail.What would need to happen is for, upon receiving an
Exception
(ideally one specific to receipt of non-numerical data, but only on performance grounds), the parser should make a second attempt at parsing the file, but stashing the contents of the first non-empty line. If parsing the remaining content of the file as numerical data works, then the contents of that first line should be added to theKeyValues
instance under some prescribed key.Unsure what should occur if the data are accessed via
load_vector()
, the data are stored specifically as a column vector, and the first row is non-numeric... should that be interpreted as a column label, or an error?The text was updated successfully, but these errors were encountered: