Proposed new behaviour of Orbit rates

Orekit development
1

Hi folks,

I’ve always found a bit weird that Orbit can have or not derivatives, depending on how the object was created. A while ago I gave some thoughts about changing this. I think the most natural thing would be that if the user didn’t give anything, then the getADot and like method should return the values consistent with Keplerian motion (so zero except for the anomaly rate), like getMeanMotion for example. I haven’t thought this thru from A to Z, so if somebody thinks that would break something important in Orekit, let me know. And more generally, please give me some feedback on this idea.

Cheers
Romain.

2

I agree with you. This would simplify user code. Returning NaN was an error.

3

Sweet I’ll create an issue for the next major release.

Cheers,
Romain.

1 Like
4

I was thinking: as part of this, could we maybe get rid of the native serialisation routines in Orbit? I’m not sure they’re really used anymore?

Cheers,
Romain.

2 Likes
5

Yes, serialization should probably be removed everywhere in fact, but it deserve a dedicated discussion topic.

1 Like