Page History

...

• ebeam.csh:  given the beam energy string (e.g. “1pt05”) returns the beam energy in MeV
• dz.csh:  given the beam energy string, returns the target thickness
• ne.csh:  given the beam energy string, returns the number of electrons per 2ns bunch
• apmass.csh: given the beam energy string, returns as list of A’ masses to simulate
• mu.csh: only used by lhe generators (e.g. tridents and wab), sets the number of bunches for each component
  

Event Generation: 

The event generation is performed via MadGraph, EGS5, or GEANT4 depending on the type.  Below lists the different type of particles produced, and some instructions on each.

...

• wide-angle bremsstrahlung == “wab”:  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/lhe/wab.xml
•  run with ./runjob.sh lhe/wab.xml 1pt05 <firstjob> <lastjob>
•  this runs MadGraph using the  /u/group/hps/production/mc/MadGraph/wab/run_card_<ebeam>.dat
• output is an lhe file with each event being 1 wab event (
• cross section ~0is 0.7 barns, 6M events/s at 50 nA
• cuts: E(photon) > 50 MeV, |theta_y(photon)| > 10 mrad, no cuts on e-
• like the tridents, these files are also bundled 100-to-1 with:
• ./runjob_100to1.sh lhe/wab_merge_100to1.xml 1pt1 1 100

...

• moller electrons == "moller":  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/stdhep/mollers.xml
•  run with ./runjob.sh stdhep/mollers.xml 1pt05 <firstjob> <lastjob>
• the executable that does the event generation is /u/group/hps/production/mc/egs5/moller_v1.exe
• output is an .stdhep file with each event containing a moller pair (93% efficiency)efficiency) 
• cross section: 0.09 barns, 800k events/s at 50 nA (258 events per 10^8 incident e-)
• cuts: E > 10 MeV, |theta_y| > 10 mrad
  

Detector Simulation

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; they may also mix components first, such as with the beam overlay. Below is what we do for each sample type:

...

• moller events == “moller”
  
•  auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/slic/moller.xml
•  run with ./runjob.sh slic/moller.xml 1pt05 <firstnum> <lastnum>
•  runs slic over moller events, 1 moller pair per evenevent

Readout Simulation

Simulation of the SVT and ECal digital readout is performed using the hps-java framework.

...

• beam background readout == "(wab-)beam-tri"
  • auger xml:  /u/group/hps/production/mc/EngRun2015Scripts/recon/(wab-)beam-tri_<trigger>.xml<trigger> can be 'singles' (event occurs for each ECal cluster passing the cuts -> ~100k events) or 'pairs' (2 clusters on opposite sides pass the cuts within a time window -> ~1k events) 
  •  run with ./runjob.sh <auger xml> 1pt05 <firstnum> <lastnum> 
    
   
• enhanced tridents with beam background== “tritrig-beam-tri”
  •  auger xml: /u/group/hps/production/mc/EngRun2015Scripts/recon/tritrig-beam-tri_<trigger>.xml
  •  run with ./runjob.sh <auger xml> 1pt05 <firstnum> <lastnum>
    

...