Page History
...
RIX says they want this "in the future" (see the sub-page Integrating Detectors in RIX)
psana Design Options
(discussion on March 16, 2022)
simple timestamp example:
andor (1hz): s 4s 8 (s=start of integration)
hsd (4hz): 12345-78
batch size now has to keep three things happy:
- performance/efficiency
- integrating detectors
- batching memory, which is only for small data (hopefully we can deal with this)
o big data isn't batched, handled on event-by-event basis, and
memory is handled naturally, so not a problem
requirement: only one integrating detector? more is OK but they have to
be synced.
- can't support conflicting requirements from 2 detectors where an
an event has to go to two places
- verify with experimenters
timescale is Sept. 2022
option 1:
- put batching on an andor boundary (4, 8)
o shots 1 thru 4 go to 1 EB core and 1 BD core
- user needs to specify a "special" stream file (andor, above)
- batch size becomes dynamic.
o current batch size is fixed: default 1000, can be set by user
o currently last batch is dynamic
- two ideas currently: chunk-size between SMD0 and EB, and batch
size between EB and BD. both are currently fixed numbers
- could use many EB cores (unlike destination callback)
- could put multiple andor images in 1 batch for efficiency
option 2:
workaround? maybe we could reuse the destination callback?
- has a limitation that we can only use 1 EB core
- Mona thinks that if "we" control destination callback then
we can perhaps have more than 1 EB core. SMD0 has to be in-charge