Difference: ProductionHowto (1 vs. 16)

1. Destination - tick here only the sites that have the chosen MC software version installed. Check this table to make sure. Check the jobs history to detect any problems at sites (e.g. jobs consistently finishing early, or going to status CLEARED without registering any output). If jobs fail at a site, uncheck it here, notify the site admin and add a comment in the logbook!

1. Choose description - this is now a drop down menu, containing items from the actual production schedule
2. Run numbers - the start run is pre-filled with the next available run number (from the DB). Choose the upper limit such that you submit not more than 100 jobs at a time.
3. Number of events - this is the number of events per job (run). We aim to keep the job runtime below 12 hours, so for channel 10 and v9/r261 that means 6000 events per job. For other channels you would have to calculate an optimum. How to do this: submit a 300-500 events job; when it finishes with output saved locally, go to the jobs table, click the "Submission Date/Time" cell to expand the row and get detailed info. Find in there the "events per second" figure. Calculate how many events (in multiples of 1000) we would be able to run and still keep the total runtime below 12 hours. Check previous production jobs as well.
4. Leave the random seed as it is, because it will be set automatically for each run.
5. MC software version - you must use the latest software version (check here if unsure). Take a look at the scripts of previous jobs to make (click sure. There is a grid "version" for each installed software revision (e.g. v6/r188, v7/r193, v9/r261), see this wiki.
6. Radiative corrections, Disable detector(s), Disable Cherenkov - leave default value here ("off", "none,none"), unless instructed otherwise.

1. In single jobs mode, you can display commented lines from scripts in case you would like to check extra settings, comments etc. For production, leave this unchecked.
2. Write scripts to disk/User and password - for multiple job submissions, you need to tick the "Write scripts to disk" checkbox, and introduce your uid and password for this interface. You must have registered and your credentials must have been validated for this to work. In single job mode, uid and password are not needed, since you will have to submit the (test) job with your credentials from your UI.

1. Number of events - this is the number of events per job (run). We aim to keep the job runtime below 20 hours, so for channel 1 an r188 that means 1500 events per job, for r193 and channel 1 the optimum would be 6000 events etc. For other channels it could be more or less than that. Check previous production jobs to find the optimal number of events. Leave the random seed as it is, because it will be set automatically for each run.
2. MC software version - you must use the latest software version (check here if unsure), and make sure the wrapper script supports this version. Take a look at the scripts of previous jobs to make sure (click here, select the last production job, then click the corresponding green box link on the "Exe" column and check the line vers="v?"). There is a grid "version" for each installed software revision (e.g. v6/r188, v7/r193), see this wiki.

1. Destination - tick here only the sites that have the chosen MC software version installed. Check this table to make sure. Check the jobs history to detect any problems at sites (e.g. jobs consistently finishing early, or going to status CLEARED without registering any output). If jobs fail at a site, uncheck it here, notify the site admin and add a comment in the logbook!

1. Click Prepare, and you are taken to a new page. If the page says "There are scheduled submissions in there. Please try again in 5 minutes" it means that you have (or someone else has) just scheduled another batch of jobs and you have to wait for these to be actually submitted, else the scripts may be overwritten - with unpredictable results.

1. Executable - automatically selected now - this is the name of the wrapper script that is executed on the worker node. It checks if the software is installed, runs the actual MC simulation, registers the output and triggers the FTS transfer(s). In single jobs mode, you can display commented lines from scripts in case you would like to check extra settings, comments etc. For production, leave this unchecked.

1. Executable - this is the name of the wrapper script that is executed on the worker node. It checks if the software is installed, runs the actual MC simulation, registers the output and triggers the FTS transfer(s). Make sure the chosen script supports the MC software version selected above. In single jobs mode, you can display commented lines from scripts in case you would like to check extra settings, comments etc. For production, leave this unchecked.

1. Click Prepare, and you are taken to a new page. If the page says "There are scheduled submissions in there. Please try again in 10 minutes" it means that you have (or someone else has) just scheduled another batch of jobs and you have to wait for these to be actually submitted, else the scripts may be overwritten - with unpredictable results.

1. Description - this is a short description of the job. It must contain the production tag (get it from here if unsure), and it must contain the keyword "production". Should not contain quotes or any other non-text characters. Leave out the tag and replace production with test if you want to submit a few test jobs.

1. MC software version - you must use the latest software version (check here if unsure), and make sure the wrapper script supports this version. Take a look at the scripts of previous jobs to make sure (click here, select the last production job, then click the corresponding green box link on the "Exe" column and check the line vers="v?"). There is a grid "version" for each installed software revision (e.g. v6/r188), see this wiki.

1. Destination - tick here only the sites that have the chosen MC software version installed. Check this table to make sure. Check the jobs history to detect any problems at sites (e.g. jobs consistently finishing early, or going to status CLEARED without registering any output). If jobs fail at a site, uncheck it here and notify the site admin!

Monitoring

You can get the iPhone app from here:

The aim is to maintain the production rate at its maximum (whatever that is, depending on the resources available) and for this the person on shift must submit new jobs when the number of waiting and running jobs is low. Job submissions in production mode are done via the Scripter interface, as explained below.

1. Description - this is a short description of the job. It must contain the production tag (get it from here if unsure), and it must contain the keyword "production". Should not contain quotes or any other non-text characters. Leave out the tag and replace production with test out if you want to submit a few test jobs.

1. MC software version - you must use the latest software release (check here if unsure), and make sure the wrapper script supports this version. Take a look at the scripts of previous jobs to make sure.
2. Decay type - is the reaction channel to simulate. Choose from the drop-down menu and make sure it corresponds to the current production tag and description (check here if unsure). Leave default values for the remaining options, unless instructed otherwise.

1. Executable - this is the name of the wrapper script that is executed on the worker node. It checks if the software is installed, runs the actual MC simulation, registers the output and triggers the FTS transfer(s). Make sure the chosen script supports the MC software version selected above.
2. User and password - for multiple job submissions, you need to tick the "Write scripts to disk" checkbox, and introduce your uid and password for this interface. You must have registered and your credentials must have been validated for this to work. In single job mode, uid and password are not needed, since you will have to submit the (test) job with your credentials from your UI.
3. Once you click Prepare, you are taken to a new page that shows you the generated scripts.

Multiple Submissions

http://na62.ppe.gla.ac.uk/scripter.php

This is an HTML form with many input filelds, most of them self-explanatory. The pre-filled values are inherited from the previous submission (which could have been a test job for example), so you must check that they fit the production round you are managing.

Here is how the scripter interface looks like:

Description of the form fields:

1. Description - this is a short description of the job. It must contain the production tag (get it from here if unsure), and it must contain the keyword "production". Should not contain quotes or any other non-text characters.
2. Run interval - the start run is pre-filled with the next available run number (from the DB). Choose the upper limit such that you submit not more than 100 jobs at a time. Do not use job cloning for production at the moment.
3. Number of events - this is the number of events per job (run). We aim to keep the job runtime below 20 hours, so for channel 1 that means 1500 events per job. For other channels it could be more or less than that. Check previous production jobs to find the optimal number of events. Leave the random seed as it is, because it will be set automatically for each run.
4. MC software version - you must use the latest software release (check here if unsure), and make sure the wrapper script supports this version. Take a look at the scripts of previous jobs to make sure.
5. Decay type - is the reaction channel to simulate. Choose from the drop-down menu and make sure it corresponds to the current production tag and description (check here if unsure). Leave default values for the remaining options, unless instructed otherwise.
6. Destination - tick here only the sites that have the chosen MC software version installed. Check this table to make sure. Check the jobs history to detect any unexpected problems at sites. If jobs fail at a site, uncheck it here and notify the site admin.

Manual job submission

Jobs can be submitted manually one by one with your credentials (i.e. grid certificate), from command line on your Grid UI. Run the scripter in single run mode (no password is required), paste the commands provided by the scripter into your UI terminal, and press enter. If you have submitted a job this way (e.g. for testing the system), then use the form at the bottom of the page

Remember that to submit jobs with your credentials, you must:

1. have a valid Grid certificate (e.g. a CERN certificate)
2. register for NA62 VO membership via https://voms.gridpp.ac.uk:8443/voms/na62.vo.gridpp.ac.uk/user/home.action (you must have the certificate uploaded into the browser for this).
3. have access to a Grid UI (a computer with the necessary software and settings)

1. have a valid Grid certificate (e.g. a CERN certificate)

You should copy these commands to the clipboard.

Job submission

Jobs must be submitted with your credentials (i.e. grid certificate), from command line on your Grid UI. Paste the commands provided by the scripter into your terminal, and press enter. If you have submitted one job (e.g. for testing the system), then use the form at the bottom of the page

to insert the job specs and status URL in the run database. You have to obtain the necessary password (PIN) from the production coordinator.

Multiple jobs submission

Batches of jobs are submitted in a similar manner, but the run database is automatically updated in this case. You have to obtain the necessary password (PIN) from the production coordinator.

1. have access to a Grid UI (a computer with the necessary software and settings)

NA62 Monte Carlo Production Howto

This wiki explains how to submit NA62 Monte Carlo jobs on the Grid using the custom-written tools and online interface for this. This wiki is written for NA62 members who have volunteered to participate in the production rota.

Online interface

The web interface for NA62 MC Grid jobs scripting, monitoring and accounting is located at:

http://ppewww.physics.gla.ac.uk/~protopop/na62/mc/tools/index.php?task=production

You can use this interface to monitor running and completed jobs, output files and production status. The Scripter section of this online interface provides an user-friendly UI for producing all necessary job submission scripts (JDL, wrapper and .mac file), and for job cloning (multiple job submissions).

Grid access

First of all, you must have access. That means you must:

1. have a valid Grid certificate

1. register for NA62 VO membership via https://voms.gridpp.ac.uk:8443/voms/na62.vo.gridpp.ac.uk/user/home.action (you must have the certificate uploaded into the browser for this).

1. have access to a Grid UI

Make sure you have all the above. Familiarize yourself with Grid commands before proceeding to the next step.

Scripter

This is an online tool that creates the necessary scripts and commands for NA62 MC job submission. Jobs must be submitted with your credentials, from command line on your Grid UI. The Scripter is located here:

http://ppewww.physics.gla.ac.uk/~protopop/na62/mc/tools/scripter.php

This is an HTML form with many input filelds, most of them self-explanatory. The pre-filled values are inherited from the previous submission (which coulkd have been a test job for example), so you must check that they fit the production round you are managing.

Once you click "Prepare", you are taken to a new page that shows you the generated scripts. It's a good idea to doublecked the settings here as well.

... will be continued ...

Troubleshooting

In case you find an error produced by the online interface, please immediately notify Dan, Janusz and Tonino.

-- DanProtopopescu - 2012-09-20