You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Dany:
There seems to be an issue with mincbbox on volumes with a single value,
but with a range of possible voxel values. To reproduce that issue, you can
create a volume with:
1- make_phantom -signed -short -voxel_range -10 100 <template_volume>
2- minccalc -expression '1' <template_volume> <test_volume>
That yields a volume filled with 1s, but with voxel that could range from
-10 to 100. Calling mincbbox on that volume returns "X X X -inf -inf -inf"
where X is 1.8E308. Repeating those same steps, but filling the volume with
values >10 would not have this issue.
From Dany:
There seems to be an issue with mincbbox on volumes with a single value,
but with a range of possible voxel values. To reproduce that issue, you can
create a volume with:
1-
make_phantom -signed -short -voxel_range -10 100 <template_volume>
2-
minccalc -expression '1' <template_volume> <test_volume>
That yields a volume filled with 1s, but with voxel that could range from
-10 to 100. Calling mincbbox on that volume returns "X X X -inf -inf -inf"
where X is 1.8E308. Repeating those same steps, but filling the volume with
values >10 would not have this issue.
As far as I can tell this is because the scale is forced to take a non-zero
value here:
https://github.com/BIC-MNI/libminc/blob/master/volume_io/Volumes/volumes.c#L2537-L2543
I can see two main ways to see that issue:
The text was updated successfully, but these errors were encountered: