Versions Compared

Key

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

Analysis

Main idea : Analyse CU beam test data to understand better the effect of GTCC and GTRC FIFO settings on tracker performance, and use the Monte-Carlo simulations to extrapolate the observed behaviour to the LAT in order to help for the determination of flight settings.

Results

See first analysis results in attachment : Presentation at SPS daily meeting September 14th

...

Currently, the Monte-Carlo cannot reproduce any dynamic effect (backpressure, dead
time), but it is possible to reproduce saturations of buffers setting GTCC buffer
size and the GTRC buffer size (even per each GTRC using an xml file). Default
settings in the Monte-Carlo are a buffer depth of 128 hits for the GTCCs and 64 hits
for the GTRCs.
e.s. : Although the monte carlo itself can't reproduce information about backpressure, dead time, and so forth, generating events with the monte carlo and then running those events through the test bed DOES generate precisely that information.

Real LAT data

The study of FIFO settings should also include two cosmic ray runs taken with the
LAT with special FIFO configuration :
+   ( GTRC limit is set to 14 and FIFO depth is set to 7 )
77004794: intSeApp_e2e_Other-TkrFifo1_0.17hr
77004795: intSeApp_e2e_Other-TkrFifo2_0.17hr

Documentation and presentations

Tracker Naming Convetions : LAT-TD-00376-01_TkrNaming.pdf
Leon's first study with the Monte-Carlo : Leon-2005March28-515GeVGammaEvents.pdf Leon-2005Sep12-Truncation.pdf
Hiro's work on LAT data : TKR-GTRC-buffer-limit.pdf