Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.   An start on one such study is here.
    • More detailed description of pattern recognition technique is here
  • 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
    • More information about new ACD recon data structures is here
  • Handle track errors correctly
    • This wasn't being done before
    • This looks nice in the event display
    • More information about error propagation is here
  • 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
    • More information about quality measures is here
  • 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.
    • More information about how we treat gaps is here
  • 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

In the process of  doing all this work a couple of smaller improvements presented themselves:

  • 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

  New information in Merit ntuple

  We wish to add some new information to the Merit Ntuple.  Mainly this is information about the combined signal size and track projection estimator of how likely a given tile is to veto a track.   

  Noticable changes in existing Merit quantities

...

  1. We changed the way the "best" track-tile, track-ribbon and track-gap associations are selected.   This causes some small fraction of the events to have changes in a couple of merit variables.   The effects are different various cases.  Here is a page that summarized the effects.
  2. We change the way we report the point of closest approach when it occurs at the head of the track.  This affects tracks near the sides an top of the LAT with high incident angles w.r.t. the tiles or ribbons.  Here is a page that describes this in more detail.
  3. We use the hardware veto bit directly to count hits in the various parts of the ACD.  Before we were using the signal size that was equivalent to the intended veto threshold.  This causes a few events to move around in the various counting variables.
  4. We set an upper limit of 10000 sigma for all associations.   This causes a few events with large negative active distances to return to the default values of -2000.

  Effects on background rejection

...

Here is a page that describes how this information is visualized in the event display.

 Path Path towards deployment

Here is a page that describes the issues with and suggests a path towards deploying this stuff 

...

Variable

Plot

Pass7?

AcdTileCount
(also AcdNoRow3Readout):

(tick)
( (error) )

AcdRibbonCount:

(error)

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="69dbe4733083b553-57fd249f-4f5d440d-a69ebd7b-683820ff4efe61231d1d9b1b"><ac:plain-text-body><![CDATA[

AcdTileEnergy
(also AcdEnergyTop, AcdEnergyRow[0-3]):

!AcdTotalEnergy.gif

thumbnail!

(error)
( (tick), [0,2,3] (tick) )

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

AcdRibbonEnergy:

(error)

AcdCornerDoca:

(tick)

AcdTkr1CornerDoca:

(tick)

...

Variable

Plot

Pass7?

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4fa56d4ef3f00b75-0094d0c4-44ec4124-a8088909-19720acd1514139b06dd00dc"><ac:plain-text-body><![CDATA[

AcdNoTop
(and AcdNoSideRow[0-3]):

!AcdNoTop.gif

thumbnail!

(error)
( (error) )

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

...

Variable

Plots

Pass7?

Comments

AcdTrk1RibbonActDist

(tick)

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="defb75545448cb1b-00b4ad51-4d8c41fe-82b5a52d-f47c04b052d084653615558b"><ac:plain-text-body><![CDATA[

AcdTrk1RibbonActEnergyPmtA[B]

!AcdRibbonActEnergyPmtA.gif

thumbnail!

(tick)[(tick)]

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.

...

Variable

Plot

Pass7?

Comment

AcdRibbonActDist

(error)

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b88ada70b4db2251-d13be4d2-4b5c49b5-a9fdb759-08c86072f2137a7ba3b6c258"><ac:plain-text-body><![CDATA[

AcdRibbonActEnergyPmtA[B]

!AcdRibbonActEnergyPmtA.gif

thumbnail!

(error)[(error)]

 

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

...