search

Teststandees / hcal_teststand_scripts

HCAL teststand scripts
0 stars 11 forks source link

Component Statuses #3

Closed elliot-hughes closed 9 years ago

elliot-hughes commented 9 years ago

We need to edit the component status functions to be informative (for debugging and logging purposes) and passive. Once this is done, we need to write a simple ts_setup.py to run all of these statuses.

elliot-hughes commented 9 years ago

I added status classes to each component (yeah, someone who likes coding can go in and make them all inherit from a template at some point) and modified their get_status functions accordingly. The get_status functions are now entirely passive. I added a script called ts_status.py which statuses each component and writes a status log to data/ts_904/status. We can add to the status functions as we see fit.