130 likes | 292 Views
GCT Software ESR - 10th May 2006. Jim Brooke. Overview. External component. Arrows are in client-server direction. Conditions DB. GCT specific. GCT Monitor. CMSSW. Trigger Supervisor. GCT GUI. GCT Emulator. Config DB. GCT Controller. XDAQ. XDAQ. Source Card Controller. python.
E N D
GCT SoftwareESR - 10th May 2006 Jim Brooke
Overview External component Arrows are in client-server direction Conditions DB GCT specific GCT Monitor CMSSW Trigger Supervisor GCT GUI GCT Emulator Config DB GCT Controller XDAQ XDAQ Source Card Controller python Test scripts Test scripts python GCT Driver Source Card Driver USB HAL/CAEN Source Cards Concentrator Card Jim Brooke, 10th May 2006
Emulator • Bit level simulation of the GCT processing • Monte-Carlo production • Hardware verification & debugging • Requirements • Run standalone or within CMSSW • File I/O or CMSSW event • Fpga-level modularity • Standalone firmware tests, event record flexibility • Produce LUT contents • Additional CMSSW components • GCT digi definitions • GCT event record unpacking; raw to digi conversion Jim Brooke, 10th May 2006
L1Trigger/GlobalCaloTrigger Processing units L1GctElectronSorter L1GctElectronFinalSort L1GctJetFinder L1GctWheelJetFpga L1GctJetFinalStage L1GctWheelEnergyFpga L1GctGlobalEnergyAlgos Internal trigger objects L1GctJetCand L1GctEmCand Framework classes L1GctSourceCard L1GctEmLeafCard L1GctJetLeafCard L1GlobalCaloTrigger Helper classes L1GctEtScales L1GctMap Ready (for 1st release) Underway Not started Emulator classes Jim Brooke, 10th May 2006
Resources Jim Brooke (25%), Rob Frazier (50%), Greg Heath(25%), Maria Hansen (50%) Status Main processing algorithms written and most ‘glue code’ complete 1st version ‘digis’ committed to DataFormats/GctDigi Integration with CMSSW underway Plans Produce stable code for validation Validate with Monte-Carlo Validate firmware against emulator Milestones June 06 : 1st release for validation Emulator Jim Brooke, 10th May 2006
GCT Driver HAL-based API for hardware access Object model of the hardware VME64x slave in each FPGA Register read/write Buffer access LUT access Python wrapper Test scripts Command prompt… Test Scripts Basic hardware/firmware tests Link tests Initial integration tests In-situ tests use Trigger Supervisor GCT Controller XDAQ wrapper around Driver Functionality : Initialise system Load LUTs Report system status Run tests In-situ debugging Capture event record External interfaces : Trigger Supervisor Config DB GUI Embedded python interpreter Mainly used for initialisation Control & test Jim Brooke, 10th May 2006
Source Card Driver Based on existing code at Imperial College Need to move this to CMS trigger repository Allows standalone testing 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 application around Driver SOAP interface to GCT Controller Functionality Retrieve captured data for in-situ readout of RCT output Control & test (Source) Jim Brooke, 10th May 2006
Control & test • Resources • Rob Frazier (100% from 1st July), Jim Brooke (20%) • Status • Work due to start after 5th June • Adapt code from old project to the new hardware • Many of the design problems solved • Need to encapsulate new hardware/firmware structure • Write new routines for different firmware (eg buffers) • Integrate with TS, Cond DB • Work started in old software • Milestones • Oct 06 : ready for Source/Leaf/Concentrator integration • Feb 07 : ready for Electron trigger integration Jim Brooke, 10th May 2006
Requirements Verify hardware processing Online/offline DQM Diagnostics Record to Cond DB GCT Monitor (library) Several applications Standalone debugging HLT farm Trigger online farm (?) Offline DQM Input is GCT event record From DAQ or GCT controller Contains all inputs and outputs Functionality Hardware verification Run on all triggers… Compare emulator with hardware Verify link checksums Produce as much diagnostic output as possible! DQM Use various subsets of triggers Occupancy plots of all objects by , , Et, module, crate Compare trigger data with full detector data etc… Send summary information to Cond DB Monitoring Jim Brooke, 10th May 2006
Monitoring • Resources • Alex Tapper (50%), Jim Brooke (20%), Greg Heath (25%) • Status • Start work after 5th June (Emulator release) • Run emulator in CMSSW DQM framework • Add diagnostic functions • Add histograms etc. • Include functionality in line with hardware schedule • Integration with RCT, electron triggers, jet triggers • Some discussion required • Standalone tests • Milestones • Oct 06 : ready for Source/Leaf/Concentrator integration • Feb 07 : ready for Electron trigger integration • Jun 07 : ready for Jet trigger integration Jim Brooke, 10th May 2006
Schedule (2006) Sept July Aug Oct Nov Dec June Jim Brooke, 10th May 2006
Schedule (2007) Jim Brooke, 10th May 2006
Milestones Jim Brooke, 10th May 2006