[MINC-users] Building minccmp

[Andrew Wood]

Hi all,

I've been having trouble with minccmp reporting 'inf' and 'nan' on some
float volumes that I've been working with.

It turns out minccmp doesn't deal correctly with NaN inputs values. I'm
wondering what would be sensible behaviour to expect from minccmp.
When corresponding voxels are both NaN, the obvious choices would
be either exclusion, or being treated as a constant (zero, or
user-specified). When one corresponding voxel is NaN, and the other
real, probably only exclusion makes sense.

Does anyone have any thoughts, or different ideas?

Thanks,
Andrew


On Tue, Feb 25, 2014 at 10:36 AM, Vladimir S. FONOV <
vladimir.fonov at gmail.com> wrote:

> I don't remember why, but now I enabled it in develop branch.
>
> https://github.com/BIC-MNI/minc-tools/commit/
> 4dd55a0409871e5ea7963ccee5ca0c1c3a84eeb6
>
>
>
> On 14-02-25 09:42 AM, Andrew Wood wrote:
>
>> Hi all,
>>
>> It seems that minctools isn't set up to build minccmp. Has it been
>> excluded
>> on purpose? Or would it be safe to turn on?
>>
>> Thanks,
>> Andrew
>> _______________________________________________
>> MINC-users at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>>
>>
>
> --
> Best regards,
>
>  Vladimir S. FONOV ~ vladimir.fonov <at> gmail.com
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>