Changes

Jump to navigation Jump to search
415 bytes added ,  14:55, 18 March 2016
no edit summary
Line 17: Line 17:  
A simple description file goes as follows:
 
A simple description file goes as follows:
   −
<pre>Executable = myprog
+
<pre>Requirements = ParallelSchedulingGroup == "stats group"
Requirements = ParallelSchedulingGroup == "stats group"
   
Universe  = vanilla
 
Universe  = vanilla
 +
Executable = myprog
 +
Arguments = $(Process)
 +
request_cpus = 1
   −
output    = myprog$(Process).out
+
output    = myprog-$(Process).out
error    = myprog$(Process).err
+
error    = myprog-$(Process).err
 
Log      = myprog.log
 
Log      = myprog.log
    +
transfer_input_files = myprog
 
should_transfer_files = YES
 
should_transfer_files = YES
 
when_to_transfer_output = ON_EXIT
 
when_to_transfer_output = ON_EXIT
 +
on_exit_remove = (ExitCode =?= 0)
 +
transfer_output_remaps = "<default_filename> = /home/<username>/jobs/<default_filename>"
    
Queue 50</pre>
 
Queue 50</pre>
Line 37: Line 42:  
where <i>input.file</i> is the name of your file. It is also implied that the file is in the same directory as the submit file.
 
where <i>input.file</i> is the name of your file. It is also implied that the file is in the same directory as the submit file.
   −
The <b>universe</b> option in the submission file specifies the condor runtime environment. Vanilla is the simplest runtime environment and executes a single-core program inside a single job slot. Multi-core and multi-processor jobs can be scheduled using the parallel universe. See the Condor documentation for more details on scheduling jobs in the parallel universe.
+
The <b>universe</b> option in the submission file specifies the condor runtime environment. Vanilla is the simplest runtime environment and executes a single-core program inside a single job slot. Multi-core and multi-processor jobs can be scheduled using the parallel universe. For jobs requiring multiple cores, change <b>request_cpus</b> to the desired number. Note that the more cores you request the longer you may have to wait for a machine to become available with the resources you request. See the Condor documentation for more details on scheduling jobs in the parallel universe.
    
For optimal allocation of resources, <b><i>serial jobs ought to be submitted to Condor as well</i></b>. This is accomplished by omitting the number of job instances leaving only the directive <i>Queue</i> in the last line of the job description file outlined above. Obviously, <i>$(Process)</i> placeholder is no longer necessary since there will be no enumeration of output files.
 
For optimal allocation of resources, <b><i>serial jobs ought to be submitted to Condor as well</i></b>. This is accomplished by omitting the number of job instances leaving only the directive <i>Queue</i> in the last line of the job description file outlined above. Obviously, <i>$(Process)</i> placeholder is no longer necessary since there will be no enumeration of output files.
191

edits

Navigation menu