MalloryJfeldman
commented
5 years ago MF thoughts:
- Really designed for LARGE files stored in conjunction with imaging files.
- Really not optimized for in-lab data or the kinds of analyses/software we use with these data
- Love the idea of "strict naming conventions" which enable sharing & understanding. Though these naming conventions are not well defined for physio data.
- I think if we wanted to use these, we would have to explore file types, additional naming conventions, and other optimizations to facilitate storing and sharing of both in-lab and in-scanner physio.
purpose: minimize curation (helping researchers not directly involved in data collection to understand and work with data); error reduction (attributed to misunderstanding meaning of data); optimization for use with data analysis software (via metadata); development of automated tools. BIDS in its current formed is designed to standardize and describe raw data.
File names are formed with a series of key-values and end with a file type, where keys and file types are predefined, and values are chosen by the user.
The standard provides data dictionaries and strict naming conventions for structural, diffusion, and functional MRI data as well as accompanying behavioral and physiological data.
Currently, physiological recordings such as cardiac and respiratory signals (and other continuous measures) can be specified using two files:
Naming conventions specify cardiac, respiratory, and trigger data.
All physio data uses the _physio suffix, and signals related to the stimulus should use _stim suffix.
Example file names:
sub-001_ses-01_task-tsst_physio.tsv.gz sub-001_ses-01_task-tsst_physio.json
Example Data: https://github.com/translationalneuromodeling/tapas/issues/36 Guidelines: https://bids.neuroimaging.io/bids_spec.pdf (section 8.6, page 43)