GCT SoftwareESR - 10th May 2006

Jim Brooke

Jim Brooke, 10th May 2006

HAL/CAEN

Overview

GCT Driver

GCT GUITrigger

Supervisor

ConfigDB

Testscripts

USB

Concentrator Card Source Cards

Source CardDriver

Source CardController

GCT Controller

python

GCT Monitor

External component

GCT specific

Arrows are inclient-server direction

GCT Emulator

pythonTest

scripts

XDAQ XDAQ

CMSSW

ConditionsDB

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

Emulator classes

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

Jim Brooke, 10th May 2006

Emulator

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

Jim Brooke, 10th May 2006

Control & test 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

Jim Brooke, 10th May 2006

Control & test (Source) 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

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

Monitoring 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

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)June July Aug Sept Oct Nov Dec

Jim Brooke, 10th May 2006

Schedule (2007)

Jim Brooke, 10th May 2006

Milestones

1. Prototype source card testing software complete May 06

2. GCT Algorithms in new CMS software framework complete June 06

3. RCT-Source Card integration software complete June 06

4. Source Card – Leaf Card integration software complete July 06

5. Source Card – Leaf Card – Concentrator Card Software complete Oct 06

6. GCT monitoring package and histograms for electron trigger complete Feb 07

7. Monitoring and testing software for the jet trigger complete June 07