Closed kiefk closed 1 year ago
Just as an fyi, the line
logger = logging.getLogger(__name__)
was added to pass log messages with custom logging levels. Feel free to use whatever logging convention works best for you, but I found it useful to create custom logging levels so I could backtrace bugs to the subroutine they showed up in. For instance, instead of levels like CRITICAL or WARNING, I had SUBAQEUOUS or TPU, etc.
Totally your call on logging convention though!
I think it's great. I used it to build a custom logging level for Sensor.py! I added it on to Merge.py to verify that the a,b, and rho values were updating as expected.
Passed the sensor_object from CBlueApp.py into the merge initalization (line 691, cBlueApp.py).
In Merge.py the init function assigns the a std dev, b std dev, and std rho from the sensor object instead of being hard coded to specific values.