JoePfeiffer d2f364f086 Correctly identify when time is past end of thrustcurve so thrust is 0 in getAverageThrust
This has been lurking -- we're not actually supposed to be calling getAverageThrustThrust when we're past the end of the thrustcurve (there's a test for whether the motor is active before calling it), but another bug in the parallel staging code exposed it.
2022-03-04 17:52:44 -07:00
..
2018-09-29 16:17:33 -06:00