GCT SoftwareJim Brooke.ppt

1、GCT SoftwareJim Brooke,Internal Review - 29th March 2005,Jim Brooke, 29th March 2005,Overview of GCT software Requirements for each component Only partially complete Some design details Status & plans Schedule, milestones GCT Wiki : https:/uimon.cern.ch/twiki/bin/view/CMS/GlobalCaloTrigger,Jim Brook

2、e, 29th March 2005,HAL/CAEN,Control and Test,GCT Driver,GCT GUI,Trigger Supervisor,Config DB,Test scripts,USB,Concentrator Card,Source Cards,Source Card Driver,Source Card Controller,GCT Controller,python,GCT Monitor,External component,GCT specific,?,Arrows are in client-server direction,GCT Emulato

3、r,python,Test scripts,XDAQ,XDAQ,CMSSW,Conditions DB,Jim Brooke, 29th March 2005,Processing Crate,GCT Driver HAL-based API for hardware access Object model of the hardware VME64x slave for each FPGA Register read/write Buffer access LUT access Other functions to be discussed Python wrapper Test scrip

4、ts Command prompt,GCT Controller XDAQ wrapper around Driver Functionality : Initialise system Report system status Run tests In-situ debugging? Output Monitoring data? SOAP interfaces : Trigger Supervisor Config DB transactions GUI Conditions DB ? Embedded python interpreter Mainly used for initiali

5、sation,Jim Brooke, 29th March 2005,GctDriver,GCT Driver,VmeDevice,HAL,read() write() readBuffer() readEvent(),read() write() blockRead() blockWrite(),read() write() readBuffer() readEvent() loadEtLUT(),Jim Brooke, 29th March 2005,GCT Controller,XDAQ,GctController,GctDriver,python,SOAP interface,Trig

6、ger Supervisor : init(key) run() getStatus(),TS Cell,Conditions DB : getConfig(key),GUI : getStatus(),SC Controller : getEvent(),Jim Brooke, 29th March 2005,Source Cards,Source Card Driver Based on existing code at Imperial College Need to move this to CMS trigger repository Allows standalone testin

7、g Serdes loopback/test ctrl & buffer readout Read serdes status Pattern generation Input capture buffer readout Include python wrapper Allows main GCT controller to run a script to eg. start test mode,Source Card Controller XDAQ Executive wrapper around Driver SOAP interface to GCT Controller Functi

8、onality Retrieve captured data for in-situ readout of RCT output Additional functionality for discussion How many PCs control the Source Cards?,Jim Brooke, 29th March 2005,Monitor,Original plan : Monitor runs in XDAQ Retrieves captured trigger data (via Controller or DAQ) Run emulator and compare Mu

9、st also monitor non trigger data Eg Link status bits, checksums, Histogram, plot, However : CMSSW DQM framework provides access to DAQ data Need to write GCT DQM application anyway Relies on DAQ What are our standalone monitoring requirements? Preferably, we have none Define DAQ packet data content

10、to proceed with DQM app Minimal content to be defined soon as part of Emulator work Send summary data to Conditions DB (?),Jim Brooke, 29th March 2005,GCT Emulator,Library within CMSSW (CMS simulation and reconstruction) L1Trigger/GlobalCaloTrigger Used in Monte-Carlo simulation of CMS - needed soon

11、! Hardware verification (Another) object model of the hardware Includes classes for algorithms and data types, as well as cards and FPGAs Write stand-alone test programs for algorithms For software unit-testing For early verification of firmware (need to define file formats),Jim Brooke, 29th March 2

12、005,GCT Emulator,Jim Brooke, 29th March 2005,Status and Plans,Emulator (JB, GH, MH, RF, AT) Version 0.1 almost complete Algorithm classes provide some output Wheel and Concentrator not modelled (maybe never required?) Some file I/O provided to verify algorithm emulation Version 0.2 Valid output to G

13、T and DAQ (1st version DAQ content) Integration with RCT (if available - nothing committed yet!) Integration with CMSSW event model ? Verification of hardware? (standalone tests) Version 1.0 Algorithms verified with simulated physics events Integration with rest of L1Trigger Discussion urgently requ

14、ired in order to inform planning,Jim Brooke, 29th March 2005,Status and Plans,GCT Driver / Controller / GUI (JB, RF) Can treat code for old GCT as v0.1 Start work on these simultaneously when effort free after Emulator v1.0 released Specification GCT Driver functionality reasonably clear Need to def

15、ine test functionality of GCT Controller in detail GCT GUI functionality totally unclear! Write (and then maintain) a set of specification documents GCT Monitor (JB, AT) Start work after Emulator v1.0 released Run Emulator in CMSSW DQM framework Aim to have basic monitoring in place by end 2006 To f

16、acilitate debugging as soon as required,Jim Brooke, 29th March 2005,Summary of Questions,Need to define the software requirements for testing/integration/commissioning After initial verification of algorithm firmware We use stand-alone test programs with file I/O Before full system verification We u

17、se the data sent to the DAQ Plan to learn from experience of other trigger sub-systems Currently ramping up to pattern tests What do we need from the GUI? Do we need a GUI at all? Run tests from Trigger Supervisor - expect minimal debug output What expert debugging tools do we want? Specification documents required Progress slow (PTDR v2, Emulator for CSA2006),Jim Brooke, 29th March 2005,Schedule,Proposed milestones (some new) Emulator v1.0 release Source Card Driver ready to integrate 1 SC with 1 RCT crate So