Hi
This message is caused by a script that monitors the status of bedpostx (it calculates how many slices have been processed). 
Running bedpostx on a local machine (as opposed to a SGE-equipped cluster) causes the monitor script to crash (sometimes) when bedpostx finishes. 
The error is completely harmless, since the monitor script is independent of bedpostx. 
We thought we had fixed that, but apparently not! 
We will look into this but for the time being, please simply ignore that error message.

Cheers,
Saad.

 

On 23 Sep 2010, at 09:51, shantanu ghosh wrote:

Hi Roser and other FSLers,

Some time ago I posted a similar bedpostx error (reproduced below) but got no answers. 

Queuing post processing stage
Done!
Error: ${FSLDIR}/bin/bedpostx line 281
You have mail in /var/spool/mail/root

Although checking the bedpostx directory it seems fine. The version is FSL 4.1.5 and is being run in rhel5. I have previously run the same dataset in FSL in rhel4 w/o any problems. Is rhel5 the problem source? \

Thanks in advance for any help.

Shantanu


 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
P Please consider the environment before printing this e-mail
 
Shantanu Ghosh, PhD
Assistant Professor
Cognitive Science Lab
Indian Institute of Technology Delhi
Hauz Khas
New Delhi 110 016
INDIA
T +91.11.2659.1382
F +91.11.2659.2277



From: Roser Sala <[log in to unmask]>
To: [log in to unmask]
Sent: Thu, 23 September, 2010 1:25:21 PM
Subject: [FSL] bespostx strange messages

Hello all, 

we are running bedpostx on healthy subjects data (in FSL v.4.1.5), and we usually get two kinds of 'error' messages :

the fist one:
...
65 slices processed
For some reason the bedpostX process DOES NOT appear
to have successfully completed. Please examine your
results carefully.
/usr/local/fsl/bin/bedpostx: line 250: kill: (32542) - No existe el proceso

and the second one:
....
/usr/local/fsl/bin/bedpostx: line 293:  3257 Seņal definida por el usuario 1        ${subjdir}.bedpostX/monitor
(which would be something like 'signal defined by user 1')

In the bedpostx output directory we have all the files that we are supposed to, and visually checking the results they seem to be ok.

We don't know where do these messages come from, and how can we check the output in a more accurately way

Many thanks, 

Roser.





--
Saad Jbabdi
University of Oxford, FMRIB Centre

JR Hospital, Headington, OX3 9DU, UK
(+44)1865-222466  (fax 717)