Fiducial/headmodel handling. about opm HOT 9 CLOSED

Agree, it's a mess, fix if you can. My only wish is that there is no matlabbatch inside of the code.

from opm.

Okay, so just reporting back on the behaviour of the code. I have a test dataset when the sensors are in a completely different space to the MRI (a possibility if its a template brain or perhaps a Cerca dataset).

Here its failed to align as the default behaviour is to assume the transformation between the MRI and the sensors is identity when no explicit description of the sensor-space fiducials are supplied (i,e from coordsystem json). So far so good.

Using the coordsystem json which has the sensor-space fiducials, In this case as the antomical fields in coordsystem are optional it will try and use the derivved coordinates from the MRI. In the case of a coordsystem json having MRI landmarks supplied it will use those instead. Alignment works.,

Also please to say its still smart enough to use digitised headpoints (from a "polhemus") if supplied when doing a registration. In the case below its the registering to the template brain.

from opm.

cool stuff George, maybe a warning needs to be thrown for first case

from opm.

did not mean to close.

from opm.

Agreed with the warning. Once I've finessed the last bugs I'll trigger a pull request.

from opm.

#7

from opm.

Think you need a final D.save after the headmodel stage, but maybe this is my superstition

from opm.

Thats a good point, I'll chuck that in for safety,

from opm.

Right #8 should be it, but no rush to pull now, can do tomorrow. Toot toot!

from opm.