Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Orekit
Orekit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Orekit
  • OrekitOrekit
  • Issues
  • #742

Closed
Open
Opened Dec 11, 2020 by Maxime Journot@MaximeJDeveloper

Allow determination of maneuver start/stop time

This issue was opened following a question from user Sacha on the forum.

As of now maneuver estimation (using batch least square or Kalman estimators) only allows the determination of ΔV vector but not the maneuver's date and/or duration.

It would be a good addition to allow determining date and duration.
@luc suggests to allow this for two independent parameters like:

  • start date and stop date
  • central date and duration

Related forum thread is here.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
11.1
Milestone
11.1
Assign milestone
Time tracking
None
Due date
None
Reference: orekit/orekit#742