amoghpj/evolver

evolver's Issues

Action items for frontend

1. Document usage in readme.
2. Update default config file handling. In theory, we should be able to prepopulate the fields not just with hard coded defaults but continue from a previous configuration file. This will be important if something crashes halfway through.
3. Combine forms to avoid having multiple submit buttons. Use a horizontal rule to separate out the parts instead
4. Add feature to store calibration file in the frontend.
5. Consider abstracting away the front end so a single instance is run on the machine. This needs implementing file browser support which will allow the user to specify which experiment to display.

Start using a data class instead of global variables

I am trying to separate out experiment specific data from general evolver logic in custom_script.py
One issue is that there are many "global" variables that need to be updated in multiple locations. The new experiment_params.yaml should store all relevant settings.

Exploit logging to store more events

Not sure what the purpose of logging is right now. It only seems to note the times that the computer reconnects to the eVOLVER. Can we use this to log more state changes?

Special handling of growthcurve

Currently, since there is no explicit logic in growthcurve the to_run parameter is ignored. This leads to errors downstream, if the user specifies running online growth rate estimation which requires the calibration data for vials which are missing.