-
Notifications
You must be signed in to change notification settings - Fork 9
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
make_phantom - Signed byte volumes created with wrong voxel range #26
Comments
There are indeed a few places where the value range is hard-coded and isn't adapted properly for changing the output type: It looks like you could fix this with: I'll need to dig into http://www.bic.mni.mcgill.ca/~david/volume_io/volume_io.html to figure out how to programmaticly set the voxel range properly given the default voxel range for a given voxel type.
|
Note the valid_range being 0 to 255 which doesn't work for signed bytes. The range should be -128 to 127 right?
Using mincstats on the same volume gives me :
The text was updated successfully, but these errors were encountered: