Refactoring and code cleanup

[mlavrent]

It'd be nice to clean up the code, and do a few of the following things:

• separate display from data processing (per MVC style)
  • separate parameter files for each one
• add in units (Pint library)
• use enums where possible
  etc.

I'm going to start work on this, with the following proposed file structure:

main.py
requirements.txt
dataTransfer/
|__params.py
|__dataReceiving.py
|__dataProcessing.py
display/
|__params.py
|__leds.py
|__screen.py

[peterhuson]

This is great! Just for some clarity, I've commented on the existing file structure below:

fsae-apollo/            
│   master_run.sh               # Instantiates screens for both the display code and the data parsing code 
│
└───hardware                    # 
│   │   leds.py                 # LED Class
│   │   master.py               # Parses data, sends colors to LEDs, sends data to display
│   │   params.py               # Parameters
│   └───arduino/canbus_middleman        # 
│   │   │   canbus_middleman.ino        # Interprets CANBUS data and sends it over the serial line
│
└───display                     # Lots of random files that handle the display code. 
│   │   main.qrc                # We should triage this to figure out what we actually need
│   │   mainwidget.cpp          
│   │   mainwidget.h
│   └───backgrounds             # Image files for the display

[mlavrent]

See https://github.com/peterhuson/fsae-apollo/tree/refactoring for work regarding this; once the screen code is done (should be soon), we can test and see how much the refactoring messed it up and work from there.