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 55
    • Issues 55
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • 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
  • #648

Closed
Open
Created Feb 11, 2020 by Maxime Journot@MaximeJDeveloper

Improving forces.maneuvers package

Current forces.maneuvers package only proposes the ConstantThrustManeuver class as a numerical force model that can be integrated during a propagation and estimated with orbit determination.

It has been discussed in the following thread on the forum that it would be a good addition to have a more versatile implementation of numerical maneuvers' models that would allow for:

  • Estimating the direction of the maneuver as well as its norm, with a 3D model that could be customized;
  • Implementing a variable thrust maneuver model (see this other forum thread);
  • Using a ΔV-based definition instead of a thrust-based definition to model, estimate or optimize quasi-impulse maneuvers;
  • Using other triggers than dates to define start and stop of maneuvers;
  • etc.

In that perspective a first implementation of a new maneuver package was proposed and is available on branch maneuver-package.

It is based on the organization proposal given in the first forum thread mentioned here.

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