Engines require outputting all possible variables

[jkirk5]

Desired capability or behavior.

It may be possible to eliminate this requirement by more intelligent code in the propulsion mission component. Adding try statements (or checking the engine's self.use_XXXX flag) to connections instead of assuming they exist, and ensuring that a value of zero is passed to the MuxComp if the variable is not provided by the engine is a possible solution.

Is your feature request related to a problem? Please describe.

Currently, due to the way all engine outputs are muxed together to compute vehicle-level totals, all engines are required to output all possible engine outputs, even if they are not produced by that engine and get defaulted to zero (e.g. outputting 0 kWh for a fuel turbine). This is a hassle for creating new engine models.

Associated Bug Report

No response