Description
Points to discuss courtesy of Jeff Landgraf:
Generally I'd like to make sure we are on the same page with regard to the organization of the detector: counts of layers, sensors, modules, staves, and ESB's. The most relevant to DAQ is just the count of ESBs (and that we share an expectation of the fibers to and from them), but Electronics & DAQ keeps tables for the detector in general and it's good to be on the same page for reviews and such.
I'd like to know the rate capabilities for each component to understand any bandwidth limitations (even though I suspect this isn't an issue for astropix). The expected capability of the ESBs are the most critical for E&DAQ purposes.
Similar for the expected hit rates from simulations and noise.
Finally I'd like to know some details of the ESB needs:
Configuration? The astopix itself might have specific needs that have to be passed through the ESB
Slow Controls? Is there any information that must be passed through the ESB for measurements of temperatures or other sensors? Are there any calibration systems that need to be triggered from the user through the ESB?
General operation?
What clocks are needed?
Do you have specific requirements for commands synchronized to specific bunches (Fast commands)?
Is there a mechanism E&DAQ can use to verify synchronization with other detectors (e.g. a trigger FAST command that retrieves at least the time counters)?
Data formats (doesn't have to be final, but we'd like some idea about header sizes, and what data is sent, and how much data an incident particle will produce on average)
