Orekit issueshttps://gitlab.orekit.org/orekit/orekit/-/issues2019-07-05T17:42:37Zhttps://gitlab.orekit.org/orekit/orekit/-/issues/550Download url of the latest Orekit archives not provided in technical document...2019-07-05T17:42:37ZSébastien Dinotsebastien.dinot@csgroup.euDownload url of the latest Orekit archives not provided in technical documentationDownload url of the latest Orekit archives not provided in the technical documentation generated by Maven:
<https://www.orekit.org/site-orekit-9.3.1/downloads.html>
---
| package | link ...Download url of the latest Orekit archives not provided in the technical documentation generated by Maven:
<https://www.orekit.org/site-orekit-9.3.1/downloads.html>
---
| package | link |
|----------|---------------------------------------------------------------------|
| source | orekit-9.3.1-sources.zip (URL to be defined after official release) |
| binary | orekit-9.3.1.jar (URL to be defined after official release) |
version 9.3.1 downloads (release date: 2019-03-16)
---10.0https://gitlab.orekit.org/orekit/orekit/-/issues/549Eclipse Detector: Re-add the getters and delete deprecated constructors ?2019-07-05T17:41:50ZMaxime JournotEclipse Detector: Re-add the getters and delete deprecated constructors ?In [EclipseDetector](https://gitlab.orekit.org/orekit/orekit/blob/develop/src/main/java/org/orekit/propagation/events/EclipseDetector.java) class, recent changes (see [#535](https://gitlab.orekit.org/orekit/orekit/issues/535)) have:
1. ...In [EclipseDetector](https://gitlab.orekit.org/orekit/orekit/blob/develop/src/main/java/org/orekit/propagation/events/EclipseDetector.java) class, recent changes (see [#535](https://gitlab.orekit.org/orekit/orekit/issues/535)) have:
1. Removed the getters for the occulted and occulting body;
1. Lead to the deprecation of constructor based on a spherical occulting body.
For version 10.0 shall we ?
1. Write back some getters. They can be useful when multiple EclipseDetectors are used and we want to discriminate between them.
Example: Set up 2 EclipseDetectors for Sun occultation, one with the Earth and the other one with the Moon as the occulting body.
Use an event logger to log the events.
After propagation, how can we distinguish between Earth eclipses and Moon eclipses if we don't have access to the occulting body name ?
Maybe there is another way to do it but I don't know how...
1. Delete the deprecated constructors and the inner class `SphericalOccultingBody`.
Though it seems ok to me to keep the older constructors for users that just want to use "simple" spherical-based occultation.
On the other hand we could simply document how to use a spherical body, as @luc explains it in issue #535.
What do you think ?10.0https://gitlab.orekit.org/orekit/orekit/-/issues/548Organization of the models package2019-07-05T17:41:51ZBryan CazabonneOrganization of the models packageA discussion has been open in the [forum](https://forum.orekit.org/t/package-organization-in-orekit/472) for this enhancement. The goal is to have a clean organization by adding sub-packages for ionospheric, tropospheric and global weath...A discussion has been open in the [forum](https://forum.orekit.org/t/package-organization-in-orekit/472) for this enhancement. The goal is to have a clean organization by adding sub-packages for ionospheric, tropospheric and global weather models.10.0Bryan CazabonneBryan Cazabonnehttps://gitlab.orekit.org/orekit/orekit/-/issues/546Update pom.xml to Hipparchus 1.52019-07-05T17:41:51ZMaxime JournotUpdate pom.xml to Hipparchus 1.5Hipparchus 1.5 was released a week ago.
We can now update the pom.xml of Orekit.Hipparchus 1.5 was released a week ago.
We can now update the pom.xml of Orekit.10.0https://gitlab.orekit.org/orekit/orekit/-/issues/545.mailmap file is out of date2019-07-05T17:42:36ZSébastien Dinotsebastien.dinot@csgroup.eu.mailmap file is out of dateThe [.mailmap](https://gitlab.orekit.org/orekit/orekit/blob/develop/.mailmap) file is quite out of date. As it stands, Orekit seems to have been developed by 49 different people, but in reality, the project has only 33 contributors.
The...The [.mailmap](https://gitlab.orekit.org/orekit/orekit/blob/develop/.mailmap) file is quite out of date. As it stands, Orekit seems to have been developed by 49 different people, but in reality, the project has only 33 contributors.
The merge request !4 is proposed to fix this issue.10.0https://gitlab.orekit.org/orekit/orekit/-/issues/541README enhancement2019-07-05T17:42:35ZSébastien Dinotsebastien.dinot@csgroup.euREADME enhancementIn my humble opinion, the [README file](https://gitlab.orekit.org/orekit/orekit/blob/master/README.txt) provided with Orekit source code is totally old-fashioned:
* It uses the plain text format rather than a lightweight markup language...In my humble opinion, the [README file](https://gitlab.orekit.org/orekit/orekit/blob/master/README.txt) provided with Orekit source code is totally old-fashioned:
* It uses the plain text format rather than a lightweight markup language such as [Markdown](https://daringfireball.net/projects/markdown/) or [reStructuredText](http://docutils.sourceforge.net/rst.html).
* It is poor in information (no indication is provided, for example, on how to contribute, or how to report a bug).
Several initiatives have attempted to list good practices regarding the content of a README file and/or to provide README templates:
* [Readme Best Practices](https://github.com/jehna/readme-best-practices)
* [Art of README](https://github.com/noffle/art-of-readme)
I think that Orekit merits such modern README file.10.0https://gitlab.orekit.org/orekit/orekit/-/issues/518AbstractGNSSAttitudeProvider should be private package2019-07-05T17:41:50ZPetrus HyvönenAbstractGNSSAttitudeProvider should be private packageThe AbstractGNSSAttitudeProvider is not usable outside the attitude package and was not intented (ref Luc) for public usage. This package should thus be set private.The AbstractGNSSAttitudeProvider is not usable outside the attitude package and was not intented (ref Luc) for public usage. This package should thus be set private.10.0https://gitlab.orekit.org/orekit/orekit/-/issues/506Delete FieldEventHandler.Action2019-07-05T17:41:50ZEvan WardDelete FieldEventHandler.Action`FieldEventHandler.Action` just duplicates `EventHandler.Action` without adding any field specific behavior or information. Remove the duplicate enum and just use `EventHandler.Action`. It may be worth moving `Action` to a top level type...`FieldEventHandler.Action` just duplicates `EventHandler.Action` without adding any field specific behavior or information. Remove the duplicate enum and just use `EventHandler.Action`. It may be worth moving `Action` to a top level type to clarify it can be used for field and non-field event detectors. Hipparchus only uses one Action enum for both double and Field ODEs. This change will break backward compatibility, so it should wait until the next major release.
Other option is to delete both of Orekit's Action enums and just use Action from Hipparchus since they must all define the same values for Orekit to work correctly.10.0