Orekit merge requestshttps://gitlab.orekit.org/orekit/orekit/-/merge_requests2024-03-16T14:25:37Zhttps://gitlab.orekit.org/orekit/orekit/-/merge_requests/465Closes #1296: Make lazy loading of UTC thread safe by checking if already...2024-03-16T14:25:37ZChristopher SchankCloses #1296: Make lazy loading of UTC thread safe by checking if already...Fix issue-1296: Make lazy loading of UTC thread safe by checking if already loaded inside synchronized block
Closes #1296Fix issue-1296: Make lazy loading of UTC thread safe by checking if already loaded inside synchronized block
Closes #129612.0.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/462Draft: Fixed issue 1273: Resolve "TimeSystem parsing in SP3Parser"2024-03-16T14:26:17ZMark RuttenDraft: Fixed issue 1273: Resolve "TimeSystem parsing in SP3Parser"Closes #1273.
I've fixed the bug and added a single test. I've included a partial QZSS SP3 file, with the number of time-steps edited down to one.Closes #1273.
I've fixed the bug and added a single test. I've included a partial QZSS SP3 file, with the number of time-steps edited down to one.12.0.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/445Resolve "Concurrency in LazyLoadedTimeScales"2023-11-02T09:25:05ZLuc MaisonobeResolve "Concurrency in LazyLoadedTimeScales"https://gitlab.orekit.org/orekit/orekit/-/issues/1250
Closes #1256https://gitlab.orekit.org/orekit/orekit/-/issues/1250
Closes #125612.0https://gitlab.orekit.org/orekit/orekit/-/merge_requests/369Stop using internal JDK methods (needed for Java 17 compilation)2023-06-30T12:08:33ZLUGANStop using internal JDK methods (needed for Java 17 compilation)11.3.3https://gitlab.orekit.org/orekit/orekit/-/merge_requests/343Modification of GLONASS parser per issue 10332023-02-16T22:17:02ZJonathan HoodModification of GLONASS parser per issue 1033modified GLONASS parser to set ToC and Date directly to ingested date instead of rounded GPS date per RINEX 8.1 specifications noting that GLONASS time is aligned with UTC and not with GPS timemodified GLONASS parser to set ToC and Date directly to ingested date instead of rounded GPS date per RINEX 8.1 specifications noting that GLONASS time is aligned with UTC and not with GPS time11.3.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/298Fix issue 924: Numerical noise in ThrustPropulsionModel and tests2022-09-16T14:17:31ZMaxime JournotFix issue 924: Numerical noise in ThrustPropulsionModel and testsFixes #924.
@evanward1 , I put you as reviewer as you opened the issue.
I simply removed the incriminated comments.
There is indeed a numerical difference when doing:
1. `acc = new Vector3D(thrust / s.getMass(), maneuverAttitude.get...Fixes #924.
@evanward1 , I put you as reviewer as you opened the issue.
I simply removed the incriminated comments.
There is indeed a numerical difference when doing:
1. `acc = new Vector3D(thrust / s.getMass(), maneuverAttitude.getRotation().applyInverseTo(direction));` (current code)
2. `acc = new Vector3D(1. / s.getMass(), maneuverAttitude.getRotation().applyInverseTo(thrustVector));` (better code?)
(or the `Field` equivalent of these)
It's a small difference due to the usage of `getNorm()` for the module (about 1e-17/18 on the acceleration norm in the tests I have checked).
The thing is, before we changed the `maneuvers` package it was like (1) and we left it like this.
Mostly because some tests in `PolynomialAccelerationTest` and `HarmonicAccelerationModelTest` compare the outputs of propagation to a propagation with an equivalent maneuver.
Since the definition of the forces is given like (1) in `PolynomialAcceleration` and `HarmonicAccelerationModel` tests, the differences are all zeros.
If we use (2) in `ThrustPropulsionModel`, numerical differences appear because of integration of the acceleration during propagation.
(See for example `PolynomialAccelerationTest#testEquivalentTangentialManeuver`)
Maybe the tolerances are too tight but I don't feel like changing all the tolerances of the tests for this small change.
Tell me what you think.11.3https://gitlab.orekit.org/orekit/orekit/-/merge_requests/281Fix issue #942: 'N/A' value not recognized for field MANEUVERABLE when parsin...2022-08-02T15:47:24ZGCFix issue #942: 'N/A' value not recognized for field MANEUVERABLE when parsing CDMs- Updated mechanism to read and write N/A values as Maneuverable enum
- Added CDM Parser test for the issue
- Added CDM Writer test for the issue- Updated mechanism to read and write N/A values as Maneuverable enum
- Added CDM Parser test for the issue
- Added CDM Writer test for the issue11.2.1https://gitlab.orekit.org/orekit/orekit/-/merge_requests/278Fixed date offsets just before whole seconds.2022-08-02T15:49:01ZLuc MaisonobeFixed date offsets just before whole seconds.Fixes #935
Fixes #939Fixes #935
Fixes #93911.2.1https://gitlab.orekit.org/orekit/orekit/-/merge_requests/242Use enhanced for-loops2022-03-20T12:51:56ZLars Næsbye ChristensenUse enhanced for-loopsUse enhanced for-loops some places we iterate over an entire array or listUse enhanced for-loops some places we iterate over an entire array or list11.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/239Replace sequential if-statements with switch-case2022-03-20T12:52:17ZLars Næsbye ChristensenReplace sequential if-statements with switch-case11.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/171Fix DateTimeComponents.toString()2021-08-19T17:32:22ZEvan WardFix DateTimeComponents.toString()Delegate to toStringRfc3339(). Previously toString() had three issues:
- could not print times during leap seconds
- could round up to invalid times when within 0.5 ms of the next minute
- generated invalid ISO 8601 because it left ou...Delegate to toStringRfc3339(). Previously toString() had three issues:
- could not print times during leap seconds
- could round up to invalid times when within 0.5 ms of the next minute
- generated invalid ISO 8601 because it left out the time zone
The last point also lost information because the time zone information
was never printed leading to two dates with the same local time having
the same string representation.
The implementation in toStringRfc3339() fixes these issues for all
reasonable dates, but is not backwards compatible with the existing
implementation. In particular it will include the time zone information
and emit more digits to avoid rounding up.
Fix #59011.0https://gitlab.orekit.org/orekit/orekit/-/merge_requests/100Resolve "initial blanks in some gravity fields headers prevent loading them"2020-11-05T13:21:41ZLuc MaisonobeResolve "initial blanks in some gravity fields headers prevent loading them"Closes #731Closes #73110.3https://gitlab.orekit.org/orekit/orekit/-/merge_requests/99Resolve "initial blanks in some gravity fields headers prevent loading them"2020-11-05T12:44:16ZLuc MaisonobeResolve "initial blanks in some gravity fields headers prevent loading them"Closes #731Closes #73110.3https://gitlab.orekit.org/orekit/orekit/-/merge_requests/66Issue #6052020-05-15T08:47:03ZBryan CazabonneIssue #605Fix issue #605Fix issue #60510.2https://gitlab.orekit.org/orekit/orekit/-/merge_requests/29Issue #5552021-03-10T10:40:44ZGautreau DylanIssue #555Added pathDelay methods that take PVCoordinatesProvider for the satellite and the receiver for ionospheric models :
`pathDelay(AbsoluteDate date, PVCoordinatesProvider sat, PVCoordinatesProvider rec, BodyShape body, double frequency, do...Added pathDelay methods that take PVCoordinatesProvider for the satellite and the receiver for ionospheric models :
`pathDelay(AbsoluteDate date, PVCoordinatesProvider sat, PVCoordinatesProvider rec, BodyShape body, double frequency, double[] parameters)`
Also added tests to check consistency between pathDelay methods.11.0https://gitlab.orekit.org/orekit/orekit/-/merge_requests/492Fix #13392024-03-06T22:51:42ZSébastien Dinotsebastien.dinot@csgroup.euFix #1339Fix #1339
Signed-off-by: Sebastien Dinot <sebastien.dinot@csgroup.eu>Fix #1339
Signed-off-by: Sebastien Dinot <sebastien.dinot@csgroup.eu>https://gitlab.orekit.org/orekit/orekit/-/merge_requests/443Draft: Fixed 1218: extend reset-at-end mechanism to analytical propagators2023-11-03T12:58:23ZRomain SerraDraft: Fixed 1218: extend reset-at-end mechanism to analytical propagatorsCloses #1218Closes #1218Romain SerraRomain Serrahttps://gitlab.orekit.org/orekit/orekit/-/merge_requests/428Issue 12312023-10-17T18:57:40ZAlberto FerreroIssue 1231Fix bug on `buildBox` constructor, to respect parent coefficients orderFix bug on `buildBox` constructor, to respect parent coefficients orderhttps://gitlab.orekit.org/orekit/orekit/-/merge_requests/427Draft: Issue 1225 Adding missing FieldLongitudeCrossingDetector2023-10-18T21:36:50ZAlberto FerreroDraft: Issue 1225 Adding missing FieldLongitudeCrossingDetectorCloses #1225
As per title, the detector was missing
Please, merge after: https://gitlab.orekit.org/orekit/orekit/-/merge_requests/424 to clean commit historyCloses #1225
As per title, the detector was missing
Please, merge after: https://gitlab.orekit.org/orekit/orekit/-/merge_requests/424 to clean commit historyhttps://gitlab.orekit.org/orekit/orekit/-/merge_requests/425Issue 12152023-10-07T16:14:11ZAlberto FerreroIssue 1215