AttitudeSequence generates out-of-sync attitude computation with variable step numerical propagators
When propagating with a variable step propagator a trajectory that uses
an
attitude sequence, displaying the results using a fixed step handler
generates
wrong output. The attitude seems to jump directly to the after switch
attitude
a few seconds before the switch really happens, then when the switch
happens
it goes back to a proper interpolation during the specified transition
time.
The problem is that AttitudeSequence, which should know about the
scheduling
issue between events handlers and ste handlers, is not protected for
out-of-sync
calls.
The issue was first raised by Tom Walford on the users mailing list
(from redmine: issue id 404, created on 2018-03-26, closed on 2018-06-04)