Difference: ProductionHowto (15 vs. 16)

Revision 162016-03-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://na62.gla.ac.uk/index.php?task=production
>
>
https://na62.gla.ac.uk/index.php?task=production
  You can use this interface to monitor running and completed jobs, output files and production status. You can also use the iPhone app to monitor jobs, files and production status.
Line: 31 to 31
 The Scripter is an user-friendly UI for producing all necessary job submission scripts (JDL, wrapper and .mac file), in both single- and multiple job submission scripts and commands for NA62 MC job submission. The Scripter is located here:
Changed:
<
<
http://na62.gla.ac.uk/scripter.php
>
>
https://na62.gla.ac.uk/index.php?task=scripter
  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.
Line: 48 to 48
 
  1. 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). 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.
  3. Radiative corrections, Disable detector(s), Disable Cherenkov - leave default value here ("off", "none,none"), unless instructed otherwise.
Changed:
<
<
  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). ALERT! If jobs fail at a site, uncheck it here, notify the site admin and add a comment in the logbook!
>
>
  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). ALERT! If jobs fail at a site, uncheck it here, notify the site admin and add a comment in the logbook!
 
  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. ALERT! 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. Click Prepare, and you are taken to a new page. ALERT! 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.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback