Partitions in Trigger Control

1. Partitions in Trigger Control J. Varela CERN & LIP-Lisbon Trigger Technical Coordinator

2. 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 Trigger Control System CMS NOTE 2002/033

3. Partition Definitions • Partition is the smallest unit that can function as a completely independent data acquisition system, in parallel with other partitions: • Independent Physics Trigger and Fast commands • Independent Fast Feedback collection • Independent DAQ path (Global or Local) • Autonomous run control • Autonomous DCS control • Operation 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 combined • In Physics run, one main Partition-Group has priority for triggering

4. Partition Granularity in CMS • Partition Granularity: • Large sub-detector component (e.g. sub-detector barrel) • No overlaps • Maximum number is 32 • A Partition is equivalent to: • a TTC distribution channel (TTCci) serving a group of front-ends • a sTTS collection channel (FMM) receiving status from a group of front-ends • a DCS control branch • Partition-Groups: • Maximum number is 8 • TTC partition-groups match central DAQ partitions

5. Operation Modes • Global DAQ: • Central Trigger Controller • Central DAQ • Physics Triggers • Maximum independent “systems” in parallel is 8 • Run Control software • Local DAQ: • Local Trigger Controller • VME data acquisition • Test Triggers • Maximum independent “systems” in parallel is 6 • Run Control software (configured in local mode)

6. 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

7. TTC Partitions Available TTC partitions: 32 Pixels 2 Tracker 4 PreShower 2 ECAL 4 HCAL 6 RPC 1 DT 2 CSC 2 Cal Trig 2 Muon Trig 3 Totem 1 29

8. Trigger Fast Control DAQ Event Managers TTCmi Global Trigger LHC GPS aTTS Central Control Partition Control Partition Control Partition Control L1A Control Front-end Emulators, Trigger Rules Trigger Throttling System (sTTS and aTTS) Calibration and Test Triggers Dedicated runs, Special triggers during runs Synchronization Control Timing signals, Resync procedures Partitioning 8 independent TTC Partition-groups, 8 independent triggers Local Triggers Local Control Local Control Local Control TTCci sTTS TTCci sTTS TTC sTTS FrontEnd FrontEnd FrontEnd TTCrx TTCrx TTCrx

9. Configurable Partitioning Partitioning in Global DAQ Mode: • Up to 8 fully independent TTC partitions-groups may be defined in the Central Trigger Controller • Partition-groups = DAQ Partition

10. Multi-Level Trigger Control TTCmi DAQ Event Manager Central Trigger Control LHC-BST aTTS Local Trigger Control CTC: CMS Control LTC: SubDetector Control TTCci sTTS TTCci sTTS TTCci: Partition Control FrontEnd FrontEnd TTCrx TTCrx

11. Trigger Control Components GPS link To EVM GLOBAL TRIGGER CRATE To/from aTTS TTCmi Central Trigger Control ClockOrbit TTC (x 32) (x 32) TTS Fast Merging Module Local Triggers CPU int F M M TTCex TTCci F M M LTC TTS ... ... FMM TTC SYNC TTS sTTS Link Subdetector Master TTC Crate TTC Link Local Trigger Controller From/To SUBDETECTOR CRATES

12. TTCci TTCci TTCci TTCci Sub-detector with 4 TTC Partitions Passive optical splitting of TTC info  TTC Partitions are hardwired VME -PCI VME 6U LTC FMM Partition 1 1 fiber Partition 2 1 fiber Partition 3 1 fiber Partition 4 1 fiber Optical coupler Optical coupler Optical coupler Optical coupler <32 fibers <32 fibers <32 fibers <32 fibers TTCex is required when the number of destinations per TTC partition is larger than 32

13. Central Trigger Control

14. TCS9U Board

15. TCS9U Hardware

16. 2 prototypes exist Production of further 12 boards launched Software HAL-based device driver being written XDAQ overlay will also be implemented LTC LTC Local 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

17. 1 prototype exists Production of further 15 boards launched TTCci TTCci L1A from CTC MUX L1A L1A from LTC To TTCex Channel-A Aux triggers Ch 1 B-Go from CTC Command code FIFO  5 ... MUX B-Go Decode B-Ch B-Go from LTC 5 Ch 16 Command code FIFO  Clock, Orbit To TTCex Channel-B B-data Programmable

18. TTCci Functions Multiplexing of L1A and B-Channel inputs To allow control by CTC or by LTC (programmable) Number of B-Channels: 16 Timing of B commands Programmable delay between external B-Go and command transmission Internal generation of B commands Synchronous with orbit input (prescaling, timing); driven by VME Internal Trigger generation Synchronous with orbit (prescaling, timing); random; trigger rules External B-data 8-bit data stored in FIFO and sent to B-channel with low priority