Page History

...

• Use separate processes for 1  event in a reddis-like decentralized environment?
• support an arbitrary loopless graph of analysis
• support for reading/writing EPICS variables in real-time (having analysis/daq/controls be in the same python environment is necessary for this). would help with feedback
• maybe could replace hutch python to control DAQ with this? (scans)
• 1 event 1 core
• scientists only write algorithm boxes
• two levels: "box" level, and then the "scheduler"
• how do we pass meta-data through the tree?  (e.g. for two ROIs in a row, the second one needs to know about the first one)
• policy for type-checking and shape-checking?

Multiprocessing

• 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?

...