Page History

...

To run DQM

example uses run 7373, and reads the files from cache (replace with the number of the run you are using):

1. Check to make sure that all the evio files have been copied from the counting house to the mss tape before proceeding /cache/mss/hallb/hps/data/ before proceeding.  (Note:  the script hps2tape.sh, which copies the files to tape, also copies it to cache as well).  
2. Check if the DQM workflow already exists .  If so, and the workflow is already running, just let it continue running.  for the run before starting the DQM.  If it already exists, do not proceed.  In this case, DQM is either running, or is on queue to run on the farm.     
   •    swif status run-7373-dqm-workflow

3. Execute the following commands to create the workflow and run

   it.  NOTE:  Add "–cache" (without quotes) to the end of the last command if the evio files are in cache.  The script that copies the files from clon to tape automatically also copies them to cache.  The DQM will the read the files from cache, and then remove them from there when

   it

   is done if this option is set

   .

    Otherwise, DQM will read the files from tape, which is slower.

    
   
   

   •    ssh hps@ifarm
   •    cd /group/hps/production/dqm/scripts
   •    python mkworkflow.py 7373 7373 --request --request cache

This creates a workflow, generates a group of jsub scripts, adds the jsubs to the workflow, and then runs the workflow.   

...

A note from the DQM coordinator:   The mkworkflow.py script generates an error message if anyone attempts to execute it from any account other than the hps account.  This is intentional, because whichever account starts the workflow owns the dqm files, which only the hps account should own, not somebody's personal account (including the DQM coodinator). 

File Locations

The DQM files will be found in

...