BIDS Naming Convention

Hi all,

I am having some difficulties with how to proceed with organising a data set. At the first time point we have participants come in for an evening fMRI, they then have an overnight sleep study where EEG data is collected, followed by a subsequent morning fMRI. Participants also complete a week of at-home data collection prior to the scans and sleep study. Participants repeat this process at subsequent time points.

Initially we were going to store all of this data under ses-1 but found that it was difficult to distinguish the morning and evening fMRI scans. We then considered storing the fMRI data in seperate ses-1am and ses-1pm subfolders, but I don’t think having session subfolders is BIDS-compatible.

What would be the best way to organise this data (PM MRI, overnight eeg, AM MRI), while keeping it all within the same session folder, according to BIDS. Thank you!

Hi @restless, and welcome to neurostars!

True, BIDS does not support this.

I would not recommend putting these in the same session. Typically a “session” is thought of as a single continuous stint in a scanner (not counting things like short breaks or head readjustments).

I would have ses-1PM, that contains func and eeg folders, and a ses-1AM that contains the morning MRI.

Best,
Steven

Hi Steven,

Thank you so much for your help!

My only concern with this is that the EEG is a separate session to the MRI scan. (Participants undergo the EEG during an overnight sleep study. The MRI scans occur a few hours before and after the participant goes to sleep.

Furthermore how would you suggest labelling the folder for the data (including from portable EEGs) attained from the week immediately preceding the scan and sleep study. Our protocol considers this entire collection of testing (at-home assessment, MRI scans, and sleep study) as a single time point.

Thank you again for your help!

Hi @restless,

Then you can have a ses-1EEG, or something like that.

Maybe ses-preEEG / ses-preMRI etc…? As long as you use some kind of intuitive naming scheme that is documented in your README, you should be fine.

Best,
Steven

Thank you so much Steven!