View - HEPHY

More documents

Recommendations

Info

Figure 5.10: The pattern test result view’s readout record browser, showing details ofa readout record with mismatching algorithm decision bits. The lowersection displays a GMT board record, and the tooltip shows the detailsof a regional muon candidate.69
6 Test Validation Using Cosmic EventsThe TestCell software was deployed to the CMS environment in September 2009,after an initial development period in Vienna. It quickly proved useful in verifyingpreviously known hardware defects and discovering new ones. Since the experimentwas at the time taking data from cosmic radiation, the interesting opportunity tolook for the consequences of undetected errors exists. This section will discuss someexamples and their consequences.6.1 Data/Emulator ComparisonThe primary tool for after-the-fact evaluation of the consequences of electronics errorsis the comparison between the results of the hardware - as recorded by the DAQreadout - and a reprocessing of the input values with the GT emulator.The process setup for the comparison between data and emulator results is verysimilar to the one used for pattern generation in Sec. 5.2.1. The setup of the CMSSWframework for this purpose is shown in Fig. 6.1. The two readout records obtainedfrom the data file and the emulator are compared by a framework analyzer, whichproduces a number of histograms on disagreements and errors encountered.Limits of data/emulator comparison for trigger decisionsWhile this form of validation is a very powerful tool, it is not perfect. First, there isthe obvious bias inherent in looking only at data recorded by the experiment - eventsthat were erroneously missed by the trigger will never make it to the input dataset andwill therefore not be noticed. In practice, this is mitigated by the fact that there areusually multiple independent trigger criteria, so that some subsets of the errors willshow up because algorithms not affected by the malfunction will still select the event.Second, due to the fact that the readout only contains the algorithm decision wordafter prescaling has been applied, it is difficult to interpret disagreements on prescaledalgorithms. Running the trigger emulator with prescaling disabled allows an error tobe flagged when the emulator does not match an emulator and the hardware does, butfor the converse, it is impossible to distinguish locally whether there is a malfunctionor the prescaling suppressed the bit. Even statistical interpretations are complicatedby the interaction of multiple prescalers and trigger masks.70
Page 5 and 6:
3.2.10 CMS Online Software . . . .
Page 7 and 8:
factor. The selected events are the
Page 9:
Figure 2.1: Expected dijet mass spe
Page 12 and 13:
Figure 2.3: Left: Dilepton mass dis
Page 14 and 15:
W −Z, γZ, γZ, γW +Z, γFigure
Page 16 and 17:
ggHVHg(a)g(b)q¯q¯qHHV ∗q(c)qq(d
Page 18:
Events per 4 GeV bin450400350300250
Page 21 and 22:
3 Experimental Setup3.1 Large Hadro
Page 23 and 24: 8.3 T. Such high fields were not ac
Page 26 and 27: luminosity) and limited storage ban
Page 28 and 29: Figure 3.4: Layout of the CMS pixel
Page 30 and 31: Figure 3.6: Transverse section illu
Page 32 and 33: Figure 3.8: HCAL jet energy resolut
Page 34 and 35: staggered by a half-cell each. A dr
Page 36 and 37: acceptance signal is distributed to
Page 38 and 39: Figure 3.11: Generic state machine
Page 40 and 41: Figure 3.12: Components of a CMSSW
Page 42 and 43: 40 MHz Pipeline, Latency < 3.2 µsC
Page 44 and 45: In addition, the GCT calculates a n
Page 46 and 47: Figure 4.4: η boundary between the
Page 48 and 49: Figure 4.5: Organization of the DTT
Page 50 and 51: Condition Type Subtype Parametersmu
Page 52 and 53: oards making up the GT and sends th
Page 54 and 55: • ESProducers: components that re
Page 56 and 57: 5 Pattern Testing for the Level-1 G
Page 58 and 59: the required processing is mostly c
Page 60 and 61: RAW DIGIL1GctJetCandCollection (for
Page 62 and 63: information about an event that is
Page 64 and 65: muons 2 or two PSB channels (named
Page 66 and 67: 5.3 Software ImplementationThe exec
Page 68 and 69: tsframework::CellOperationTestOpera
Page 70 and 71: system. Each subsystem maintains it
Page 72 and 73: Test Execution PanelThe test execut
Page 76 and 77: FEDRawDataCollectionL1GlobalTrigger
Page 78 and 79: Figure 6.3: Result of a Function Te
Page 80 and 81: Figure 6.6: Disagreements in e/γ a
Page 82 and 83: Figure 6.9: TestCell output from an
Page 84 and 85: Bibliography[1] Abraham Pais. Inwar
Page 86: f880c6bdfaf56c65fb10dd89a52019d8cf1
show all

View - HEPHY

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?