To run MC the 'official' way using scripts, please see 2015 MC Production Using Scripts.

...

This assumes that you have access to /u/group/hps/hps_soft, which should be accessible from both the CUE environment and ifarm, or else somewhere wherever where stdhep, SLIC, and hps-java are built, using the instructions here: Software Installation

SLIC

SLIC takes .stdhep files as input. If you have .lhe files that you want to process (usually tridents or A' signal), it may be better to use an existing script for this step, or else contact Brad Bradley Yale for instructions (btu29@wildcats.unh.edu).

...

If the exact number of events in the file is unknown, using any large integer (but not a 'long'!) higher than the expected number of events will successfully process all the events of them without error.

Readout

The following steps simulate readout, which defines things like trigger response and prescaling taken from a steering file.

Note: If using a detector with a fieldmap, then a symbolic link to the fieldmap directory must be made, if not done already (see previous section).

1) Before the actual readout, the events from SLIC output will first need to be spaced out to simulate pileup:

...

where ${hps-java} = /u/group/hps/hps_soft/hps-java/hps-distribution-3.4.1bin.jar

'hps-distribution-bin.jar' links to whichever jar in the 'hps-java' directory is most recent (this can of course be changed),

or whichever jar you want to use, and
${steering} = EngineeringRun2015TrigSingles1_Pass2.lcsim
or whichever customized readout steering file you want to use.

If you want to use your own steering file other than the release version for anything in the readout or recon steps, replace
"-r /org/hps/steering/recon/${steering}"
with
"-f /path/to/your/${steering}" without the '-r' flag.

The run number can also be replaced.

The "-DdisableSvtAlignmentConstants" is there because using SVT alignment constants from the database will technically change the detector geometry from what it is defined to be from the .lcdd file, and may cause a crash.

Reconstruction

1) Finally, recon is run using:

java OLD WAY: java -DdisableSvtAlignmentConstants  -XX:+UseSerialGC -Xmx500m -jar ${hps-java} -r /org/hps/steering/recon/${steering} -i {in}.slcio -DoutputFile={out} -Ddetector=${detector} -Drun=5772
New Way:   java -DdisableSvtAlignmentConstants  -XX:+UseSerialGC -Xmx500m -jar ${hps-java} -r /org/hps/steering/recon/${steering} -i {in}.slcio -DoutputFile={out} -d${detector} -R5772

To make a DST using the recon output:

source /u/group/hps/hps_soft/setup_dst.csh

/u/group/hps/hps_soft/hps-dst/build/bin/dst_maker {in}.slcio -o {out}.root

'hps-dst' is linked to the latest version of the dst_maker.

Note: If using an HPS jar before GBL was integrated into the trunk, then a '-g' switch must be added to the command in order to include GBL tracks in the resulting DST file, and also a flag to set the correct magnetic field for 1.056 GeV running.

i.e. "dst_maker {in}.slcio -o {out}.root -g -b .24"