Page History

...

• 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 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 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 pretty small, so after these are completed you should tar them up 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

...

The detector simulation is performed by slic, which is itself a front-end for GEANT4 which helps incorporate the specific geometry HPS uses along with putting the GEANT output into LCIO collections that are then used by the reconstruction in hps-java.  The batch scripts do more than just run slic though, particularly for making samples with ; they may also mix components first, such as with the beam overlay.  Below Below is what we do for each sample type:

...

• 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 <firstjob> <lastjob><firstnum> <lastnum>
•  this 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
  • input: 1 file each of beam, hadrons, and (bundled) tri for each num
  • output: 100 files for each num, each differently sampled from the inputs
• enhanced tridents == “tritrig”
• auger  auger xml: /u/group/hps/production/mc/EngRun2015Scripts/slic/tritrig.xml
•  run with ./runjob.sh slic/tritrig.xml 1pt05 <firstjob> <lastjob><firstnum> <lastnum>
•  runs 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 <firstjob> <lastjob><firstnum> <lastnum>
•  runs 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 <firstjob> <lastjob> <firstnum> <lastnum>
  •  this submits 1 job, combing 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
    • input: 100 .slcio files for each num between <firstnum> and <lastnum>, e.g. num=12 processes slic files 1100-1200
      
    • output: 1 readout .slcio file
       
  
   
• enhanced tridents with beam background== “tritrig-beam-tri”
  •  COMING SOON