View - HEPHY

More documents

Recommendations

Info

5.3 Software ImplementationThe execution of the tests described in the previous section requires access to boththe GT and GMT hardware. Since GT and GMT are already represented in theTrigger Supervisor deployment of CMS as two cells running on the machine connectedto the GT crate, it was natural to implement the testing system using the sametechnology. This is especially important for the goal of testing in conditions as closeas possible to those of actual operation. Thus, the user interface and logic of thetesting process was implemented as another Trigger Supervisor cell called the TestCell,which communicates with the subsystem cells using the TS framework mechanisms,principally by calling commands for hardware access.5.3.1 User Interaction ConceptOne of the key requirements of the TestCell project was to make it very easy to verifycorrect operation of the system. For this reason, the execution of a test had to bemade as foolproof as possible to allow non-experts to run such tests. For the functiontests at least, the selection of a correct test configuration is not exactly trivial sincethe generated inputs need to match the hardware configuration in points such as thescales and trigger menu used. This led to the introduction of the concept of a testspecification, which contains all the parameters necessary to execute a test. Whilethe creation and maintenance of test specifications is an expert task, the step of testexecution simply requires the user to select a test specification and press a button inthe user interface. The system then executes the tests and provides a summary verdictthat makes it easy to identify whether the test has succeeded. If errors have occurred,the application should also help experts analyze the problem. Since the errors arenot necessarily reproducible, the application allows users to save a test result afterexecution. These results can then be reviewed by experts to pinpoint the source ofthe problem.These three separate concepts result in the basic separation of the user interfaceinto three TS panels - the Test Specification Panel, the Test Execution Panel and TestResults Panel.5.3.2 Object ModelThe object model for the TestCell is designed to be extensible. To this end, the celllogic operates on an abstract object model (shown in Fig. 5.4) where each type oftest is represented as a TestCategory object. A TestCategory provides the centralinterface needed to specify, execute and analyze tests of that method. The followingobjects need to be provided for each type of test:• A TestSpecification provides all the input information required to execute atest.• A TestOperationBase instance is a TS operation that implements actual executionof the test. Its finite state machine is shown in Fig. 5.5.61
TestCategoryname: stringdescription: stringcreatescreatescreatesTestOperationBaseTestResultBrowserproducescreatesTestSpecificationEditorcreatesTestResultname: stringexecuted: timestampsummary: stringhardwareInfo: stringbelongs toTestSpecificationname: stringdescription: stringcreated fromFigure 5.4: Abstract object model for a test category.setupHaltedprepareReadyanalyzePreparedsummarizeDoneexecuteExecutedFigure 5.5: Finite State Machine for the generic test operation.62
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 68 and 69: tsframework::CellOperationTestOpera
Page 70 and 71: system. Each subsystem maintains it
Page 72 and 73: Test Execution PanelThe test execut
Page 74 and 75: Figure 5.10: The pattern test resul
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

Create successful ePaper yourself

Delete template?

Save as template?