j. varela, lip-lisbon/cern leade wg meeting cern, 29 march 2004 requirements of cms on the bst j....
TRANSCRIPT
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Requirements of CMS on the BST
J. Varela
LIP Lisbon / CERN
LHC Experiment Accelerator Data Exchange Working Group
1. Trigger Fast Control
2. Detector Control System
3. Requirements on BST
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Trigger Fast Control
Global Trigger Global Trigger TTCmiTTCmi DAQ Event Managers
DAQ Event Managers
Partition ControlPartition Control
TTCrxTTCrx
FrontEnd
Partition ControlPartition Control
TTCrxTTCrx
FrontEnd
Partition ControlPartition Control
TTCTTC sTTSsTTS TTCTTC sTTSsTTS TTCTTC sTTSsTTS
TTCrxTTCrx
FrontEnd
Central Control aTTSaTTSLHC-BST
GPS
LHC-BST GPS
Local Control
Local Control
Local Control
Local Control
Local Control
Local Control
Local Triggers
BST
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
GLOBAL TRIGGER CRATE
CPU
int
TTCci
TTCex
TTCTTS
From/To SUBDETECTOR FRONTEND CRATES
TTS Link
TTC 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
BST link
FMM
FMM
BST link
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
TTCci Module
Interface to TTC optical distributionReplaces TTCvi
TTCci Functions:
Selecting Central or Local control
Internal storage of B commands
Timing of B commands
Internal Trigger generation
L1A and B-data transmission
Development byTony Rohlev (Wisconsin/CERN)
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Trigger Record to EVM: (Included in Event Record)
Begin of event 64 bits //Trigg type, Eventnr, BCnr, SourceID..
Trigger number 24 of 32 //Nr of all L1A hex= „00NN NNNN“ DAQ#+ TriggType + BCnr 20 bits of 32 // 4+4+12 bits , hex=„00DT 0BBB“ Subdetector partitions 32 bits // 1= partition is connected, 0= not connected
Event Number 24 bits of 32 // hex= „00NN NNNN“ Orbit number 32 bitsTechnical trigger bits 32 bitsAlgo bits_0 32 bits Physics trigger algorithm bits 0...31
Algo bits_1 32 bits Physics trigger algorithm bits 32...63
Algo bits_2 32 bits Physics trigger algorithm bits 64...95 Algo bits_3 32 bits Physics trigger algorithm bits 96...127
Algo bits_4 32 bits reserved for optional upgrade
Algo bits_5 32 bits reserved for optional upgrade
GPS time_0 32 bits // bytes 0-3
GPS time_1 32 bits // bytes 4-7
End of Event 64 bits //Event length, CRC.. (as for DAQ)
Trigger Interface to DAQ
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Detector Control System Detector subsystems
-HV/LV-Fluids and environment-Cooling-Racks/Crates-Temperatures-Infrastructures-Test systems (Laser, LED, alignment camera etc..)
Detector safety (DSS)-Temperature-Gas-Radiation
Experiment supervision-DCS Resources handling-Alarm and loggings-History data base-External systems communication.
GPS Time allows to correlateEvent Data withDetector Control Data
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Interface to LHC BSTLHC Beam Synchronous Timing System (BST)
> BST used to synchronize LHC beam instrumentation> Distribution of BST messages (once per orbit) uses TTC> BST message: 32 bytes, of which 8 bytes for GPS Time
Usage in CMS:
GPS Time added to Event Record:
BST/TTC link to Central Trigger Control (1 link)
BST/TTC link to Local Trigger Controllers (10 links)
GPS Time and LHC Data added to DCS Data:
BST/TTC link to central VME receiver (BOBR)
(complementary to access to LHC data via DIP)
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Bytes Description Data format Updated every
0 Machine Mode Enumerated type: No beam, filling, ramping, physic,É On change
1 Beam Type Enumerated type: Ion, Proton,É On change
2 Beam Energy 2 bytes in GEV On change
3 Beam Energy
4 Mean Current per Bunch 2 Bytes * 10E11 ppp
5 Mean Current per Bunch
6 Number of injected Bunches 2 Bytes integer On change
7 Number of injected Bunches
8 Next Batch to Inject 0 for no beam or 1 .. 12 On change
9 GPS Absolute Time 64 bits UTC format On change
10 GPS Absolute Time
11 GPS Absolute Time
12 GPS Absolute Time
13 GPS Absolute Time
14 GPS Absolute Time
15 GPS Absolute Time
16 GPS Absolute Time
17 Last Machine Timing Event 2 Bytes : Machine Timing Event number On reception
18 Last Machine Timing Event
19 BI Predefined received Events 2 bytes : corresponding to 16 predefined events table On reception
20 BI Predefined received Events
21 Main Trigger Byte 8 X 1 bit dedicated Trigger: warning injection, start post-mortem, É 1 Turn
22 BI devices dedicated Bytes 10 Bytes device dedicated commands or triggers : 1 Turn
23 BI devices dedicated Bytes Closed orbit capture, Single Turn trajectory measurement,É.
24 BI devices dedicated Bytes
25 BI devices dedicated Bytes
26 BI devices dedicated Bytes
27 BI devices dedicated Bytes
28 BI devices dedicated Bytes
29 BI devices dedicated Bytes
30 BI devices dedicated Bytes
31 BI devices dedicated Bytes
time granularity of 1ms
time granularity of 1turn
BST Message Contents
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
BST
MESSAGE
ASSEMBLER
TTCEncoder
&Optical
Transmit.
Bunch & Turn Clocks
TTC Optical Network
Universal time
MachineEvents (?)
BeamParameters
Real-timecommands
Hardware triggers
BOBR
TTCrx BSTMESSAGERECEIVER
Clocks
Data
Bytes
CTCTTCrx
LTCTTCrx
10
1
1
BST Overview
CMS specific BST itemsshould be located in racks S1 E 8-10 (LHC, BPTX, BPM)
Located in Central Trigger and TTC racks (S1 E 2-4)
J. Varela, LIP-Lisbon/CERN LEADE WG Meeting CERN, 29 March 2004
Summary of Requirements to BST
Distribution of BST messages to the experiment
Final specification of BST message content and format
Specification of BST/TTC message protocol and timing
Update of GPS time once per 10 orbits (or better)
CMS specific BST items should be located in racks LHC, BPTX or BPM (S1 E 8-10)