Special instructions: trigger subsystems

[gladky]

   * Background info: *LIST of Trigger subsystems and their FEDs*
      * Calo Layer-1: 1354, 1356, 1358
      * Calo Layer-2: 1360
      * CPPF (Concetration Pre-Process Fan-out system for endcap RPC): 1386
      * BMTF (Barrel Muon Track Finder): 1376, 1377
      * OMTF (Overlap Muon Track Finder): 1380,1381
      * EMTF (Endcap Muon Track Finder): 1384 (- side), 1385 (+ side)
      * uGMT (Micro Global Muon Trigger): 1402
      * GTUP (Micro Global Trigger, uGT): 1404
      * GTUPSPARE: 1405

[gladky]

Could you please help me understand what this special instructions are about? What does it mean for the operator / expert system?

[andreh12]

After looking at the twiki page, the list you posted in the first comment looks to me like it was put there for better communication with the L1 trigger shifter or DOC so that one can translate the FED number (as e.g. seen in DAQView) to something the L1 shifter or DOC can understand easily.

It is basically a more fine grained naming than partitions and fedbuilders.

For example for FED 1384, from DAQView one learns that the TTC partition is MUTF and the fedbuilder is EMTFOMTF but the one can't tell that FED 1384 is part of EMTF which is useful information for the L1 trigger persons (the fedbuilder combines EMTF and OMTF).

[hsakulin]

This is simply the correspondence between trigger sub-systems and their FED IDs. It helps shifters to communicate effectively. Except for the + and 1 distinction in the EMTF FEDs, the information is available in the FEDGroup in the HWCfgDB.

We may want to propagate the FEDGroup into the JSON model so that the Expert’s messages can be made even more informative.

On 04 May 2018, at 15:21, Maciej Gladki notifications@github.com wrote:

• Background info: LIST of Trigger subsystems and their FEDs
  • Calo Layer-1: 1354, 1356, 1358
  • Calo Layer-2: 1360
  • CPPF (Concetration Pre-Process Fan-out system for endcap RPC): 1386
  • BMTF (Barrel Muon Track Finder): 1376, 1377
  • OMTF (Overlap Muon Track Finder): 1380,1381
  • EMTF (Endcap Muon Track Finder): 1384 (- side), 1385 (+ side)
  • uGMT (Micro Global Muon Trigger): 1402
  • GTUP (Micro Global Trigger, uGT): 1404
  • GTUPSPARE: 1405

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[gladky]

1. Shall we add FEDGroup field for each FED objejct in the next version of DAQAggregator?
2. How do you want to display fed group information in expert messages? Here are few expamples:

TTCP TOTDET of CTPPS_TOT subsystem is blocking triggers, it's in WARNING TTS state, The problem is caused by FED 587 in WARNING

TTCP CTPPS of CTPPS subsystem is blocking trigger, it's in BUSY TTS state, The problem is caused by FED [(1463 behind pseudo FED 11462), (1462 behind pseudo FED 11462)] in (FED has no individual TTS state, BUSY @ its pseudo FED)

TTCP [MUTF, CALOL1] of TRG subsystem is blocking trigger, it's in BUSY TTS state, The problem is caused by FED [1380, 1381, 1356, 1358 and 1 more] in BUSY

[hsakulin]

1. Yes, we should add FEDGroup.
2. You could use the FED Group whenever you list a number of FEDs in order to group them. In case the list contains FEDs from multiple partitions I would prefix the group with the aprtition or group only by partition. e.g.: TTCPs [MUTF, CALOL1] of TRG subsystem are blocking the trigger. The problem is caused by MUTF/OMTF FEDs [1380, 1381] and CALOL1 FEDs [1356, 1358 and ??] in BUSY.

Regarding the listing of pseudo FEDs maybe the following would be more readable: The problem is cause by pseudo-FED 11462 (with main FEDs [1462, 1463]) in BUSY.