Page History
...
Additionally a JSON file containing a source configuration may be provided. A URI to the file where the prefix contains the source type must be passed to AMI. For example to load the above file run ami-local hdf5:///worker.json to use the psana source run ami-local psana:///worker.json.
Viewing Low-Rate Detectors in AMI
By default, low-rate detector data can be "swamped" by high-rate events, so no updates are seen for low-rate detectors. Ric Claus provides a fancy way of selecting which events have priority to go to ami (the "monitoring event-builder (meb) decision" which can be done with python) but there is also a readout-group based mechanism available which may be more commonly used since it is simpler. Ric writes:
"Look at the trigger_0 detector in configDb. To increase the chances seeing slow detector events in AMI, you need to configure the TEB to reserve some buffers for the slow readout group triggers. This is done by entering the number of buffers you want to reserve for the readout group in the rogRsrvdBuf element for the group. One buffer may be sufficient, but you could try raising the number of reserved buffers, up to the number of buffers the MEB was configured with (64?). At the maximum, I think there would never be any buffers available for the fast readout group(s) so you would never see anything from the fast detectors in AMI."
Configuration Flags
...
These flags can be passed to the source using any of the three methods above, the gui configuration window, a json file, or using the -f command line flag. To specify multiple flags using the command line pass -f multiple times. For example:
...
Configuration Flags
| Flag | Description |
|---|---|
| interval | Time in seconds to sleep between events |
| init_time | Time in seconds to sleep before emitting the first event |
| repeat | Loop over files/events after reaching end |
| files | Comma separated list of files to load (either xtc2 or hdf5) |
These flags can be passed to the source using any of the three methods above, the gui configuration window, a json file, or using the -f command line flag. To specify multiple flags using the command line pass -f multiple times. For example:
| Code Block |
|---|
ami-local -f interval=1 psana://exp=tmoc00118,run=4,dir=/ffb01/data/tmo/tmoc00118/xtc/ |
Viewing Low-Rate Detectors in AMI
By default, low-rate detector data can be "swamped" by high-rate events, so no updates are seen for low-rate detectors. Ric Claus provides a fancy way of selecting which events have priority to go to ami (the "monitoring event-builder (meb) decision" which can be done with python) but there is also a readout-group based mechanism available which may be more commonly used since it is simpler. Ric writes:
"Look at the trigger_0 detector in configDb. To increase the chances seeing slow detector events in AMI, you need to configure the TEB to reserve some buffers for the slow readout group triggers. This is done by entering the number of buffers you want to reserve for the readout group in the rogRsrvdBuf element for the group. One buffer may be sufficient, but you could try raising the number of reserved buffers, up to the number of buffers the MEB was configured with (64?). At the maximum, I think there would never be any buffers available for the fast readout group(s) so you would never see anything from the fast detectors in AMI."
Reporting AMI Issues
Users are encouraged to submit AMI bug reports, feature requests, and questions through github issues: https://github.com/slac-lcls/ami/issues
...
Overview
Content Tools