1 / 14

GCT Software Jim Brooke

GCT Software Jim Brooke. Internal Review - 29 th 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.

finola
Télécharger la présentation

GCT Software Jim Brooke

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GCT SoftwareJim Brooke Internal Review - 29th March 2005

  2. 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 Brooke, 29th March 2005

  3. Control and Test 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, 29th March 2005

  4. 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 scripts 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 initialisation Processing Crate Jim Brooke, 29th March 2005

  5. LeafJetFpga WheelJetFpga VmeDevice VmeDevice GCT Driver read() write() readBuffer() readEvent() loadEtLUT() read() write() readBuffer() readEvent() read() write() blockRead() blockWrite() GctDriver VmeDevice HAL Jim Brooke, 29th March 2005

  6. GCT Controller GUI : getStatus() Trigger Supervisor : init(key) run() getStatus() XDAQ GctController SC Controller : getEvent() SOAP interface TS Cell GctDriver Conditions DB : getConfig(key) python Jim Brooke, 29th March 2005

  7. 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 Executive wrapper around Driver SOAP interface to GCT Controller Functionality Retrieve captured data for in-situ readout of RCT output Additional functionality for discussion… How many PCs control the Source Cards? Source Cards Jim Brooke, 29th March 2005

  8. Monitor • Original plan : • Monitor runs in XDAQ • Retrieves captured trigger data (via Controller or DAQ) • Run emulator and compare • Must 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 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

  9. GCT Emulator • Library within CMSSW (CMS simulation and reconstruction) • L1Trigger/GlobalCaloTrigger • Used in Monte-Carlo simulation of CMS - needed soon! • 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 2005

  10. GCT Emulator Jim Brooke, 29th March 2005

  11. 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 GT 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 required in order to inform planning Jim Brooke, 29th March 2005

  12. 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 define 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 facilitate debugging as soon as required Jim Brooke, 29th March 2005

  13. 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 use 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

  14. Schedule • Proposed milestones (some new) • Emulator v1.0 release • Source Card Driver ready to integrate 1 SC with 1 RCT crate • Source Card Controller ready for commissioning • All SCs, full RCT readout • GCT Driver ready for testing with Concentrator Card • Standalone via python scripts • GCT Controller ready for RCT/GT integration • GCT GUI ready for RCT/GT integration • GCT Software ready for Trigger commissioning Jim Brooke, 29th March 2005

More Related