Level-3 Trigger/Event Tagging Commissioning Plan Spring 2016

From GlueXWiki
Jump to: navigation, search

Overview

This details the plan for commissioning and testing the L3 trigger and Event Tagging system. The system relies on use of the monitoring farm to provide a distributed system for handling the full data rate of the DAQ. When L3 is active, the system actively rejects events. Regardless of whether events are rejected or not, the events are reformed before writing to disk. This compacts the events and allows information to be added. This ability is the Event Tagging potion of the system.

Day 1 (4hr)

The following runs need only last about 5 minutes so that a steady state can be reached and the rates can be recorded.

  1. Run without L3 using "PHYSICS" Run type in rcm.sh (note TRIGGER, MODE, BLOCKS, CALIB)
    • Record:
      • SEB event rate
      • SEB data rate
      • ER event rate
      • ER data rate
      • Livetime
  2. Run with L3 and using same trigger.
    • Select "EXPERT" as Run type in rcm.sh and "hd_all.L3.tsg" as the SETUP