Closed JThoennissen closed 1 year ago
Find a screencast showing 1. below:
merged and deployed to staging , can you verify if it's fixed?
The second issue is fixed 👍 The first issue remains, but is not urgent. It seems the scale is initially set to 20,53 for Hippocampus volume ...
Here, I am respecting the transform returned by the image service.
I am unsure why the image service returned to contain the specific transform. better asking @pacher
Why the Hippocampus public volume has a transform like that
[
[
20.531328320802004,
0,
0,
-24353.02734375
],
[
0,
20.531328320802004,
0,
-24353.02734375
],
[
0,
0,
16.66734486266531,
-29998.779296875
],
[
0,
0,
0,
1
]
]
A command line to retrieve the transform would be
curl 'https://zam10143.zam.kfa-juelich.de/chumni/list' | jq '.[1].extra.neuroglancer'
It seems that affine matrix stored in Hippocampus nifti is wrong which is not surprising given the origin of this nifti. I would suggest to close the issue and re-open if this problem is observed with any other user uploaded nifti generated by any standard software.
Upd.: I mean there is no software issue to fix, but we probably need to fix the Hippocampus nifti to improve user experience.
The issue causes two problems: