Difference: ProductionHowto (3 vs. 4)

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)