j. varela, cern & lip-lisbon tracker meeting, 3rd may 2005 1 partitions in trigger control j....

J. Varela, CERN & LIP-Lisbon Tracker Meeting, 3rd May 2005 1

Partitions in Trigger Control

J. VarelaCERN & LIP-Lisbon

Trigger Technical Coordinator


Trigger Control System

Distribution of L1A and Fast Commands to Subdetectors

TTC architecture

Collection of Fast Feedback from Subdetectors

TTS architecture

Trigger Interface to DAQ

Tools for Timing and Synchronization

Tools for Calibration and Test

CMS NOTE 2002/033


Partition DefinitionsPartition is the smallest unit that can function as a completely independent data acquisition system, in parallel with other partitions:

Independent Physics Trigger and Fast commandsIndependent Fast Feedback collectionIndependent DAQ path (Global or Local)Autonomous run controlAutonomous DCS controlOperation does not affect other partitions

Partition-Group is a programmable combination of Partitions that can function as a completely independent data acquisition system, in parallel with other partitions:

Partitions of different subdetectors may be combinedIn Physics run, one main Partition-Group has priority for triggering


Partition Granularity in CMS

Partition Granularity: Large sub-detector component (e.g. sub-detector barrel)No overlapsMaximum number is 32

A Partition is equivalent to:a TTC distribution channel (TTCci) serving a group of front-endsa sTTS collection channel (FMM) receiving status from a group of

front-endsa DCS control branch

Partition-Groups:Maximum number is 8TTC partition-groups match central DAQ partitions


Operation Modes

Global DAQ:Central Trigger ControllerCentral DAQPhysics TriggersMaximum independent “systems” in parallel is 8Run Control software

Local DAQ:Local Trigger ControllerVME data acquisitionTest TriggersMaximum independent “systems” in parallel is 6Run Control software (configured in local mode)


Granularity in a Subdetector

During commissioning it may be useful to have a finer granularity at the subdetector level

Each subdetector has its own tools, which depend on particular hardware solutions

What is the natural unit in the Tracker case?

How many of this units can reasonably be expected to be operated in parallel?

ECAL case: each SuperModule can run independently, with local (SM) generation of test signals


Pixels 2Tracker 4 PreShower 2ECAL 4HCAL 6 RPC 1DT 2CSC 2Cal Trig 2Muon Trig 3Totem 1

29

TTC Partitions

Available TTC partitions: 32


Trigger Fast Control

Global Trigger Global Trigger TTCmiTTCmi DAQ Event Managers

DAQ Event Managers

Partition ControlPartition Control

TTCrxTTCrx

FrontEnd


TTCrxTTCrx

FrontEnd


TTCciTTCci sTTSsTTS TTCciTTCci sTTSsTTS TTCTTC sTTSsTTS

TTCrxTTCrx

FrontEnd

Central Control aTTSaTTSLHC GPS

LHC GPS

Local Control

Local Control

Local Control

Local Control

Local Control

Local Control

Local Triggers

L1A Control

Front-end Emulators, Trigger Rules

Trigger Throttling System (sTTS and aTTS)

Calibration and Test Triggers

Dedicated runs, Special triggers during runs

Synchronization ControlTiming signals, Resync procedures

Partitioning

8 independent TTC Partition-groups, 8 independent triggers


Configurable Partitioning

Up to 8 fully independent TTC partitions-groups may be defined in the Central Trigger Controller

Partition-groups = DAQ Partition

Partitioning in Global DAQ Mode:


Central Trigger Control DAQ Event Manager

Local Trigger Control

Multi-Level Trigger Control

TTCci: Partition Control

CTC: CMS Control

LTC: SubDetector Control

TTCci sTTS

TTCrx

FrontEnd

TTCci sTTS

TTCrx

FrontEnd

LHC-BST

aTTSaTTS

TTCmi


GLOBAL TRIGGER CRATE

CPU

int

TTCci

TTCex

TTCTTS

From/To SUBDETECTOR CRATES

sTTS LinkTTC Link

Local Triggers

LTC TTC

TTS

... ...

Fast Merging Module

Local Trigger Controller

SYNC TTS

FMM

Central Trigger Control

(x 32) (x 32)

TTCmi

To EVM

To/from aTTS

ClockOrbit

Trigger Control Components

Subdetector Master TTC Crate

GPS link

FMM

FMM


VME

-PCI

FMM

LTC

VME 6UTTCci

TTCci

Sub-detector with 4 TTC Partitions

TTCci

TTCci

Partition 1

Optical coupler

<32 fibers

1 fiber

Optical coupler

<32 fibers

1 fiber

Optical coupler

<32 fibers

1 fiber

Optical coupler

<32 fibers

1 fiberPartition 2 Partition 3 Partition 4

TTCex is required when the number of destinations per TTC partition is larger than 32

Passive optical splitting of TTC info TTC Partitions are hardwired


Central Trigger Control


TCS9U Board


TCS9U Hardware


LTC

• 2 prototypes exist

• Production of further 12 boards launched

• Software

– HAL-based device driver being written

– XDAQ overlay will also be implemented

LTCLocal control of sub-detectors:

- Up to 6 partitions- Input for 6 local triggers- Interface to 6 TTCci- Interface to one TTCvi (backward

compatibility)- Interface to sTTS (6 channels)- Interface to aTTS (1 channel)- Interface to 4 Emulators

- Interface to DAQ EVM (S-Link)- Interface to BST


TTCci

• 1 prototype exists

• Production of further 15 boards launched

B-Go from CTC

L1A from CTC

L1A from LTCMUX

L1A To TTCex

Channel-A

B-Go from LTC

5

5

MUX

B-Go

Decode

B-Ch

Command code FIFO

Ch 1

Command code FIFO

Ch 16

...

To TTCex

Channel-B

Programmable

TTCci

Clock, Orbit

Aux triggers

B-data


Multiplexing of L1A and B-Channel inputsTo allow control by CTC or by LTC (programmable)

Number of B-Channels: 16

Timing of B commandsProgrammable delay between external B-Go and command transmission

Internal generation of B commandsSynchronous with orbit input (prescaling, timing); driven by VME

Internal Trigger generation

Synchronous with orbit (prescaling, timing); random; trigger rules

External B-data8-bit data stored in FIFO and sent to B-channel with low priority

TTCci Functions

j. varela, cern & lip-lisbon tracker meeting, 3rd may 2005 1 partitions in trigger control j....

Documents

partitions partitiongroup

run control software

independent physics

central daq partitions

ttc partitiongroups

cms partition granularity

tracker case

main partitiongroup