The report.log has some very strange entries in it after the commands:
/bin/mkdir mc ; /bin/mv -f prefiltered_func_data_mcf.par
prefiltered_func_data_mcf_rel.rms prefiltered_func_data_mcf_rel_mean.rms mc
This probably means that something has gone wrong in the mcflirt run
up when the motion plots are being generated. One possibility is that
write to the right place so that some output was not generated or that
existing files that were not overwritten (any SPM *.mat files that were
in the wrong place
could cause a problem like this I guess). However, it could be
to this as well.
Could you check to see if the contents of your mc directory are sensible and
like other feat folders? If you are not sure then send us a long
listing (ls -l) of
All the best,
Johannes Klein wrote:
>I'm trying to re-evaluate some old data with Feat for comparison with the
>old SPM results, which is a simple ABAB style block design. When I start the
>analysis, it runs for awhile and then the console says:
>error reading "file4": I/O error
> while executing
>"gets $mcchannel line"
> (procedure "feat5:proc" line 598)
> invoked from within
>"feat5:proc [ file rootname [ lindex $argv 0 ] ]"
> (file "/usr/local/fsl/bin/feat" line 17)
>Processing stops. I've attached the report.log.
>I'm a bit lost here. Can anyone give me a hint what's wrong?
>Thanks for your time