You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Major Changes

  • Use Pattern Recognition in addition to GEANT model to determine which tiles and ribbons to associate with tracks
    • This allows us to handle near misses, which is needed to do efficiency studies
  • Have information be associated with tracks, instead of having a single big set for the whole event
    • This makes using the event display much easier
    • This makes getting access to information in Recon root files easier
  • Handle track errors correctly
    • This wasn't being done before
    • This looks nice in the event display
  • Sort ACD - track associations by a combined signal size/ distance quality measure instead of using only distance
    • This gets rid of problems with shadowing, where one association with a small signal masked another nearby one with a larger signal
  • Always calculate gaps to tiles
    • Before this was a hodge podge, we had to handle cases where the track hit ribbons, tiles and missed everything differently.
  • Sort gaps by the probability that the track went into the gap, including the size of the gap and the error projection
    • Before gaps were sorted only by the distance to the gap

  Minor Changes

  • 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="5258bba0-ffa0-468d-88c7-ccf56e9b45e2"><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="a9fa619e-42b5-4013-81d5-9e7bcf892f26"><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



AcdTkr1ActiveDist:  
All Events

Combination of 3 effects:

  1. Selection of which associtation to use
  2. DOCA calculation for case where doca occurs at head of track
  3. Entries lost b/c sigma > 10000 (stripe at -2000)

AcdTkr1ActDistTileEnergy:
All Events:

Combination of 2 effects:

  1. Selection of which associtation to use 
  2. Entries lost b/c sigma > 10000 (stripe at -2)

AcdTkr1ActiveDist:
 Events where POCA occurs above track



This shows the selection effect from moving from the largest active distance
to the combination of active distance, error projection and signal size.



AcdTkr1ActiveDist:
Events where POCA occurs at track start

Combination of 2 effects:

  1. DOCA calculation for case where doca occurs at head of track
  2. Entries lost b/c sigma > 10000.  (stripe at -2000)

Acd2Tkr1ActDistTileEnergy v Acd2Tkr1ActiveDist:
Events where  AcdTkr1ActiveDist > 0 and
Acd2Tkr1ActiveDist: !=  AcdTkr1ActiveDist

This plot shows that for events where AcdTkr1ActiveDist was positive the new
selection picks a solution that is either positive or very close to zero and with a large
energy deposit 


  Changes in the AcdTkr1RibbonActDist set of variables

Variable

Plots

Comments

AcdTrk1RibbonActDist

Combination of two effects:

  1. Lots of associations with larger miss distances lost because they occur behind the head of the track.
  2. A small number of events have different ribbon selected because of the change in ordering

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ba76ec49-6d52-4aab-acfd-cda55180a529"><ac:plain-text-body><![CDATA[

AcdTrk1RibbonActEnergyPmtA[B]

!AcdRibbonActEnergyPmtA.gif

thumbnail!

Combination of two effectos:]]></ac:plain-text-body></ac:structured-macro>

  1. Lots of associations with larger miss distances lost because the occur behind the head of the track.
  2. A small number of events have different ribbon selected because of the change in ordering.

 Changes in the AcdTkr1RibbonDist series of variables

Variable

Plot

Comment

AcdTkr1RibbonDist

Most of the results are identical.  The differences come from cases where the distance was previously calculated w.r.t. the ribbon and is now being calculated w.r.t a tile that was just missed.   Since the ribbons are slightly offset from the plane of the tiles, tracks at high incidence angle can hit ribbon while passing 30 mm or more inside the tile

 Changes in the AcdActiveDist3D series of variables

Variable

Plot

Comments

AcdActiveDist3D

Combination of 3 effects:

  1. Selection of which associtation to use
  2. DOCA calculation for case where doca occurs at head of track
  3. Entries lost b/c sigma > 10000 (stripe at -2000)

AcdActiveDistTileEnergy

 

AcdActDistTrackNum

 

 Changes in the AcdRibbonActDist series of variables

Variable

Plot

Comment

AcdRibbonActDist

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c3c8960a-1d96-4728-b202-6f2d9152268f"><ac:plain-text-body><![CDATA[

AcdRibbonActEnergyPmtA[B]

!AcdRibbonActEnergyPmtA.gif

thumbnail!

 

]]></ac:plain-text-body></ac:structured-macro>

 Changes in the AcdTkrRibbonDist series of variables

Variable

Plot

Comment

AcdTkrRibbonDist

 
  • No labels