[VOTE] Releasing Orekit 11.3 from release candidate 1

This is a VOTE in order to release version 11.3 of the Orekit library.
Version 11.3 is a minor release.

Highlights in the 11.3 release are:

  • The unscented Kalman filter (numerical version),
  • The semi-analytical unscented Kalman filter (DSST version),
  • A new PVCoordinatesProvider modelling waypoints on an ellipsoid following a loxodrome (commonly, a rhum bline),
  • A new method to compute hyperbolic anomaly based on Gooding and Odell algorithm,
  • A new built-in additional state for covariance propagation (linear method based on the state transition matrix computation),
  • With a new state covariance object allowing covariance transformation between frames and orbit types,
  • And the ability to extrapolate a state covariance matrix using a Keplerian model,
  • A new ExtremumApproachDetector for close encounter computation,
  • The migration of all JUnit tests from JUnit 4 to JUnit 5,
  • The ability to estimate measurement parameters (station position or clock biases) from an ephemeris,
  • New methods to convert from/to Orekit frames and CCSDS frames,
  • Improvements of CCSDS CDM (Collision Data Message) parsers,
  • Improvements in date handling and aggregate bounded propagators,
  • Several bug fixes and documentation improvements.

The release candidate 1 can be found on the GitLab repository as
tag 11.3-RC1 in the release-11.3 branch:

The release notes can be read here:
(Please note that due to an issue with the website generation, the description and date are not generated. They will for the official release. For more details, see the changes.xml file.)

Maven artifacts are available on Sonatype at: Index of /repositories/orgorekit-1060.

The votes will be tallied in 120 hours for now, on 2022-10-25T09:00:00Z
(this is UTC time).

Hi Maxime,

A great release ahead!
About the covariance transformation, by orbit type it is meant that one can go from/to Cartesian to/from Keplerian for instance? In that case I am assuming this is done using the Jacobian matrix? If yes then again, like for the propagated case, there needs to be a clear statement in the documentation that this is a linearization-based approximation.
In general, only Cartesian transformations between frames are actually linear, so that the linearization is then exact.


+1 for the release


Yes again

I don’t think we mentioned this in the documentation…
I don’t think we need to amend the RC1 vote for a documentation improvement since it can be done during a patch release. Therefore, could you open an issue with a ‘Documentation’ label in order to add these information during the next patch release?

Best regards,

+1 from me, a good release!

Hi, great work!

I have tried to do a first wrapping for python and it works fine with the exception of the hipparchus class RosenNumberPartitionIterator. I haven’t digged deep into why it fails on this seemingly trivial class, but when excluding it the wrapper seems to build fine. I don’t think this is critical for having in Python, nor part of orekit 11.3 so +1 for me!

If anyone has any insight of the magic in the roses, please share…

+1 for release.

Paul Cefola

+1 from me.

+1 for the release :wave: !

Great new features!

+1 from me.


+1 from me as well (assuming there will be a Zenodo release :sweat_smile:)

Issue about documentation opened. Sorry for my insistence on that, I just do no want people to think that linearization-based covariance transformation/propagation is the only option, or even worse the exact solution.

@petrus.hyvonen I don’t know what happens with this Hipparchus class. At first I thought it was due to the implements Iterator... but there are many other classes in Hipparchus that are built the same.
You should probably open a separate discussion thread on the forum or an issue on Hipparchus about this .

I understand but unfortunately we cannot know before the official release is out on the Github mirror repository.
It worked for Hipparchus so I’m confident! :slight_smile:

No problem @Serrof, you are right in wanting a better documentation.

This vote passes with +1 from Bryan, Luc, Petrus, Paul, Frank, Vincent, David, Romain, Pascal, Nicolas, Sébastien and myself (some directly on the thread, some on the voting widget and some on a private PMC thread).

I will proceed with the release right away.

1 Like