Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • hope these don't need to be processed by AMI, unless DAQ manages to bring them into the hutch-DAQ via "PGP broadcast"
  • if they produce files like current system, AMI would handle them with psana offline event builder.
  • as alternative to PGP, online event-builder could grab well-timestamped epics data for us in AMI

DAQ/DRP Reconfig

  • we will assume the DAQ/DRP reconfigs look identical to us
  • DRP reconfigs can be generated from AMI
  • we think DAQ/DRP reconfigs don't interfere with AMI-analysis-graph reconfigs

Display Images at Low Rate

  • no "requests" to graph from display clients
  • use "reduce" boxes

Monitoring of AMI Performance/Health

  • stats sent when data flowing
  • isAlive-health monitored with procserv like process
  • ideally could trigger a python-strace when stuck
  • stats do not flow through the data graph:  separate path (a separate stats piece of the graph?)

DAQ Transitions

  • Try to eliminate transitions in the DAQ
  • instead use "base-configuration" for a run, and time-ranges-of-validity for configuration changes (scans)
  • online and offline event-builders will event-build the configuration changes accordingly

To Discuss

  • changing data as run goes on (e.g. DRP pre scaled uncompressed events)

Projects

  • scaling
  • ami "calculator"
  • pyqtgraph graphical operations:
    • "box" gui
    • "point and click" gui (how much goes in here)

...