...
- Change the way the distance of closest approach is calculated when the POCA occurs exactly at the head of the track
- This effects some events track which graze side tiles (and a very few which graze to tiles), but only when the distances of closest approach is quite large
- Use the hardware veto information instead of the energy information in counting number of tiles hit in the Merit Variables
- This handles issues with the slower timing of the PHA electronics
Testing and Comparison
Merit Variables that stayed exactly the same
Variable | Plot | |||
---|---|---|---|---|
Acd Tile Count (also AcdNoRow3Readout): | | |||
AcdRibbonCount: |
| |||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d04a2e6c-b627-4e25-b83c-80a9eef19c4c"><ac:plain-text-body><![CDATA[ | AcdTileEnergy (also AcdEnergyTop, AcdEnergyRow[0-3]): | !AcdTotalEnergy.gif | thumbnail! | ]]></ac:plain-text-body></ac:structured-macro> |
AcdRibbonEnergy: |
| |||
AcdCornerDoca: |
| |||
AcdTkr1CornerDoca: |
|
Variables that changed slightly because we are using the hardware veto to count hits instead of the Energy corresponding to an expected veto
Variable | Plot | |||
---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3e8a0009-51b5-4ecd-a962-c06f61c5d3d8"><ac:plain-text-body><![CDATA[ | AcdNoTop (and AcdNoSideRow[0-3]): | !AcdNoTop.gif | thumbnail! | ]]></ac:plain-text-body></ac:structured-macro> |
Changes in the AcdTkr1ActiveDist set of variables
Variable | Plot | Comments |
---|---|---|
|
| Combination of 3 effects:
|
AcdTkr1ActDistTileEnergy: |
| Combination of 2 effects:
|
AcdTkr1ActiveDist: |
|
|
|
| Combination of 2 effects:
|