-
Notifications
You must be signed in to change notification settings - Fork 4
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
Display develop HEAD reports wrong value for voxel under cursor #65
Comments
ok, is there anything unusual about that file (e.g. what is the voxel type)? Also, do you know if you have Convert_volumes_to_byte set to FALSE? |
The mincheader of the file:
and mincinfo:
I don't have a Display.globals anywhere where the manual says it could be, so I have whatever the code default is for that setting (I think). Can I check somehow? |
The default value for that variable is unfortunately still TRUE. Try running Display with
|
That fixes it. |
So, I guess I can switch that in a ~/.mni-displayrc for myself. Maybe that default should make it into the codebase? |
@gdevenyi I had been planning to make it the default. Will do that today. |
Out of curiosity - since register reported the correct value, I assume this On Thu, Sep 1, 2016 at 8:52 AM, Robert D Vincent [email protected]
|
@zijdenbos Correct. The default was changed in Register a long time ago - I just changed it in Display today. |
@zijdenbos Byte volumes are so 1996. |
That's only 20 years ago :) On Thu, Sep 1, 2016 at 11:46 AM, Robert D Vincent [email protected]
|
I'm writing some code using nibabel to lookup voxel values from minc files, so I was using Display to look at the value under the cursor to compare (since I know both the world and voxel coodinates thanks to recent Display improvements).
I found consistent difference between my nibabel output and Display. After much testing, I have confirmed it's not my nibabel code as register reports the correct value.
Screenshots:
Display:
voxel [96,114,96]
Register:
voxel [96,114,96]
Nibabel:
The text was updated successfully, but these errors were encountered: