feat(cond): randomized starting positions for air conditioning selector knobs

[rare-potato]

Fixes #3128

Summary of Changes

On plane load the air conditioning selector knobs will be set to positions other than 12 o'clock based on a multimodal distribution centered on the 11 o'clock, 12 o'clock, and 1 o'clock notches, with more weight on the 11 and 12 o'clock notches.

References

Additional context

Task List:

• Get feedback on most common positions outside of the 12 o'clock position
• Program the multimodal distribution
• Determine if code should be implemented in a different place.
• Make some temperature settings more common based on ambient air temperature(Should be a separate Issue and PR)
• Finish Pull Request formatting

Discord username (if different from GitHub): Rare Potato#9693

Testing instructions

Load plane multiple times checking that the A/C Selector knobs change position based on the logged
"WASM: A/C Knob Rounded Variable"

How to download the PR for QA

Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, click on the bottom PR tab
4. Click on the A32NX download link at the bottom of the page

[rare-potato]

I'd really like some input on if the current changes are in an appropriate location in reference to src/fbw/src/FlyByWireInterface.cpp and src/fbw/src/FlyByWireInterface.h.

I personally feel that these are not the appropriate locations but am unsure of where else I could implement this.

[tracernz]

Take a look in https://github.com/flybywiresim/a32nx/tree/master/src/systems. The readme there explains some basics. Drill into the systems and a320_systems directories to find the code.

[wpine215]

Will this be revisited anytime soon?

[rare-potato]

Yeah, I'll go ahead and mark this closed since it's been so long since I last worked on it. I might revisit the issue at a later date with a new PR on a later fork if someone else doesn't pick it up before hand.

[tracernz]

It appeared this was pretty close? Did it just need rebased, or still some implementation left to do?

[rare-potato]

@tracernz It mainly needed to be finished rebasing implementing of the rebase from my initial implementation. If I recall correctly I had successfully moved the logic portion to Rust but was having difficulty understanding the airframe initialization dataflow and never got around to finding someone to help me better understand it.

In other words, I wasn't able to figure out how exactly when/where the initialization of the airframe occurred to set the appropriate SIMVARS but wouldn't repeat itself.