Simulator Redesign

[dimembermatt]

As we've added more complex components to the simulator (different simulation categories, different MPPT algorithms, different MPPT subalgorithms, etc), we've accrued a lot of technical debt in terms of the design of the simulator that limits our ability to debug problems and add new features.

This redesign should overhaul the existing simulator and make it more developer friendly and user friendly. Additionally, now that I (Matthew) am overhauling the TREL MCS, I can further integrate our UI with PyQT to make it a more visually engaging and useful sim.

Expected file and class structure:

Simulation: Manages control of both the PV simulation as well as the array simulation and overall program flow
    | - Source: Manages PV level modeling
    |       | - Cell: Manages cell level modeling
    |               | - Derived Cell model: Cell Model definition
    |               | - Derived Cell model
    |
    | - MPPT: Manages update of the MPPT
    |       | - MPPTAlgorithm: Mppt algorithm base class
    |       |       | - Derived MPPTAlgorithm: Implementation details for a specific algorithm
    |       |       | - Derived MPPTAlgorithm
    |       |
    |       | - MPPTComponent: Algorithm swappable component
    |       | - MPPTComponent
    |
    | - DC-DC Converter: "Converts" MPPT setpoint to an actual pulse width.
    | - Display: Manages updates to UI widgets
External files
    | - Cell Model lookup table: Nonideal Model lookup
    | - PV Simulation output .csv: Simulation data logging output for analysis.
    | - Source Models
    |        | - Source Model .json: PV Model definition
    |        | - Source Model .json

[dimembermatt]

First wiring of data to the UI after finishing many unit tests.

Button choices are bad and I think the default behavior should be thought about a little more on what should actually be displayed. A textbox widget needs to be implemented in the Console class tied to buttons for us to define specific data ranges of input.

For the SourceView, we might want something like this:

• Two modes: Single or comparison mode.
  • Single mode displays a single model with two graphs: fixed temp/independent irradiance, vice versa.
  • Comparison mode displays multiple selectable models with one graph (both models are overlayed over each other). The temperature and irradiance are fixed.
• Graphs on the right 3/4ths of the screen.
  • Graph should be replaced with a Loading textbox (and maybe a loading bar?) if not processed yet. This happens as soon as the buttons compile or prior to default load in.
    • default load in is nonideal model with default resolution
• Console on the left 1/4th of screen, with the following textboxes and buttons:
  • Mode: This could be a toggle button between single and comparison mode.
  • If in Single mode, we have the following textboxes and buttons:
    • textbox with label - voltage resolution
    • textbox with label - irradiance resolution
    • textbox with label - temperature resolution
    • button to compile and display graphs.
  • If in Comparison mode, we have the following textboxes and buttons:
    • textbox with label - voltage resolution
    • textbox with label - irradiance
    • textbox with label - temperature
    • buttons for each model type (toggle)
    • button to compile and display graphs.
  • for both modes, we have a top textbox that defines the PV Source model.