Allowing for raw files to be automatically relocated about mne-bids HOT 9 CLOSED

That is correct. Although one of the visions/goals of mne-bids was to nudge users towards the fiffile format. The MEG-BIDS discussions didn't lead to an accepted file format. However, the more file formats you have, the more you move away from standards :-) cc @teonbrooks

from mne-bids.

The raw_to_bids function as it stands doesn't produce the folder required to place the raw data in (but can be easily modified to do so).

I am not sure I follow. Can you elaborate? raw_to_bids does produce the folder to put your BIDS compatible data.

Regarding the notes, you are correct. Do you have time to make a PR?

from mne-bids.

When I ran the script it would produce the file structure like "sub-control01/ses-01/meg/" within which the .tsv and some .json files reside, however there should be a subsequent subfolder within this folder with the same title as the sidecar .json. so in the example given in the specification you would have a further subfolder within the above directory "~/sub-control01_ses-001_task-rest_run-01_meg/" where the raw data goes.

And yep, I can do a PR.

from mne-bids.

however there should be a subsequent subfolder within this folder with the same title as the sidecar .json. so in the example given in the specification you would have a further subfolder within the above directory "~/sub-control01_ses-001_task-rest_run-01_meg/" where the raw data goes.

okay I did not understand this before, but I guess it is also something KIT specific? Feel free to make a PR

from mne-bids.

I think there was some confusion on my end. The bids specification is a little bit un-unified on how the raw files should be located. The general example doesn't always match the examples for specific MEG systems. If you look at appendix VI (section 16) of the bids specification you can see that some systems are recommended to have a sub folder for the raw data, while others (eg Elekta) store the raw data in the main meg folder.
I will try consolidate the info in the specification into a PR to fix it.
I will probably include the raw file path in that PR too since the two will be linked.

from mne-bids.

If you look at appendix VI (section 16) of the bids specification you can see that some systems are recommended to have a sub folder for the raw data, while others (eg Elekta) store the raw data in the main meg folder.

The reason for this is that for some MEG devices, the info for a single recording is spread out between different files. However, in the case of Elekta it is contained in a single *.fif file

from mne-bids.

Yep, I understand that now, but we will need to handle that correctly as it isn't handled by mne-bids at the moment. Currently only .fif files will be copied to the correct location. Any other raw files will just be ignored.

from mne-bids.

@monkeyman192 this is fixed I think? should we close this issue?

from mne-bids.

Yep, I think this got included in a PR at some point :)

from mne-bids.