I have a question about my FSL third level analysis for RiskTime.01. The highest-level report log (the one in the top-level output directory looks fine, and the program did produce data for the contrast (though data that didn't look like what I would have expected based on previous analyses).
However, when I go down one level into the cope1.feat directory and look a the report log there, I get something that looks like this:
Progress Report / Log
Started at Fri May 30 13:36:09 EDT 2008
Higher-level stats
cat ../design.lcon | awk '{ print }' > design.lcon
/usr/local/fsl/bin/flame --cope=filtered_func_data --vc=var_filtered_func_data --dvc=tdof_filtered_func_data --mask=mask --ld=stats --dm=design.mat --cs=design.grp --tc=design.con --ols --nj=10000 --bi=500 --se=1 --fm --zlt=100000 --zut=100000
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
The same message (DOF cannot be zero or negative!) repeats for many pages. Then it switches to:
DOF cannot be zero or negative!
DOF cannot be zero or negative!
DOF cannot be zero or negative!
Log directory is: stats
Setting up:
ntptsing=23.000000
No f contrasts
nevs=1
ntpts=23
ngs=1
nvoxels=221619
Running:
nmaskvoxels=601
njumps = 10000
burnin = 500
sampleevery = 1
nsamples = 9500
Metropolis Hasting Sampling
Number of voxels=601
Percentage done:
1
stdtr domain error
ndtri domain error
stdtr domain error
ndtri domain error
stdtr domain error
ndtri domain error
stdtr domain error
ndtri domain error
stdtr domain error
ndtri domain error
stdtr domain error
ndtri domain error
Then it keeps counting up the percentage done from 1 to 100 with these same error messages repeated every time, after which it finishes off with the post-stats looking normal.
I don't know what's happening. Is this supposed to be happening? Like I said, it does output a contrast, but none of my older third-levels have log files that contain these sorts of error messages and I can't shake the feeling that so many pages of errors must mean something is wrong.
The second-levels logs all normal (both the top directory report and the report for the individual cope I checked).
Any ideas what's going on?
FSL - cope1 report log errors
Posted - May 30 2008 : 3:08:33 PM
