Page History
...
- the absolute encoder will continue to be used
- perhaps add a second high-rate (maybe even MHz?) relative encoder
- in november either we have to increase the current absolute encoder rate, or do the "interpolation". beam starts at a few kHz.
- feels like a good chance we need interpolation mode since the MHz encoder does not yet exist
- existing absolute encoder may trigger at 500Hz or 1kHz, but no more
- existing absolute encoder has estimates for velocity, acceleration, jerk, maybe more? zach can include these in the data stream fairly easily so we can see how well it does
- for psana we will need to have an encoder readout trigger the "start" of a batch (for parallelization) similar, but different from, integrating detectors where data triggers the "end" of a batch.
- is there a batching conflict between integrating detectors (e.g. andor) an absolute encoder? may need to trigger the encoder at a higher-harmonic of the andor? but maybe still a conflict because one marks the end of the batch while the other marks the beginning?
Overview
Content Tools