Class ACS: : This structure is likely to change for v2.0
Global ACS::data: : find a better way to handle it
Global acs_event: : This is going to change in v2.0 to more accurately reflect how the ACS will operate
Global acs_state: : This is going to change in v2.0 to more accurately reflect how the ACS will operate
Global adcgrpcfg: : combine this with a timer to not spam interrupts so much?
Global can_msg: : This is going to change in v2.0 once a protocol is decided for communication with the ACS
Global can_msg_type: : This is going to change in v2.0 once a protocol is decided for communication with the ACS
Global can_recv: : This is going to change in v2.0 once a protocol is decided for communication with the ACS
Global getNextEvent (ACS *acs): : we should seperate the trap from the state changes in the next version
Class MTQR: : this structure is not being used effectively it may or may not be a good design choice
Global OPENLOOP: : openloop is going away
Global SCALE: : the definitions of STEP, STRETCH, and SKIP evolved over the course of various experiments. These will completely change in v2.0. Below is their intended and eventual meanings.
Global THREAD_SIZE: : had to reduce this to compile with new ADC code We should figure out what an actual good value is
Global trap_rw_control (ACS *acs): : have a better data system.
Global trap_rw_scale (ACS *acs): : have a better data system.
Global trap_rw_skip (ACS *acs): : have a better data system.
Global trap_rw_stretch (ACS *acs): : have a better data system.
Global WA_ACS_THD_SIZE: : Thread sizes cause continual problems for managing memory if the threads are too small it breaks, if the thread working areas are too large then you run out of memory. One solution is to move to a mcu with more memory.