...

• 288 bits of "event codes":
  • some have well-defined meanings (in progress)
  • 16 highest bits are hutch specific for sequences (272-287)
  • DAQ readout groups are "extra bits" included at end of timing frame
• timing frames have "destinations": e.g. bykiks, and bykikh both go to "bsy" dump
• unlike LCLS1 we will not be using event-codes to understand when bykiks has fired: use destinations instead
• To trigger on "every shot" with beam (the equivalent of LCLS1's eventcode 140) use "Mode=FixedRate:1MHz, Destination=Include:DumpSXR" (without the "destination" field I believe you will just get a pure 1MHz trigger)

Trigger Types

Timing receivers share a common logic module for generating triggers.  They consist of the logical AND of two components, a rate component and a beam destination component.

• Rate component.
  • sequences / event code
  timing trigger types:
  • sequences
  • ac-line rate (1,5,10,30Hz...) + timeslot mask
  • fixed-rate patterns (11H, 1010H, 100100H, 10001kH, 1000010kH, 71kHz71kH, 929kHz)
  need to coordinate hutch sequence-
  • 1MH)
• Beam destination component
  • "Dont Care" : beam or no beam, we don't care
  • "Inclusive" : specify a set/mask of destinations to which the beam must be destined; see the table below
  • "Exclusive" : specify a set/mask of destinations to which the beam must not be destined; see the table below.

Need to coordinate hutch sequence-pattern scripts with accelerator sequence-pattern (patterns repeat on 1H marker).

Sequencing Example

See https://github.com/slac-lcls/lcls2/blob/master/psdaq/psdaq/seq/rixexample.sh (high level example for bursts and period patterns) and Integrating Detectors in RIX.  See also Matt's documentation.

...