next up previous contents
Next: Commands that query the Up: Commands that control the Previous: Commands that control the

In run mode DSIM

  1. HIT_JITTER or /EOSG_GEANT/RUN/HIT_JITTER X_CHAR


    tabular553

    This command determines if the resolution effects are added to the hit positions returned from GEANT. If ON the x and y positions returned have a Gaussian distributed random number (with tex2html_wrap_inline2340's determined by DX and DY in the routine GUOUT_SMDATA) added to them to mimic the resolution of the TPC. If a hit is outside the TPC's active volume after jittering, the hit position is moved to the closest point within the active volume.

  2. HIT_MERGE or /EOSG_GEANT/RUN/HIT_MERGE X_CHAR


    tabular553

    This command determines if the GEANT hits in the TPC are merged before being output. If ON then hits that are close to other hits are merged into a single large hit (``cluster''). If the size of the cluster is small enough, it is output as a single hit. Note that merging is done after hit ``jittering'' (if jittering is enabled).

  3. HIT_SCALE or /EOSG_GEANT/RUN/HIT_SCALE X_CHAR


    tabular553

    This command determines if the tex2html_wrap_inline2342 values are scaled before being output. The formula used to scale the values is tex2html_wrap_inline2344, and is used to match the Monte Carlo's energy calibration to the TPC's calibration, so that the normal PID routines may be used. Note that the scaling is applied after merging, and/or jittering (if either is enabled).

  4. HIT_THRESHOLD or /EOSG_GEANT/RUN/HIT_THRESHOLD X_CHAR


    tabular553

    This command determines if a threshold is applied to the hits before being output. To mimic the TPC's threshold, a threshold on the tex2html_wrap_inline2342 of the particle (while above a pad row) can be applied. Note that the threshold cut is applied after merging, jittering, and/or scaling (if any of these are enabled).



E895 common account
Wed Aug 6 16:32:35 EDT 1997