better calibration data model

[CamDavidsonPilon]

• It would be nice if all calibrations looked the same, without having to update each one and make sure the syntax is correct. Maybe this would help? https://click.palletsprojects.com/en/8.1.x/commands/#custom-multi-commands
• Users want to share calibrations, edit them, etc. It would be a great idea for calibrations to be flat files on disk (yaml?), instead of stored in a db.
• A UI page that (in the general section):
  • has a list of each workers calibrations
  • a way to view calibrations (a chart?)
  • a way to select calibrations to use
  • a way to run calibrations (stirring, pump, OD, LED (via a plugin??))

[CamDavidsonPilon]

• Calibrations will be yaml files stored locally in .pioreactor/storage/calibrations/<type>

[CamDavidsonPilon]

Hm, I need to separate the type of calibration, from what is being calibrated. The latter determines the folder structure (this enables moving a calibration from the media_pump folder to the waste_pump folder for example).

[CamDavidsonPilon]

Next: I need an two APIs for different calibration protocols:

1. How does the user choose (discover??) a specific protocol to calibrate device D?
2. How does a 3p developer add a protocol, calibration type, etc. to target device D?