There existed a bug until recently (fixed on Dec 6, 2018) when reading CTF recordings with a headshape .pos file that would introduce an error in MEG coil orientations on the order of 1%. These errors would propagate to the forward and inverse solutions and thus affect any results in source space.

For users currently analyzing data where the bug is present, we created a process (fixed Feb 15, 2019) that can reset a channel file while keeping existing projectors and history, to avoid having to restart analysis from zero. This short tutorial shows how to fix data already read and pre-processed in Brainstorm.

If you choose to proceed with fixing your data, understand that all existing data including and past computing a forward model will have to be discarded and recomputed.

First, make sure your copy of Brainstorm is up to date.

When manually selecting files and folders, raw and imported data cannot be processed at the same time, so if you wish to keep some imported data as well, you can either process them separately, or use the process File > Select files: recordings. The latter option allows you to process your entire protocol at once.

[file selection pic]

The process will work best if the original raw data is still available in the same location as when it was first read into Brainstorm. If this is no longer the case and the raw files cannot be put back in their original location for some reason, the process will prompt you to select each distinct channel file once manually. This is another reason to prefer processing all files at once since many raw and imported files can point to the same original channel file.

Add the Standardize > Adjust coordinate system process to the pipeline and select the first option: Reset coordinates... Also specify the file format.

[pic]

The other options are described in the Head Motion tutorial. While you can select other options like Adjust head position and Refine MRI coregistration, note that if a file fails these extra steps (e.g. because of missing head coil channels or head points file - which would be the case for a noise recording), then the channel file is not modified at all, even if the reset step would have succeeded on its own. It is thus important to pay attention to errors in the pipeline report to ensure all files were fixed.