Closed jeanconn closed 1 year ago
It seems like one could extend this "skip this one" behavior for targ_att not defined (though the NSM code gives [nan, nan, nan, nan] instead of None) or curr_att still not defined around
Or don't add a maneuver transition if curr_att is None etc around https://github.com/sot/kadi/blob/81ff21b98930bffac8efc2dac6c15c74250ffadc/kadi/commands/states.py#L1171
I figure the latter makes good sense.
Thanks for looking into this. I need to understand it a bit better. Hopefully this won't be a showstopper since it does go away if the start of the commanding for continuity does not fall in the intermediate time.
In [1]: from kadi.commands.states import get_continuity
In [3]: cont = get_continuity('2022:301:12:42:32.418', lookbacks=[6, 30, 180, 1000], scenario="flight")
In [4]: cont = get_continuity('2022:301:12:42:32.418', lookbacks=[8, 30, 180, 1000], scenario="flight")
In [5]: try:
...: cont = get_continuity('2022:301:12:42:32.418', lookbacks=[7, 30, 180, 1000], scenario="flight")
...: except Exception:
...: print('dang')
...:
dang
This looks similar to https://github.com/sot/kadi/pull/199 only here it looks like maybe the transition to safe mode while already in NSUN is setting things up for an undefined maneuver transition?