Trigger "trains"

Deadlines for updates in the trigger menu

• A new menu is integrated, validated and deployed every 2 weeks
• Deadlines:
  • TSG meeting April 7 : the 3rd version of the 5e32 menu
  • TSG meeting April 21 : the 1st version of the 1e33 menu

What should be ready by the deadline

General requirements

For updating or adding a trigger path to the HLT menu you must have:

• the support from Physics Office / Physics Coordination
• presented the request at a TSG or TSG-coord meeting (every Monday 2pm-4pm & Thursday 4pm-6pm)
• an implementation of your path in confDB
• performed the CPU studies

Details on the workflow

• In case it appears during the approval talk that small changes are needed: the updated confDB implementation has to be delivered at most 2 working days after the TSG deadline. This "2 day" is because seemingly "small changes" asked for at approval may turn out to have larger consequences than anticipated.
  • better send around your confDB implementation as soon as you consider it is ready, such that technical problems are catched as soon as possible
  • also note that the POGs trigger representatives need to sign-off for your path (e.g. Jeff B. checks the egamma part of the paths, Jyothsna checks the btag part of paths using b-tagging etc). This sign-off must be done by the "N+2" deadline.

• HCI would integrate things in 2 working days, and descope anything which for whatever reasons can't be integrated in those 2 working days, so that HCI always delivers a menu to the next stage 4 working days (at most) after the TSG deadline.

• Once HCI delivers the menu, the other TSG groups validate it. This takes typically 2-4 days, as in general some iterations are needed (e.g. some prescales that were forgotten, some event content that must be updated etc.)

• the train process, from approval to deployment, must be viewed as a trigger menu production+deployment cycle, not a "late" trigger menu development cycle, which means for example that any problematic trigger must be descoped if its fix can't be accommodated in time for the work needed for delivery of the menu from one stage to the next stage.

• deadlines will be strictly enforced.

Important notes for developers

• Any update must be based on the most-recent master table (we do not want to spend time re-doing changes again!)
  • in case of doubt: ask Andrea and Martin

• The paths must be well tested before submission, even for the smallest of modification, not only on signal but also on data and background.

• The proponents are strongly encouraged not to wait until the deadline, as else, they may miss the train !

-- EmmanuellePerez - 15-Apr-2011