Line: 1 to 1 | |||||||||
---|---|---|---|---|---|---|---|---|---|
WMSX examples | |||||||||
Line: 6 to 6 | |||||||||
Job submission with edg-job-submit is not very straightforward, as the generated job identifier has to be stored, and then the job output retrieval directory has to be resolved by this identifier. To save you from this typing exercise, the WMSX is capable of managing the output retrieval directory for simple jobs. | |||||||||
Changed: | |||||||||
< < | You can find a prepared example for this task here: . To submit the example job, type the following commands. | ||||||||
> > | You can find a prepared example for this task here: simplejob.tar.gz. To submit the example job, type the following commands. | ||||||||
Get the tarball: | |||||||||
Line: 45 to 45 | |||||||||
> voms-proxy-destroy | |||||||||
Added: | |||||||||
> > | An educative example for simple interactive job submission may be found here: interactive.tar.gz. This works in a similar way as the simplejob.tar.gz example. | ||||||||
Mass submission of independent jobs: parameter scan with short calculationsWMSX is a very convenient tool for mass submission of short, e.g. of about maximum 1 day lifetime, independent jobs. Possible application: parameter scan studies with relatively short calculations. (The job lifetime is limited by the typical allowed maximal job lifetimes, assigned by the Grid sites. A limit of 3 day running time is typical, so a maximum 1 day job is fine.) WMSX automatically manages output retrieval issues and the limiting of the number of concurrently running jobs. For this purpose, the jobs are described with a slightly extended JDL language, which is preprocessed by WMSX. IfJobType = "Interactive" is set, the file containing StdOut / StdErr is updated on the fly, so you can see what your job is actually doing. A pre-execution script helps to prepare inputs, and a post-execution script helps to process outputs of the job. | |||||||||
Changed: | |||||||||
< < | You can find a prepared example for this task here: . To submit the example job, type the following commands. | ||||||||
> > | You can find a prepared example for this task here: sample.tar.gz. To submit the example job, type the following commands. | ||||||||
Get the tarball: | |||||||||
Line: 92 to 94 | |||||||||
The mass submission has an important feature: each job can decide whether a launch of a further job is needed. This decision is done by the post-execution script: if it returns with exitcode 1, the chain script is invoked. The lines of the standard output of the chain script is interpreted by WMSX as lines in the arg.list file (see previous example), so new jobs are launched. In this way, jobs can be chained (and the chains can also fork, as a job can also launch multiple jobs). In this way, a parameter study with long term calculations can be performed. The long term calculations are preformed by the job chains. A good example is numerical solution of partial differential equations: multiple chains are launched (possibly with different initial conditions), and each chain is imitating a long term job (the solution of the partial differential equation with a given initial condition), split up into subsequent shorter term jobs. | |||||||||
Changed: | |||||||||
< < | You can find a prepared example for this task here: . To submit the example job, type the following commands. (Similar to the previous example.) | ||||||||
> > | You can find a prepared example for this task here: chainsample.tar.gz. To submit the example job, type the following commands. (Similar to the previous example.) | ||||||||
Get the tarball: | |||||||||
Line: 130 to 132 | |||||||||
> myproxy-destroy > voms-proxy-destroy \ No newline at end of file | |||||||||
Added: | |||||||||
> > |
-- AndrasLaszlo - 16 Apr 2008
|