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

bedpostx spherical coordinate reference axes #94

Closed
Lestropie opened this issue May 1, 2024 · 0 comments
Closed

bedpostx spherical coordinate reference axes #94

Lestropie opened this issue May 1, 2024 · 0 comments

Comments

@Lestropie
Copy link
Collaborator

Ideally, conversion of a bedpostx output to BIDS compliance would only require basic image manipulation operations such as concatenation. I need to check the outputs of bedpostx on datasets with different orientations to see exactly how they encode those polar angles. If they don't conform to the ISO standard, then we will either need to define a third reference axis system over and above ['ijk', 'xyz'] to support those data directly, or unambiguously define the mathematical transformations required to get from bedpostx to BIDS and back again.

I have recently acquired a dataset that's ideal for this purpose: 24 combinations of slice encoding direction / slice order / phase encoding direction. So I can run bedpostx on all 24, then attempt conversion to scanner-space 3-vectors and check the result in mrview.

Lestropie added a commit that referenced this issue Jun 5, 2024
- FSL bedpostx command fibre orientations stored as spherical coordinates are confirmed to use the "bvec" reference frame.
- Enforcing azimuth angle to obey the right hand rule about the zenith axis would necessitate direct modification of image intensities from bedpostx outputs to store. Therefore it would be preferable to instead define the sign of the azimuth angle based on the direction of the second reference axis.
Closes #95.
Closes #94.
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

1 participant