Hi Moises,
Thank you for your answer. How do bedpostx compare to bedpostx in terms
of reliability and bugs?
Are there any patch that adds SLURM support to fsl_sub?
Best,
Knut Jørgen
On 01/25/2015 04:03 PM, Moises Hernandez wrote:
> Hi Knut,
>
> bedpostx can be parallelised, but it does not support openmp.
>
> The script divides the dataset into slices. If you have a Grid Engine
> system or similar, the slices will be queued as independent processes.
> Then, if you have more than one slot (cores) in the system, multiple slices
> will be processed in parallel:
>
> http://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FslInstallation#Using_FSL_with_a_GridEngine_.28or_similar.29_computing_cluster
>
> Another option is to use a GPU:
> http://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FslInstallation#Running_bedpostX_on_a_GPU_or_GPU_cluster
>
> Best,
> Moises.
>
>
> On 24 January 2015 at 16:46, Knut J Bjuland <[log in to unmask]> wrote:
>
>> Do bedpostx in FSL 5.0.7 support openmp? I found this command in fsl_sub?
>>
>> How do I force bedpostx to use openmp? Should I load openmp and start
>> -NJOBS 4 if I have four cpus?
>>
>>
>>
>> # Note, we support openmp tasks even when Grid Engine is not in use.
>> omp_pe='openmp'
>> # If the PE name is 'openmp' then limit the number of threads to those
>> specified
>> How can I set export omp_pe to control, which openmp FSL should uses?
>>
>> Knut Jørgen Bjuland
>> NTNU
>>
|