Coregistration before data import

Discussions
,
1

Greetings,

We had a short clarification question regarding the order of certain steps in our MEG data pipeline. Typically we have performed the coregistration step after importing the raw data into the database. The idea being that this ensures that the correct coregistration information is attached to the imported, epoched data on which we perform beamform imaging.

We are instead considering implementing this coregistration step prior to importing the data. When testing this, it seems the correct coregistration information (i.e., the spatial transformations on headpoints and sensor locations) is transfered from the raw to imported data folder. The reason for this change is to make sure that the coregistration data in maintained in the event we need to delete the imported folder and re-import the raw data. In other words, we will edit MRI registration to the “channel” file in the raw folder, and those edits will carry over to the “channel” file in the imported folder.

Given the way that importing of data works, does this plan sound reasonable? Will all the MRI registration and all other information be present in the channel file when beamform imaging our imported data?

2

Hello @natepetro,

Here I'm not sure if "...after importing the raw data into the database." means:

  1. Corregistration is performed on the raw data () which has been linked to the database (with the option Review raw file), or
  2. Corregistration is performed on the imported data () which has been imported (with the option ** Import MEG/EEG**).

The typical Brainstorm workflow is:

  1. Import anatomy, set fiducials
  2. Review raw data (link raw data to database)
  3. Corregsitration on the linked raw data
  4. Import epochs from linked raw data

In this case the corregistration transformation computed in the Step 3 are copied to imported epochs in Step 4.

More info here:
https://neuroimage.usc.edu/brainstorm/Tutorials/ChannelFile#Review_vs_Import