Re: [Condor-users] submit file problem

[Todd Tannenbaum <tannenba@xxxxxxxxxxx>]

On 12/21/2011 11:51 AM, nuhaa wrote:
> hi,
>
> i have a problem regarding the submit file. i have 4 images (A0.png -
> A3.png). i need to run myexec twice on each image but with different
> arguments. but then i need the log file to be grouped by image because i
> need to see how long does it take to run both executables on an image.
> this submit file does not work. after the first queue, it looks for
> A4.png which doesnt exist.
>
> universe = vanilla
> should_transfer_files = YES
> when_to_transfer_output = ON_EXIT
> executable = myexec
> input = A $(Process).png
> log = set$(Cluster).log
> output = set1-firstArg.out $(Cluster).$(Process)
> arguments = arg1 arg2
> queue 4
> output = set1-secArg.out $(Cluster).$(Process) #Process has become 4 here
> arguments = arg1 arg3
> queue 4
>
>
> is there any way i can do this?


Yes. What is happening above is all the jobs are going into one cluster, 
which is the expected behavior.  To get two job clusters, each with 
$(Process) going from 0 to 3, you have two choices:

1) make two separate submit files and run condor_submit twice

or

2) when condor_submit sees another "executable" line in the config 
files, it will start a new cluster. this isn't officially supported, but 
it works.  My guess is if you simply took your above submit file and 
inserted the line
   "executable = myexec"
before your second queue statement, like I have below, it will all work 
as you want.

universe = vanilla
should_transfer_files = YES
when_to_transfer_output = ON_EXIT
executable = myexec
input = A $(Process).png
log = set$(Cluster).log
output = set1-firstArg.out $(Cluster).$(Process)
arguments = arg1 arg2
queue 4
output = set1-secArg.out $(Cluster).$(Process)
arguments = arg1 arg3
executable = myexec
queue 4


regards,
Todd