Yup that worked.
Like the following command line just confirmed... DUH!!!!
data = spm_read_vols(spm_vol('thresh_tmap.nii'));
find(~isnan(data(:)))
ans =
320733
On 15/03/2019 17:57, Flandin, Guillaume wrote:
> Dear Remi,
>
> If you change the interpolation scheme to be nearest neighbour then NaN
> will be replaced by the actual value.
>
> The lucky voxel (p<0.04 FWE-corr!) will still not appear in the figure
> because of the intensity scaling so you have to change the range manually:
> Intensity > Range > This image > Manual > [0 5]
> This voxel is directly visible on the thresholded image because the
> range is computed as min/max from finite values ([0 1] here) while it is
> [5.06 5.06+eps] in the non-thresholded version (as everything but one
> voxel is NaN).
>
> Best regards,
> Guillaume.
>
>
> On 15/03/2019 16:26, Remi gau wrote:
>> Hello all,
>>
>> Encountered a weird problem: one of my analysis gives me a single
>> activated voxel but the thresholded t-map of that analysis has a NAN
>> value for that voxel (see attached pictures).
>>
>> If I however manually threshold the image then everything is fine and I
>> get a single voxel in this image.
>>
>> Any idea what is going on?
>>
>> Best
>>
>> Remi
>>
>>
|