rostral-caudal axis is flipped for tail prone data about brkraw

[dvm-shlee]

@eugenegkim That's just a bug because I haven't had enough test case for that.
Could you provide the dataset that causes the issue? then I can fix it for the next update.

Thank you!

[eugenegkim]

Yeah! Seems like ages ago. Hope you and all your loved ones are doing well.

[dvm-shlee]

@eugenegkim Oh BTW, could you let me know if it just flipped or rotated 180 degrees so that the left and right are also flipped?

If you are urgent to access the data and If you are familiar with python, you can easily correct that with python API.

For example. as below.

import numpy as np
import nibabel as nib
import brkraw as br
from brkraw.lib.utils import apply_rotate
raw = br.load('<your raw data path>')
old_nii = raw.get_niftiobj(<scan_id>, <reco_id>)
new_affine = apply_rotate(old_nii.affine, rad_y=np.pi)

new_nii = nib.Nifti1Image(old_nii._dataobj, affine=new_affine, header=old_nii._header)
new_nii.to_filename('<new filename>')

[eugenegkim]

Oh good point. It looks like it's rotated 180 degrees. I use an in-house converter, so it's not urgent. But I'm looking into making all my data BIDS-compliant. I'll send you the dataset in a moment. Thanks!

[dvm-shlee]

@eugenegkim Oh BTW, have we meet at the Bruker sequence programming course? Your name is familiar 😃

[dvm-shlee]

@eugenegkim Thanks for sharing the data. I will update the code once I clarify the issue. Regarding the BIDS, there is something I haven't documented yet (for JSON), so if you experiencing any issue, please let me know.

[dvm-shlee]

@eugenegkim I found using your dataset that Bruker does internal correction for the position, so actually no need additional correction, but my code originally did. It has been removed now. It will work without issue from v0.3.3 released version.

[eugenegkim]

Thanks!