Hi @admin and @ardacanbas1,
I hope that I will be able to take a closer look at the data next week. That’s also my problem, we are still waiting for the upgrade and the formula was based on only one test data set from @meggon. There was already some confusion about VE and XA in the header. The problem is, we have a SeriesDate of 20180121 and a InstanceCreationDate of 20231024. I suspect that a VE data record was imported onto an XA console and then exported again. When jumping from VE to XA, I wouldn’t be entirely sure that it would work flawlessly.The originally imported data no longer exists?
Hi @admin ,
Last week, I tried several approaches to derive orientation values, and I think I have found a method to overcome this issue. Instead of using the SlabOrientation values, I derived rotation angles (in radians) from the RowVector and ColumnVector matrices by decomposing them into Euler angles. I tested this approach on multiple datasets, and so far it appears to work well.
For voxel positioning, I used the MidSlabPosition matrix instead of PositionVector. Apart from these changes, I did not make any major modifications to the existing code.
I would like to thank @wclarke and @hraum for their help and contributions. I am currently working on implementing .rda processing in the next stages of the Oryx-MRSI pipeline, and we hope to release a new version soon. I am sharing the code below, please feel free to review and inspect it.
loadfile.m (9.8 KB)
Mask_Press_run_Pinfo.m (3.7 KB)
1 Like
Hi @hraum
You might be right, the acquisitions date back to 2017–2018, which would explain this. Unfortunately, I was not involved in the acquisition process and only have access to the data in its current form. I also doubt that the scanners still retain this information, since that the data are nearly 10 years old.