Page History

...

The last line, with “jsub” is the line that actually does the submission to the queue.

IMPORTANT: Always submit the xml script with the proper

...

type of runjob! (The xml header will remind you of this as well)

...

e.g. beam-tri_100.xml is submitted with ./runjob_100.sh, and  beam-tri_100to1.xml with ./runjob_100to1.sh                                                         Alternatively, there are 'smart' versions of each runjob script that is meant to handle large numbers of files. These 'smartrunjobs' first check to see if every input file to be used exists, and also that none of the output files exist. If everything is correct, it either submits the jobs, or gives further instructions for how to do so.

'smartrunjob_v1' takes in the beam energy in the same place as the standard runjobs.                                                                                                                                                                                                                                                                      Run with: python smartrunjob_v1.py <job template> <energy> <firstnum> <lastnum>   

'smartrunjob_v2.py' takes in a variable template (e.g. EngRun2015params.xml) in place of the beam energy, which sets any desired run parameters before submitting jobs. (Check this template first!)                                                                                                        Run with: python smartrunjob_v2.py <job template> <variable template> <firstnum> <lastnum>

More details on submitting jobs with 'runjob.sh' can be found below.

A few other helper scripts that are used in the auger xml are in:                                                                                                                                                                                                                                                                                                    /u/group/hps/production/mc/run_params

...