Package org.orekit.forces.maneuvers

Class FieldImpulseManeuver<T extends CalculusFieldElement<T>>

java.lang.Object
org.orekit.forces.maneuvers.AbstractImpulseManeuver
org.orekit.forces.maneuvers.FieldImpulseManeuver<T>
Type Parameters:
T - type of the field elements
All Implemented Interfaces:
FieldDetectorModifier<T>, FieldEventDetector<T>
public class FieldImpulseManeuver<T extends CalculusFieldElement<T>> extends AbstractImpulseManeuver implements FieldDetectorModifier<T>
Impulse maneuver model for propagators working with Fields.

This class implements an impulse maneuver as a discrete event that can be provided to any Propagator and mirrors the standard version ImpulseManeuver.

The maneuver is executed when an underlying event is triggered and the handler returns anything but CONTINUE, in which case this class will generate a RESET_STATE event. In the simple cases, the underlying event detector may be a basic date event, but it can also be a more elaborate apside event for apogee maneuvers for example.

The maneuver velocity increment is defined via FieldImpulseProvider. If no AttitudeProvider is given, the current attitude of the spacecraft, defined by the current spacecraft state, will be used as the AttitudeProvider so the velocity increment should be given in the same pseudoinertial frame as the FieldSpacecraftState used to construct the propagator that will handle the maneuver. If an AttitudeProvider is given, the velocity increment given should be defined appropriately in consideration of that provider. So, a typical case for tangential maneuvers is to provide a LOF aligned attitude provider along with a velocity increment defined in accordance with that LOF aligned attitude provider; e.g. if the LOF aligned attitude provider was constructed using LOFType.VNC the velocity increment should be provided in VNC coordinates.

The norm through which the delta-V maps to the mass consumption is chosen via the enum Control3DVectorCostType. Default is Euclidean.

Beware that the triggering event detector must behave properly both before and after maneuver. If for example a node detector is used to trigger an inclination maneuver and the maneuver change the orbit to an equatorial one, the node detector will fail just after the maneuver, being unable to find a node on an equatorial orbit! This is a real case that has been encountered during validation ...

Since:
12.0
Author:
Romain Serra
See Also: