Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

affine transformation matrix to map MEG space into defaced MRI #752

Closed
guiomar opened this issue Mar 10, 2021 · 2 comments
Closed

affine transformation matrix to map MEG space into defaced MRI #752

guiomar opened this issue Mar 10, 2021 · 2 comments

Comments

@guiomar
Copy link
Collaborator

guiomar commented Mar 10, 2021

Hi!

Talking to @RikHenson, we were wondering if there's a specific place in the specs to store the affine transformation matrix that maps MEG space to defaced MRI. I suggested to store the HeadCoilCoordinates, AnatomicalLandmarkCoordinates and DigitizedHeadPoints in the *_coordsystem.json. But how about this matrix?

Rik refers to a 4x4 (or 3x3 if same resolution) affine transformation matrix that maps from the MEG space to MRI space (or vice versa), ie created after coregistering the headpoints+fiducials to the MRI scalp surface. While some people coregister using only the fiducials, others also use headpoints to help with any error in the fiducial locations. This coregistration can be difficult if the headpoints include digitised points on the nose, when the nose is not present in the MRI surface because of de-facing. So he was planning to do the coregistration on a local (non-shared) version of non-defaced MRIs, and provide the transformation matrix for other researchers when we share a (BIDS) version in which the MRIs have (necessarily) been de-faced. What would you recommend?

Could this be related to the extension for affine transformations BEP014?
https://docs.google.com/document/d/11gCzXOPUbYyuQx8fErtMO9tnOKC3kTWiL9axWkkILNE/edit#heading=h.wo1gx72glci0

@robertoostenveld @sappelhoff @agramfort @ftadel @Moo-Marc @jasmainak

@Moo-Marc
Copy link
Contributor

Hi Guio,

I started basically the same discussion on the google group: https://groups.google.com/g/bids-discussion/c/BeyUeuNGl7I

We don't need to save an additional matrix, as long as we assign the "fitted" landmark coordinates either in the _t1w.json (the "MNE approach") or the _coordsystem.json (my suggested "Brainstorm approach"). But I agree it would be best to standardize, in particular so that software tools know how to best import this data (and in particular don't re-do head point fitting on the defaced anatomy).

Cheers,
Marc

@guiomar
Copy link
Collaborator Author

guiomar commented Mar 10, 2021

Thanks Marc!! I hadn't seen the discussion on the google group

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants