Why can't a leader support multiple experiments?

[CamDavidsonPilon]

• Overview page is only designed for 1 experiment
  • top level header can be used to select experiments
• Pioreactors page is only designed for 1 experiment. The latest experiment is retrieved from the database, and this populates MQTT topic strings, and then data is fetched for that experiment.
  • again, the top level header can be used to choose experiment, and the assigned Pioreactor workers are displayed
• workers use the function get_latest_experiment_name which implies a single experiment is running.
  • new db table pioreactor_worker_assignments (TBD) exists. Workers should use a new function get_latest_assigned_experiment_name and hit a new endpoint to get their experiment name,
• leader actions, like experiment_profile execute will grab the latest experiment.
  • we pass in the experiment to "target"

---

OTOH,

• mqtt_to_db_streaming is experiment agnostic
• so is watchdog and monitor, mostly
• MQTT can support multiple experiment streams
• So can the database

[CamDavidsonPilon]

• [x] experiment profiles needs to decided how to handle if an pioreactor is not active, or if it's not assigned