...
The DESY afs script seems to work the best. (I am having trouble running EDG commands with the CERN setup script.)
VOMS Server
It is my understanding that before you do anything, you need to authenticate with a proxy server called a "VOMS server"At the beginning of each session, a proxy certificate needs to be obtained.
| No Format |
|---|
voms-proxy-init -verify -debug -voms ilc |
This needs to command should be done executed at the start of every session in which jobs are going to be submitted.
If you get the message VOMS Server for ilc not known! when trying to run this command, or any other commandif other similar error messages occur when running other grid commands, then the information about the ILC VOMS server is missing and needs to be installed at your site.
The ILC VO information can be found on the VOMS at DESY page.
The ilc VOMS file information can be found at downloaded from http://grid.desy.de/etc/vomses/ilc-grid-voms.desy.de and . The contents of this file should be added to the list of VOMS configuration data kept in ~/.glite/vomses. Alternately, or the site's grid administrator can add this information to administrator install the ilc VO information into a central config file.
These The following commands will download the VOMS file and add the information to the user 's config file in the home directory.
| No Format |
|---|
cd ~ mkdir .glite # only needed if .glite does not exist already cd .glite wget http://grid.desy.de/etc/vomses/ilc-grid-voms.desy.de # fetch the VOMS file touch vomses # make sure this file exists cat ilc-grid-voms.desy.de >> vomses # add the ILC VOMS information |
Now, the voms-proxy-init command should work correctly.
| No Format |
|---|
voms-proxy-init -verify -debug -voms ilc |
Test Commands
We will use the The GLITE UI which will be used to run test jobs. It uses commands like starting with "edg-*" for job submission, monitoring, etc.
If not running from DESY, GLITE needs to be told about the ILC VO serversmany of the edg commands will require a config file for the ilc VO, which can be copied from a DESY afs location.
In another shell on lxplus, execute the following commands.
...
Now follow the instructions for submitting a test job at http://grid.desy.de/ilc/ under "Submitting jobs to the Grid".
Look for resources to run a job.
| No Format |
|---|
edg-job-list-match --config-vo ./edg_wl_ui.conf test.jdl |
...
| No Format |
|---|
edg-job-submit --nogui --config-vo ./edg_wl_ui.conf -o test.jid test.jdl |
Test Check the job status.
| No Format |
|---|
edg-job-status -i test.jid |
...
| No Format |
|---|
export LFC_HOST=`lcg-infosites --vo ilc lfc` lfc-ls -l /grid |
Running SLIC
This is a trivial example of running the SLIC simulator on the LCG grid.
Create a shell script slic.sh.
| No Format |
|---|
#!/bin/sh wget http://www.lcsim.org/dist/slic/slic_v2r3p0_geant4_v9r0_i686_linux-gnu.tar.gz tar xzf ./slic_v2r3p0_geant4_v9r0_i686_linux-gnu.tar.gz wget http://www.lcsim.org/detectors/acme0605/acme0605.lcdd printenv ./SimDist/scripts/slic.sh -g ./acme0605.lcdd -r 1 ls *.slcio |
The above script does the following.
- Downloads a tarball with the slic binary and untars it.
- Downloads a detector XML file.
- Prints the environment.
- Runs one event (single muon) on the detector file.
- Prints a list of LCIO files created.
Now make a file slic.jdl.
| No Format |
|---|
Executable = "slic.sh";
StdOutput = "out";
StdError = "err";
InputSandbox = {"slic.sh"};
OutputSandbox = {"out","err","outfile.slcio"};
|
The OutputSandbox contains a list of files that will be cached for retrieval later, including the output LCIO file.
To run the SLIC test job.
...
| No Format |
|---|
edg-job-status -i slic.jdl |
Retrieve the output. By, default the job output will go into a directory in /tmp so we specify the current directory instead.
| No Format |
|---|
edg-job-get-output --dir `pwd` -i slic.jdl
|