Page History

...

• two separate free-lists: one for CPU, one for GPU
• LCLS would like a GPU-enabled TDet firmware (timing system triggers a fake-payload of user-defined size)
  • generates fake payloads 
  • Ryan said: that TID needs to come up with a block-diagram for this
• For real detector: LCLS would like multiple detector lanes (8 for kcu) built by the Batching EB in in kcu1500 firmware
  • this is separate from the BEB on the FEB which joins timing to data 
  • a "partial" event builder (detectors still split 
  • this is currently done for epixHR (we think the old pre-existing timing-stream is disabled in the KCU BEB)
  • Mudit could modify the existing epixHR kcu1500 firmware, but eliminate timing system and expand to 8 data lanes
  • could we eliminate the front-end BEB to avoid a level of tail-iteration?  Ryan thinks maybe even could avoid the kcu tail-iteration somehow
• There are two different uses of the word "batching": batching-event-builder (which cpo thinks of as being just an event builder) and batching in the sense of giving the KCU one "wakeup" call for multiple events (a "batch").

Example of two-level batching event builder (BEB) in the FEB and KCU:

FE FEB segment a batch: t1,d1a,d1b event-built into "f1a"
FE FEB segment b batch: t1,d1c,d1d event-built into "f1b"

...