Jérémie Dubois-Lacoste <[email protected]> writes: > My answer may sounds so stupid that I'm sure I didn't properly get > you problem. :-) > Why not writing a bash script with 34 lines, one for each call to your > 34 sh things, and then submit this "meta" script to the queuing system?
Presumably because the jobs are long-running and there are time or reliability limits. It's normally best to have more short-ish jobs than fewer long ones, though not too short compared with overheads, obviously. > 2012/9/26 Daniel Gruber <[email protected]>: >> The easiest way would be to give a job a name with qsub -N job1 (or use >> -terse for getting the job id) and >> then using -hold_jid for the second job. More details you will find in the >> qsub man page. Of course you >> can also use DRMAA, or more unusual an array job with task throttling (-tc >> 1). Happy to be unusual -- I'd have suggested -tc 1. If necessary in an array job, you pick non-uniformly-named work from a list in a file with $(awk "NR=$TASK_ID" <file>) -- Community Grid Engine: http://arc.liv.ac.uk/SGE/ _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
