Are there any voxels in your map that survive the 1.3 sig threshold?
On 06/07/2015 03:56 AM, std...@virgilio.it wrote:
> Hi list,
>
> I'm performing FS-FAST for seed-based (thalamus).
> During mri_glmfit-sim --glmdir my-glm.wls/ --grf 1.3 neg
> --cwpvalthresh .0166
> I have this error:
>
> Input
Hi list,
I'm performing FS-FAST for seed-based (thalamus). During mri_glmfit-sim
--glmdir my-glm.wls/ --grf 1.3 neg --cwpvalthresh .0166I have this error:Input
volume FOV xfm Matrix:
-2.000 0.000 0.000 76.000;
0.000 0.000 2.000 -93.000;
0.000 -2.000 0.000 76.000
No; it is not thickness; it is GM/WM intensity values;
thank you for the suggestion with mri_mcsim.
2015-03-23 18:22 GMT+01:00 Douglas N Greve :
>
> Yes, 35 is more than I've precomputed. But another question is whey it
> is 35 when it looks like you've smoothed it by only 15. What is the
> nat
Yes, 35 is more than I've precomputed. But another question is whey it
is 35 when it looks like you've smoothed it by only 15. What is the
nature of this data? Is it thickness?
If this is something you really need/want to do, I'm recommending that
people start using mri_mcsim instead of runnin
Yes,
the mri_glmfit run correctly (also for a similar analysis where the
computed FWHM was under 30 mri_glmfit-sim run without problems)
the mri_glmfit command was:
*mri_glmfit --glmdir $path/resultsDIR --y
$path/lh.all_long.wm_orig_0.2.mgh-rate.fwhm15.fsaverage.mgh --fsgd
$path/gender_csf_stroop
did this run correctly with just mri_glmfit? What was your mri_glmfit
command line? Why are you running a simulation instead of using cached data?
doug
On 03/21/2015 10:52 AM, Dídac Vidal wrote:
> Dear Freesurfer users,
>
> I am trying to run mri_glmfit in simulation mode as the computed FWHM
Dear Freesurfer users,
I am trying to run mri_glmfit in simulation mode as the computed FWHM is
over 30
I run --> mri_glmfit-sim --glmdir GLMDIR
\--sim mc-z 1 1.3 mc-z.abs.13
\--sim-sign abs
However I get an dimension mismatch error
-->ERROR:
