This page lists the public plots illustrating signal read-out studies.

Signal Read-Out

Compressed Fragment

Distribution of the Tile Calorimeter Read-Out Driver (ROD) fragment sizes (32 bit words) for Pb+Pb √sNN = 2.76 TeV Heavy Ion collisions data (run 169627, Lint= 1.35 mb-1, 847 events, 64 fragments per event). The bandwidth limit for 100 kHz L1 Trigger rate is 398 words. It should be noticed, that the maximal ROD fragment size in this distribution is 87% of the bandwidth limit. (Link to CDS record).

eps version of the figure
Maximal average bandwidth load distribution for TileCal Long Barrel (LB). √s = 7 TeV p-p collisions data (run 189280, express stream, Lint=3030 nb-1, μ=15.5, 10069 events with the bandwidth threshold of 6 ADC counts). For each of 32 Tile ROD (Read-Out Driver) fragments produced by 16 Long Barrel RODs, the moving average of fragment sizes over 16 consecutive events is calculated and the maximum of the 32 is selected.
Red lines - Reco+Frag1: Threshold Smax – Smin > 6 ADC counts;
Blue lines - Frag5: extrapolation for all raw data;
Solid lines - runs with the current version of software;
Dashed lines - evaluation for the same runs with the upgrades currently under way (Sep 2011).
The bandwidth limit for 100 kHz L1 Trigger rate is 398 words. (Link to CDS record).
eps version of the figure

Fragment 1 size

Size of Read-Out Link (ROL) fragments containing data from four Tile Super Drawers for 7 TeV pp collisions data ( Run number 191190) at a peak luminosity of 3.5 x 1033 cm-2 s-1. The size is computed as the average of eight consecutive events corresponding to the Read-Out Drivers (ROD) output buffer in a worst scenario of having consecutive events belonging to the JetTauEtmiss data stream, in which TileCal shows the highest occupancy above noise threshold. The bandwidth specification of the ROD output link defines a maximum fragment size depending on the Level 1 trigger rate. The dashed lines show the maximum fragment size for 100 kHz (in red) and for 75 kHz ( in blue). The top plot is the distribution of fragment size per ROL with the present dataformat where selected samples ( channels with (Smax-Smin) > 6 ADC counts) are directly copied as received from the front-end electronics . The bottom plot shows the same distribution for a dataformat where the selected samples are compressed. The ROL index [0,31] correspond to the Long Barrel and the ROL index [32,63] to the Extended Barrels. These plots shows that the Tile Hadronic Calorimeter is already capable of running with present LHC conditions at a Level 1 trigger rate of 75 kHz and at 100 kHz with the new dataformat. (Link to CDS record)

Major updates:
-- PawelKlimek - 2016-08-23

Responsible: PawelKlimek
Subject: public

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formateps Frag5_ROD_FragSize_169627.eps r1 manage 9.7 K 2016-08-23 - 19:02 PawelKlimek  
PNGpng Frag5_ROD_FragSize_169627.png r1 manage 18.1 K 2016-08-23 - 19:02 PawelKlimek  
Unknown file formateps FragSize_new_Final.eps r1 manage 39.8 K 2016-08-23 - 19:05 PawelKlimek  
PNGpng FragSize_new_Final.png r1 manage 19.0 K 2016-08-23 - 19:05 PawelKlimek  
Unknown file formateps FragSize_old_Final.eps r1 manage 58.5 K 2016-08-23 - 19:02 PawelKlimek  
PNGpng FragSize_old_Final.png r1 manage 21.4 K 2016-08-23 - 19:02 PawelKlimek  
Unknown file formateps maxLB_aver16_ROD_FragSize_189280.eps r1 manage 12.3 K 2016-08-23 - 19:02 PawelKlimek  
PNGpng maxLB_aver16_ROD_FragSize_189280.png r1 manage 18.3 K 2016-08-23 - 19:02 PawelKlimek  
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2016-08-24 - PawelKlimek
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback