Page History

...

• "beam-tri":  simply simulates the beam going though the target; the “tri” refers to trident events that are inserted at the expected rate.  This is intended to be an unbiased representation of our data
• “tritrig-beam-tri”:  the “tritrig” refers to a sample of tridents that are preselected (at the MadGraph level) to be more likely to be in the detector acceptance and pass the trigger cuts so that we can efficiently get a large sample.  These are then have “beam-tri” overlaid in order to simulate what trident events look like in the detector.  
• “ap” and “ap-beam-tri”:  the “ap” stands for “A prime” and is our signal MC…they can be generated at a given mass and ctau, and we produce them are produced with and w/o beam overlay (mostly with).  
• we’ll also, in the near future, want to simulate dedicated Moller and wide angel Brem samples angle bremsstrahlung samples
  

Below, I go through each generation step for each sample is outlined. 

Batch Job Submission:

There is a basic example on the confluence here:

https://confluence.slac.stanford.edu/display/hpsg/Example+of+using+the+JLAB+Auger+system

For official production, we run Official production runs from here:

/u/group/hps/production/mc/EngRun2015Scripts

and you the user should be logged in as user='hps'. You need to be put on the list to log in as this user, but once you are you don’t need a password; just log into JLAB unix as yourself and then ssh hps@ifarm65 (or any other machine). 

...

The basic format of this xml file is:  

<Request>

 <AugerJobParameter parameter=“blah”/>

...

The last line, with “jsub” is the line that actually does the submission to the queue.

IMPORTANT: Always submit the xml script with the proper version of runjob! (The xml header will remind you of this as well)

e.g. beam-tri_100.xml is submitted with ./runjob_100.sh, and  beam-tri_100to1.xml with ./runjob_100to1.sh

A few other helper scripts that are used in the auger xml are in:   

/u/group/hps/production/mc/run_params

...

• beam electrons:  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/stdhep/beam.xml
•  run with ./runjob.sh stdhep/beam.xml 1pt05 <firstjob> <lastjob>
• the executable that does the event generation is /u/group/hps/production/mc/egs5/beam_v3.exe
• output is a an .stdhep file with each event being 1 scattered electron (I think…1 event _may_ be 1 bunch) 
• beam hadrons:  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/stdhep/hadrons.xml
•  run with ./runjob.sh stdhep/hadrons.xml 1pt05 <firstjob> <lastjob>
• the executable that does the event generation is a GEANT4 release that gets copied locallyorg
• output is a an .stdhep file with each event being hadrons from bunch
• unbiased tridents == “tri”:  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/lhe/tri.xml
•  run with ./runjob.sh lhe/tri.xml 1pt05 <firstjob> <lastjob>
•  this runs MadGraph using the  /u/group/hps/production/mc/trigg/run_card_<ebeam>.dat
• output is an lhe file with each event being 1 trident
• these files are small, so they are bundled 100-to-1 with:
• ./runjob_100to1.sh lhe/tri_merge_100to1.xml 1pt1 1 100
• enhanced tridents == “tritrig”
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/lhe/tritrig.xml
•  run with ./runjob.sh lhe/tritrig.xml 1pt05 <firstjob> <lastjob>
•  this runs MadGraph using the  /u/group/hps/production/mc/tritrig/run_card_<ebeam>.dat
• the cuts here are E(e+e-)>0.8 EBeam and m(e+e-)>10MeV
• output is an lhe file with each event being 1 trident
• signal events ==  “ap-truth”
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/lhe/ap-truth.xml
•  run with ./runjob.sh lhe/ap-truth.xml 1pt05 <firstjob> <lastjob>
•  this runs MadGraph using the  /u/group/hps/production/mc/ap/run_card_<ebeam>.dat
• also converts the lhe to stdhep while adding displaced vertex (though now ct is hardcoded to 0 in the .xml)
• output is an stdhep file with each event being 1 trident

...

• beam simulation == “beam-tri”
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/slic/beam-tri_100.xml
•  run with ./runjob_100.sh slic/beam-tri_100.xml 1pt05 <firstnum> <lastnum>
•  this submits 100 jobs, combining beam, tri, and hadron events into beam “bunches”, 1 per event
  •  e.g. <firstnum>=11, <lastnum>=20 submits 100*(20-11)=1000 jobs
  • inputinputs: 1 .stdhep file each of beam, hadrons, and (bundled) tri for each num
  • outputoutputs: 100 .slcio files for each num, each sampled differently sampled from the inputsmixed input files
• enhanced tridents == “tritrig”
•  auger xml: /u/group/hps/production/mc/EngRun2015Scripts/slic/tritrig.xml
•  run with ./runjob.sh slic/tritrig.xml 1pt05 <firstnum> <lastnum>
•  runs slic over the tridents, 1 trident-per-event
• signal events == “ap-truth”
  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/slic/aptruth.xml
•  run with ./runjob.sh slic/aptruth.xml 1pt05 <firstnum> <lastnum>
•  runs slic over signal events, 1 signal event-per-event

...

• beam background readout == "beam-tri"
  • auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/readout/ beam-tri_<trigger>_100to1.xml
    • <trigger> can be 'singles' (event occurs for each ECal cluster passing the cuts -> more events) or 'pairs' (2 clusters on opposite sides pass the cuts within a time window -> fewer events) 
      
  •  run with ./runjob_100to1.sh readout/beam-tri_pairs1_1_5mm_100to1.xml 1pt05 <firstnum> <lastnum>
  •  this submits 1 job, which combines the simulated readout of 100 files from the previous stage into 1 output file
    • e.g. <firstnum>=11, <lastnum>=20 submits (20-11)=10 jobs
    • inputinputs: 100 sampled .slcio files for each num between <firstnum> and <lastnum>, e.g. num=12 processes slic files 1100-1200
      
    • output: 1 readout .slcio file: the combined readout of the inputs
       
  
   
• enhanced tridents with beam background== “tritrig-beam-tri”
  •  COMING SOON