The engineering GUI has not been finalized, but one of the ideas we had for it was to include a small callout for helpful text descriptions.
We may want to further iterate on that specific design (e.g., should some help text appear on hover? or would there be too much text? perhaps just a help menu or button that shows a static page of text, explaining the program? that would be easier to control)
For now, this issue should just list what things should go in any help text or documentation, so that we don't forget non-obvious things during development.
According to DM's orbitv design (which we may or may not fully implement):
The amount of waste/resistive heat generated by a component is a ratio of the power, and that ratio changes per-component (some components are more efficient than others)
components are cooled by environmental heat loss, coolant loop 1 heat transfer, loop 2 heat transfer, loop 3 transfer, atmospheric transfer, and all these rates are component-specific (i.e. some components are cooled faster by loop 1 than loop 2)
components cool faster when above a certain temperature, e.g. 20 "degrees"
The engineering GUI has not been finalized, but one of the ideas we had for it was to include a small callout for helpful text descriptions.
We may want to further iterate on that specific design (e.g., should some help text appear on hover? or would there be too much text? perhaps just a help menu or button that shows a static page of text, explaining the program? that would be easier to control)
For now, this issue should just list what things should go in any help text or documentation, so that we don't forget non-obvious things during development.