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
currently, cpp_ptb is making (maybe this issue should be raised in cpp_bids repo?) bold.json and it is putting so much information that is not compatible with MRIQC. this bold.json should be kept in source, it is not for raw folder.
However, the users are not informed about this decision. Here is an example, I took some data from a colleague to run MRIQC on their dataset. Now I have to make MRIQC compatible bold.json manually because the user does not have compatible bold.json files, and had no clue that this is not raw folder, and they should be using "conversion" bold.json files. That is another issue, not every user is using good converters which are building MRIQC-compatible bold.json files.
I suspect if we wanted to run fmriprep, that could be problematic with these bold.json files as well?
A suggestion would be keeping these super informative bold.json, but with another label, and creating MRIQC bold.json for being more compatible with these toolboxes. What do you think?
Unclear documentation
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
New feature
currently, cpp_ptb is making (maybe this issue should be raised in cpp_bids repo?) bold.json and it is putting so much information that is not compatible with MRIQC. this bold.json should be kept in source, it is not for raw folder.
However, the users are not informed about this decision. Here is an example, I took some data from a colleague to run MRIQC on their dataset. Now I have to make MRIQC compatible bold.json manually because the user does not have compatible bold.json files, and had no clue that this is not raw folder, and they should be using "conversion" bold.json files. That is another issue, not every user is using good converters which are building MRIQC-compatible bold.json files.
I suspect if we wanted to run fmriprep, that could be problematic with these bold.json files as well?
A suggestion would be keeping these super informative bold.json, but with another label, and creating MRIQC bold.json for being more compatible with these toolboxes. What do you think?
Unclear documentation
No response
The text was updated successfully, but these errors were encountered: