Hi all,
It seems that I have a very similar problem. I'm using FSL 5.0.7 on Neurodebian 7.4 (64 bit) on Oracle Virtual Box (the host operating system is Windows 7). When I run FEAT, this is what happens in the terminal:
brain@neurodebian:~$ fsl5.0-feat /home/brain/host/MRI_Data_Research_Internship/2014_08_014/2014_08_014_FSL/feat_test.feat/design.fsf
mkdir .files;cp /usr/share/fsl/5.0/doc/fsl.css .files;ln -s /usr/share/fsl/5.0/doc/images .files/images
while executing
"fsl:exec "mkdir .files;cp ${FSLDIR}/doc/fsl.css .files;ln -s ${FSLDIR}/doc/images .files/images""
(procedure "fullFirstLevelAnalysis" line 51)
invoked from within
"fullFirstLevelAnalysis $session"
invoked from within
"if { $done_something == 0 } {
if { ! $fmri(inmelodic) } {
if { $fmri(level) == 1 } {
for { set session 1 } { $session <= $fmri(multiple..."
(file "/usr/share/fsl/5.0/bin/feat" line 389)
The corresponding log file only contains the following lines:
/bin/cp /tmp/feat_oqj7Ph.fsf design.fsf
/usr/share/fsl/5.0/bin/feat_model design
mkdir .files;cp /usr/share/fsl/5.0/doc/fsl.css .files;ln -s /usr/share/fsl/5.0/doc/images .files/images
FATAL ERROR ENCOUNTERED
The problem seems to occur on line 127 in the feat script:
fsl:exec "mkdir .files;cp ${FSLDIR}/doc/fsl.css .files;ln -s ${FSLDIR}/doc/images .files/images"
Apparently a symbolic link cannot be created, or it is broken. For all that I know the problem doesn't seem to becaused by the fact that the link cannot be written. When I run the respective command (ln -s ${FSLDIR}/doc/images .files/images) on its own in a different folder, the hidden directory (.files) and the symbolic link are created. When I click on the symbolic link, it directs me to the proper target (i.e. ${FSLDIR}/doc/images). However, in the properties of this symbolic link it says that the link is broken.
When the last part of line 127 is deleted form the feat script, the problem does not occur anymore:
fsl:exec "mkdir .files;cp ${FSLDIR}/doc/fsl.css .files"
In this case the whole analysis runs without any error mesages. The only side effect that I noticed is that the report.html file isn't opened automatically as usually. However, when I manually open that file after feat has finished, everything looks normal.
So, by deleting the last bit of line 127 in the feat script I could circumvent the problem. Maybe someone with more experience could come up with a proper solution?
Many thanks in advance.
Cheers,
Ingo
|