Data cannot be sorted

[mgxd]

Hi Anderson,

I am running into the following issue when running PALM on surface data, I have checked all inputs for NaNs but none are present - any ideas?

Running PALM alpha111 using Octave 4.0.3 with the following options:
-i /input/combined_133_gambling_reward_gtr_loss_R.func.gii
-d /input/design.mat
-t /input/design.con
-T
-saveparametric
-zstat
-ise
-tfce2D
-s /surf/R_midthickness.surf.gii /input/combined_133_gambling_reward_gtr_loss_R_area.func.gii
-o /input/palm/palm_R
Found HCP Workbench executable in /opt/workbench/bin_linux64/wb_command
Loading surface 1/1: /surf/R_midthickness.surf.gii
Reading input 1/1: /input/combined_133_gambling_reward_gtr_loss_R.func.gii
Reading design matrix and contrasts.
Elapsed time parsing inputs: ~ 162.086 seconds.
Number of possible sign-flips is 1.0889e+40 = 2^133.
Generating 10000 shufflings (sign-flips only).
Building null distribution.
0.01%    [Design 1/1, Contrast 1/1, Shuffling 1/10000, Modality 1/1]
     Saving file: /input/palm/palm_R_dpv_ztstat
0.02%    [Design 1/1, Contrast 1/1, Shuffling 2/10000, Modality 1/1]
-----------------
Elapsed time with permutations: ~ 18224.5 seconds.
Computing p-values.
Saving p-values (uncorrected, and corrected within modality and within contrast).
     Saving file: /input/palm/palm_R_dpv_ztstat_uncp
     Saving file: /input/palm/palm_R_dpv_ztstat_fwep
     Saving file: /input/palm/palm_R_tfce_ztstat
     Saving file: /input/palm/palm_R_tfce_ztstat_uncp
Error using palm_competitive (/opt/palm/palm_competitive.m:105)
Data cannot be sorted. Check for NaNs that might be present,
or precision issues that may cause over/underflow.
If you are using "-approx tail", consider adding "-nouncorrected".

Error in palm_datapval (/opt/palm/palm_datapval.m:67->palm_competitive)
Error in palm_saveall (/opt/palm/palm_saveall.m:303->palm_datapval)
Error in palm_core (/opt/palm/palm_core.m:2489->palm_saveall)
Error in palm (/opt/palm/palm.m:81->palm_core)

Thanks!

[andersonwinkler]

Hi Mathias,

Could it be that your input files are in single precision (float32)? Try adding the option "-precision double". Please let me know if it fixes the problem (in which case the error message may be expanded so as to include this option).

All the best,

Anderson

[mgxd]

@andersonwinkler thanks for the quick reply, that was indeed the problem!