Hi,
I think a while back that Matt Glasser posted the 'fsl_sub' that we use on
our TORQUE system. For convenience, I'm again attaching the 'fsl_sub'
that we are using currently with FSL 5.0.6.
It is provided solely as is, in the hope that it may be beneficial to
others using TORQUE. I can not provide any support if it doesn't work on
your particular system.
Good luck,
-MH
--
Michael Harms, Ph.D.
-----------------------------------------------------------
Conte Center for the Neuroscience of Mental Disorders
Washington University School of Medicine
Department of Psychiatry, Box 8134
660 South Euclid Ave. Tel: 314-747-6173
St. Louis, MO 63110 Email: [log in to unmask]
On 2/19/14 12:50 PM, "Kathy Pearson" <[log in to unmask]> wrote:
>Michael,
>
>So far I have only a work-around, no real solution, for these problems
>noted with redhat torque and moab:
> (a) if a job completes, no more dependencies may be added to it with
>qsub -W
> (b) the array dependence jid[N] may need to be expanded to jid[1]
>jid[2] ... jid[N] --- or perhaps replace afterok with afterokarray
>
>For (a), I have simply used the qsub -h option to hold all jobs, then
>called qrls to release them after feat finishes queueing all of the
>tasks. I am unsure of how to incorporate this idea into fsl_sub. Using
>the qsub -h option is merely an expedient to make our grid behave more
>like SGE where I never saw this problem.
>
>The (b) question could likely be resolved within fsl_sub, but I cannot
>get the afterokarray syntax to work as documented on my system and
>stringing out jid[1]:jid[2] ... jid[91] as I have done certainly seems
>inelegant.
>
>Kathy
>
>--------------------------------------------------------
>Hi Kathy and Henk,
>
>could I maybe interest you in collaborating on github (or any other scm
>resource) for this particular matter?
>
> https://github.com/octomike/fsl_overlay
>
>I would really love to see your changes and add it to our torque/fsl_sub
>overlay !
>
>cheers,
>Michael
________________________________
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
|