Versions Compared

Old Version 3

changes.mady.by.user Luca Latronico

Saved on

compared with

New Version Current

changes.mady.by.user Luca Latronico

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

NB: these are unedited notes

Sparse notes from morning session

  • Ghosts
    • look into CAL trigger info, probably only for high energy ghosts: it may be possible to look for a missing CAL-HI primitive
    • slide 14: yellow layers are inferred ghosts, i.e. layers that did trigger, while the other blue layers did not trigger (but had a request either in the TEM diagonistics or from a 3-in-a-row)
    • slide 16, comment from Bill: might be a residual activation from exiting the SAA, check with Neil Johnsono about average energy expected from such events; Eric/Luca: we have indications of such activations from several monitoring plots, found specific quantitites that display such behaviour
    • on ghosts from CAL (Steve): can we get ghosts in CAL by looking at the inconsistency between the readout energy and the selected readout range (e.g. an out of time ghost whose signal decays in time and latched a higher energy readout range)
  • CR Tracking
    • essentially available in GR; Leon: need to think about restructuring, we now have different type of tracks and need to decide which to present to subsequent steps; Bill: need to work on the ED too; Eric: need to find a way not to step on each other, like a key system in the TDS; Tracy: easy to do, need to change the track list from a vector to a map; Eric: need to change ACDValTools accordingly, it does not currently know about this. Leon: implementation issue, need to talk over this; Philippe: do we have a hint of how oftern this finds a new track? Bill: not really; Leon: it should find the same ghosts tracks that we find; Leon: there is a sense that adding all this will slow down recon, but it may not be so, since, e.g. tracks that are found by the CR tracking may not have to be reconstructed by the gamma track finder
  • Tree-based Track fitting
    • processing time for combo pat rec (current) is artificial and determined by choices in recon that limit the combinatorics
    • slide 25: currently no mechanism to merge two trees, so in the case of a photon converting high up the Tree-based track fitting misses the direction; Luca B: any bias from the method with the angle? Bill: namenly which method has a larger fish-eye effect?
      Bill: I b=think ultimately this approach will impact much the bkg rejection, since it gives a full picture of the shower develpoment, so I don't expect too much improvement on the PSF, but we can think to many metrics of the tree we can move to CTs to train them; incidentally, our bkg rejection sufffer at high energy, which is where this tool works best
  • PSF/Eric: I would say this is most you can do with Merit; Luca B: I scanned some 100s events, high energy photons > 5-10 GeV, and compared residuals of the TKR direciton vs the CAL direction, and found a better picture wrt my expectations, need to check; you do not need to scan many events where 1/2 xtal in the cal screw direction and centroid; Eric: this is not an effect of isolated xtals that pull the centroid, we are talking about longitudinal position being off and impacting the centroid measurement
    Eric: this plot tells me it is a matter of longitudinal position, things are fine in the middle of a tower, when you move closer to twr boundaries data and MC disagree more
    Toby: we should start always specifying what happens for Front and Back PSF separately
  • CTBCORE: this is mostly related to Pass7, but I want to discuss it here since we will have to face similar validations for Pass8.

Notes from afternoon Tagup

  • discussed more specific developments this morning, will need to think about knitting all these together
  • Tracy managed to compile Geant4 v9.3 in GR!
  • BT paper: Luca and Philippe discussed plans for the BT paper; it would be worth working on the results on energy scale from Melissa and on issues related to longitudinal CAL position measurement (aka CTBCORE issue) using BT data and try to add them to the paper; we think this would make the BT paper more interesting as opposed to just compiling a summary of quite old results and state conclusions unrelated to the LAT calibration
  • Leon: started scanning a skim of periodic trigger events with some people (Philippe, Luca B, Johan?) and found them to belong to two piles: 1 has an energy release consistent with MIPs, which is surprising, the other has completely uncorrelated tracks and energy deposits in the CAL - investigations are ongoing
  • several people installed and started workin on TMine (Steve, Luca L ?..) , and initiated discussions with developers (Eric, Alex)
  • discussion about CAL longitudinal position calibration: Sasha reports it is currently not applied as it requires a special handling a layer7 (question), since it has low stat; Eric and Sasha report that there we are currently using the same identical calibration for MC and recon, which implies that systematics from the real CAL are not in the MC and its response is bound to be better