My impression is that qsub
behaves differently from cluster to cluster. However in my experience, I've always just done:
qsub myscrip.sh
Note that this is different than:
qsub bash myscript.sh
qsub csh myscript.csh
In other words, qsub
is a wapper around a shell (usually a particular shell, but since shell's are similar enough, this isn't usually an issue), not around arbitrary commands. The easy fix here is to just put your commands in a shell script and submit that:
#qsub directives here
#wrapper.sh
python commandLineDouble.py 1 10 1
Now you just do qsub wrapper.sh
and Bob's your uncle (Assuming that your cluster's parallel environment has python installed...).