Page History

...

• display makes requests to clients? both algorithm/parameter changes and gather messages
• different rates for different gather requests?
• how do you guarantee consistency with changing calculations e.g. ROI?

Reduce/Gather Design Ideas

• specify what to send, when to send (upstream)
• what to accept what to do with it
• send on timer or event-count
• reduce-last-hundred-events will be fuzzy (alternative is to constrain the way daq hands out events to cores)

Plot "Boxes" Ideas

• keep them separate from the graphs
• many output boxes (plot, save to disk, etc.)
• three big ideas: management, graph, output

Reconfiguration of Graph

• reconfigure everything downstream of the box that gets changed
• boxes like a "deque" box will clear their deque's.
• boxes could have a variety of more complex reconfigures that have fewer side-effects (e.g. not clear the deques in some circumstances)

Possible Graph Backward Loops

• This is the case where a background is computed by a post-reduce box and fed to an upstream box
• We think we can avoid backward loops in this case by having one chain of post-gather boxes feed upstream boxes

Topics to Discuss

• metadata
• slow data (epics)
• data interface (top-down vs. bottom-up design)
• IOC recorders

Packages to Consider

pyqtgraph

...