-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BIDS Formatting #66
Comments
MF thoughts:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: translationalneuromodeling/tapas#36
Guidelines: https://bids.neuroimaging.io/bids_spec.pdf (section 8.6, page 43)
The text was updated successfully, but these errors were encountered: