Hi Michael,
that's fine, these two numbers are not related. The 50 volumes in the merged_* files correspond to 50 samples from the parameters distribution, while the number of volumes in the input file is the number of diffusion-sensitizing directions applied during the acquisition.
Cheers,
Stam
On 13 Jul 2011, at 19:36, Borich, Michael wrote:
> Hi Saad,
>
> Thank you for the response and information. I have checked the merged_* files and the correct number of slices are present but this check prompted one other follow-up question: Should the number of volumes be different from the input data? There are 50 volumes contained within each merged_ file but 61 volumes in the input file. My assumption is that this is not an issue but wanted to confirm. Thank you again for your assistance.
>
> Best,
> Michael
> _____________________
> Michael R. Borich, DPT, PhD
> Postdoctoral Research Fellow
> Brain Behavior Laboratory
> University of British Columbia
> 212-2177 Wesbrook Mall
> Vancouver, BC V6T 1Z3
> phone: 604-827-3369
> fax: 604-822-1870
>
> ________________________________________
> From: FSL - FMRIB's Software Library [[log in to unmask]] on behalf of Saad Jbabdi [[log in to unmask]]
> Sent: Tuesday, July 12, 2011 10:10 AM
> To: [log in to unmask]
> Subject: Re: [FSL] Error message when using bedpostx
>
> You can safely ignore this error message, which is related to a monitoring process that is running in the background.
> A safe way to check if everything went fine is to compare the number of slices in the merged_* files to that of the input data.
> You can also look at the error logs in the log sub-directory.
>
> Saad.
>
>
>
> On 12 Jul 2011, at 17:28, Michael Borich wrote:
>
>> Hello all,
>>
>> I am receiving the following error message when running bedpostx:
>>
>> Errors: /usr/local/fsl/bin/bedpostx: line 250: kill: (13188) - no such process
>>
>> This appears to happen near the completion of the routine as all output files are created and the files do not appear to be corrupted when running simple probtrackx analyses afterwards. Does anyone have an idea what could be causing this error? Also, is there a reliable way to check the output files to determine if they can be used despite receiving this error message? Thanks!
>>
>> Best,
>> Michael
>>
>
> --
> Saad Jbabdi
> University of Oxford, FMRIB Centre
>
> JR Hospital, Headington, OX3 9DU, UK
> (+44)1865-222466 (fax 717)
> www.fmrib.ox.ac.uk/~saad
>
|