|
META TOPICPARENT |
name="WebHome" |
How to submit simple jobs onto the Grid |
|
> grid-proxy-init -valid 4:00 This is the same, but the authentication will expire in 4 hours (default lifetime is 12 hours). |
|
< < | If you are member of more then one VO, you can choose between them by using the voms-proxy-init for logging in, instead of grid-proxy-init . E.g.: |
> > | If you are member of more then one VO, you can choose between them by using the voms-proxy-init for logging in, instead of grid-proxy-init command. E.g.: |
|
> voms-proxy-init -voms hungrid Or:
> voms-proxy-init -voms hungrid -valid 4:00 |
|
< < | To get information on your user proxy, you can use the commands grid-proxy-info or voms-proxy-info . |
> > | To get information on your user proxy, you can use the commands grid-proxy-info or voms-proxy-info -all . |
|
Get your jobs authenticated on the Grid |
|
Requirements = (
Member("AFS", other.GlueHostApplicationSoftwareRunTimeEnvironment) && |
|
< < | other.GlueCEUniqueID=="grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid" |
> > | other.GlueCEPolicyMaxWallClockTime>=2160 |
| );
] |
|
-
Executable - This variable specifies the executable file of your job.
-
StdOutput - The StdOut of your program shall be written into this file.
-
StdError - The StdError of your program shall be written into this file.
|
|
< < |
-
InputSandbox - This is a list of files, which are sent to the system as the components of your job. Typically the executable of your program, and some supplementary files. The size of the files, sent via the
InputSandbox , should be small (<10MB). Large files (as large input data files) should be communicated to the job by other ways, e.g. via AFS, NFS, or the internet (using e.g. wget ), or via the Grid Storage System.
-
OutputSandbox - This is a list of files, which are retrieved after the job has finished. Typically the file containing the StdOut / StdError and some output files. The size of the files, retrieved via
OutputSandbox , should be small (<100MB). Large files (as large output data files) should be transfered by other means, e.g. via the Grid Storage System.
-
Requirements - This optional variable may be a logical expression, specifying requirements for site or the node, where the job is going to be executed.
Member("Some_software", other.GlueHostApplicationSoftwareRunTimeEnvironment) means the requirement of the software Some_software on the target node. other.GlueCEUniqueID=="grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid" means the requirement that the job should be sent to the computing element (queue) grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid .
|
> > |
-
InputSandbox - This is a list of files, which are sent to the system as the components of your job. Typically the executable of your program, and some supplementary files. The size of the files, sent via the
InputSandbox , should be small (<10MB). Large files (as large input data files) should be communicated to the job by other ways, e.g. via AFS, NFS, or http (using e.g. wget ), or via the Grid Storage System.
-
OutputSandbox - This is a list of files, which are retrieved after the job has finished. Typically the file containing the StdOut / StdError and some output files. The size of the files, retrieved via
OutputSandbox , should be small (<100MB). Large files (as large output data files) should be transfered by other means, e.g. via the Grid Storage System.
-
Requirements - This optional variable may be a logical expression, specifying requirements for site or the node, where the job is going to be executed.
Member("Some_software", other.GlueHostApplicationSoftwareRunTimeEnvironment) means the requirement of the software Some_software on the target node. other.GlueCEPolicyMaxWallClockTime>=maximal_running_time means the requirement for such queues, where the job execution time limit is larger than the specified maximal_running_time (in minutes). A requirement of the form other.GlueCEUniqueID=="grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid" would mean the requirement that the job should be sent to the computing element (queue) grid109.kfki.hu:2119/jobmanager-lcgpbs-hungrid .
|
|
Once you prepared the JDL file, you can look for the available queues, which are capable of running your job, by the command: |
|
< < | > edg-list-match -vo your_vo testjob.jdl
|
> > | > edg-job-list-match -vo your_vo testjob.jdl
|
| |
|
< < | This will return a list of Grid queues (computing elements). |
> > | This will return a list of Grid queues (computing elements), which are capable of executing your job. |
|
The job can be submitted by the command: |
|
This will retrieve the content of the OutputSandbox into the directory /tmp/jobOutput/yourusername_jobID . |
|
< < | For further information, look at the man pages of the above commands, and maybe also to the man pages of other edg- commands. For further references on simple job submission, see https://edms.cern.ch/file/454439//LCG-2-UserGuide.html . |
> > | For further information, look at the man pages of the above commands, and maybe also to the man pages of other edg- commands. For further references on simple job submission, see https://edms.cern.ch/file/454439//LCG-2-UserGuide.html . Also a complete description of the JDL language is available there. |
| |