Displaying Values/Booleans/Enums and Comparing Data

**Comparing data: As a team member, I need to be able to view and compare multiple graphs so I can see and compare how each graph changes relative to each other. This will allow me to pinpoint if a change in one set of data corresponds with a change in another (i.e. changes occur at the same time, or one changes after the other) and aid in issue triangulation.
- I will often compare data sets that are closely related to each other, such as front battery voltage and rear battery voltage
- I could also theoretically want to compare stuff like altitude and motor controller temperature (how does going up a hill affect the MCl temp?)

Displaying Values vs Booleans vs Enums

Depending on the nature of the value and how users want to interpret it, display types will differ as well - monitoring trends vs exact values
e.g. current speed, voltages, current
Looking at Near East’s dashboard as an example, they have displayed values in three different ways. There are exact values to the right side of the dashboard, graphs are includes to show trends in the bus currents and also values are displayed in the CMU status.
For exact values
- Limit it to a clearly labelled and displayed number
- For better grouping (such as all the battery cell voltages or temperatures) stacking them like so might better utilize the given area. Colour coded if there is an outlier?
- For a more prominent display, such as an averaged value or speed, the larger number makes it stand out (this is seen on the Near East dashboard).
For trends
- The best way to display trends is through line graphs. While monitoring the trends is important, there should be a feature where specific point can be selected and the value indicated.
- I like this, where guide lines are included to pinpoint the x and y axes.
- This is another example if we are displaying multiple values on a single graph. A specific time can be highlighted, and the exact values of all of the lines should be displayed in a popup.

Booleans can be displayed primarily using colours ( red or green) as colours are a pretty universal indicator of true/false.
An alternative to red or green could just be light or no light
Here is an example of a symbol which lights up - too many different symbols is confusing and users won’t necessarily know what they mean but its a possibility (symbol for e-brake engaged or something)
Another method is to include a visualized switch where it can be switched on/off
Specific booleans such as the faults only need to be displayed if true, and in that case, can appear as a text banner for the fault (will get into this in the enum)

I think the primary enums which we will be encountering are faults and drive states
Drive states - Letters associated with each drive state (also seen on the Near East dashboard above)
- Users need to know what each letter is associated with
Enums could be displayed as banners, status boxes, or a combination of both
This is an example of an expandable status log. Most status updates will not be useful until they actually occur so they shouldn’t take up a consistent space on the dash.
They should also be easily accessible in the case where something does happen, so an alert icon can remain at a certain location on the screen.

Displaying two different data sets
- Could be stacked like an oscilloscope. Stacking the two graphs is best for comparing data over a series of time. By stacking them vertically, the x-axis times can be aligned and we do not to be worried about different y-axis units
It is important to have a common reference point for the graphs where a user can highlight a time and a vertical line will appear for each graph.
A line showing the difference
Stacking graphs in the same spot (difficult for things with diff x+y values)
Stacking graphs where the area between is coloured
Make the difference between them clear
Side by side could be useful
Anything bar chart
- Can have a curve connecting them
Display data on the same graph
- Double bar chart etc.