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, CuBIDS has the entities that may exist in output filenames hardcoded. If we instead choose to limit CuBIDS to the acq entity (which is how we label variants), then we can just use whatever entities were in the original filenames.
This will primarily affect CuBIDS.change_filename. I'm not sure how it would impact the key/parameter/acquisition group grouping process.
Additional details
Simpler code, more generalizability.
The text was updated successfully, but these errors were encountered:
Summary
Currently, CuBIDS has the entities that may exist in output filenames hardcoded. If we instead choose to limit CuBIDS to the
acq
entity (which is how we label variants), then we can just use whatever entities were in the original filenames.This will primarily affect
CuBIDS.change_filename
. I'm not sure how it would impact the key/parameter/acquisition group grouping process.Additional details
Simpler code, more generalizability.
The text was updated successfully, but these errors were encountered: