Difference: ProductionHowto (3 vs. 4)

Revision 42012-10-11 - DanProtopopescu

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

NA62 Monte Carlo Production Howto

Line: 10 to 10
  The web interface for NA62 MC Grid jobs scripting, monitoring and accounting is located at:
Changed:
<
<
http://ppewww.physics.gla.ac.uk/~protopop/na62/mc/tools/index.php?task=production
>
>
http://na62.ppe.gla.ac.uk/index.php?task=production
 
Changed:
<
<
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).
>
>
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).
 
Changed:
<
<

Grid access

>
>
Job submissions in production mode are done via the Scripter interface, as explained below.
 
Deleted:
<
<
First of all, you must have access. That means 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)

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:

Changed:
<
<
http://ppewww.physics.gla.ac.uk/~protopop/na62/mc/tools/scripter.php
>
>
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:

ScripterUI.001.png

Description of the form fields:

 
Changed:
<
<
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.
>
>
  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.
  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.
Deleted:
<
<
Towards the bottom of the page there's a list of commands like this:
 
Deleted:
<
<
SubmitJob.png
 
Changed:
<
<
You should copy these commands to the clipboard.
>
>
ALERT! You have to obtain the necessary password (PIN) from the production coordinator.
 
Deleted:
<
<

Job submission

 
Changed:
<
<
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
>
>

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

  DBForm.png
Changed:
<
<
to insert the job specs and status URL in the run database. ALERT! You have to obtain the necessary password (PIN) from the production coordinator.
>
>
to insert the job specs and status URL in the run database. ALERT! You have to obtain the necessary password from the production coordinator.

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)
 
Changed:
<
<

Multiple jobs submission

>
>
Make sure you have all the above. Familiarize yourself with Grid commands before trying this feature.
 
Deleted:
<
<
Batches of jobs are submitted in a similar manner, but the run database is automatically updated in this case. ALERT! You have to obtain the necessary password (PIN) from the production coordinator.
 

Troubleshooting

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

Deleted:
<
<
-- DanProtopopescu - 2012-09-20
 
META FILEATTACHMENT attachment="SubmitJob.png" attr="h" comment="Submit commands example" date="1348225491" name="SubmitJob.png" path="SubmitJob.png" size="64747" stream="SubmitJob.png" tmpFilename="/usr/tmp/CGItemp26913" user="DanProtopopescu" version="2"
META FILEATTACHMENT attachment="DBForm.png" attr="h" comment="Run DB insertion form" date="1348224283" name="DBForm.png" path="DBForm.png" size="23533" stream="DBForm.png" tmpFilename="/usr/tmp/CGItemp23669" user="DanProtopopescu" version="1"
Added:
>
>
META FILEATTACHMENT attachment="ScripterUI.001.png" attr="h" comment="Scripter UI" date="1349972004" name="ScripterUI.001.png" path="ScripterUI.001.png" size="127975" stream="ScripterUI.001.png" tmpFilename="/usr/tmp/CGItemp27714" user="DanProtopopescu" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback