engineering GUI specifications

[pmelanson]

Important: we should be able to fit this on 1280x1024

Use cases:

1. Cold starting the habitat reactor. When cold starting, the only components used are
   • Hab reactor
   • hab fuel cell
   • hab battery
   • primary and secondary bus connections
   • habitat reactor fuel injectors
   • habitat fuel cell injector
   • reactor containment
   • and coolant loops/radiators
2. launching through atmosphere or other high intensity burns. During this use case, many more miscellaneous components are used, but the most important ones are:
   • hab reactor (importantly, the temperature of the hab reactor)
   • the 4 hab engine pairs, engine injectors
   • SRBs [careful to not accidentally trigger!]
   • parachute
   • passive radiators (not active radiators!)
   • coolant loops
   • and fuel usage
3. the engineer being bored and looking at the engineering program for eight hours straight (usually during normal operation, the engineer would like to monitor temperature for all components, but also not accidentally leave their laptop on the engineering keyboard and turn off the reactor. Read-only button?)

every component has the following fields:

• whether it's connected
• a temperature
• electrical info
• coolant loop assignment

not all of these pieces of information should be shown at the same time because 99% of the time 75% of that info is useless. Usually temperature is useful.

nice to have: we may want to make the coolant loop and radiator systems more intuitive, perhaps differentiating which radiators are passive vs active (i.e. we can use them during launch).

important specification: we should lay out all the components for habitat and AYSE (possibly not both at the same time), so that programmers can get to work implementing a GUI that represents all the components

Components list:

[coming later]