Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Orekit Orekit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Orekit
  • OrekitOrekit
  • Issues
  • #885
Closed (duplicated) (duplicated)
Open
Created Jan 18, 2022 by Luc Maisonobe@lucOwner

Allow duplicate dates in TimeSpanMap

There are cases when the same date is used twice in TimeSpanMap. One such example is in TimeSpanEstimatedTroposphericModel, where there are two methods addTroposphericModelValidBefore and addTroposphericModelValidAfter which are both called from AbstractOrbitDetermination (in the unit tests and in the tutorials) with the exact same epoch.

This was explicitly forbidden in TimeSpanMap API, but it seems to be useful, so it should be supported.

Currently, depending on how the changes for issue #833 (closed) are implemented, this makes some test fail as tropospheric models are not set up properly.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking