public class FieldNumericalPropagator<T extends CalculusFieldElement<T>> extends FieldAbstractIntegratedPropagator<T>
orbits using
numerical integration.
Numerical propagation is much more accurate than analytical propagation
like for example Keplerian or Eckstein-Hechler, but requires a few more steps to set up to be used properly.
Whereas analytical propagators are configured only thanks to their various
constructors and can be used immediately after construction, numerical propagators
configuration involve setting several parameters between construction time
and propagation time.
The configuration parameters that can be set are:
setInitialState(FieldSpacecraftState))setMu(CalculusFieldElement))addForceModel(ForceModel),
removeForceModels())type of orbital parameters to be used for propagation
(setOrbitType(OrbitType)),
type of position angle to be used in orbital parameters
to be used for propagation where it is relevant (setPositionAngleType(PositionAngle)),
additional equations
should be propagated along with orbital state
(FieldAbstractIntegratedPropagator.addAdditionalEquations(org.orekit.propagation.integration.FieldAdditionalEquations)),
FieldAbstractIntegratedPropagator.addEventDetector(FieldEventDetector),
FieldAbstractIntegratedPropagator.clearEventsDetectors())FieldAbstractPropagator.getMultiplexer())From these configuration parameters, only the initial state is mandatory. The default
propagation settings are in equinoctial parameters with
true longitude argument. If the central attraction coefficient
is not explicitly specified, the one used to define the initial orbit will be used.
However, specifying only the initial state and perhaps the central attraction coefficient
would mean the propagator would use only Keplerian forces. In this case, the simpler KeplerianPropagator class would
perhaps be more effective.
The underlying numerical integrator set up in the constructor may also have its own configuration parameters. Typical configuration parameters for adaptive stepsize integrators are the min, max and perhaps start step size as well as the absolute and/or relative errors thresholds.
The state that is seen by the integrator is a simple seven elements double array. The six first elements are either:
equinoctial orbit parameters (a, ex,
ey, hx, hy, λM or λE
or λv) in meters and radians,Keplerian orbit parameters (a, e, i, ω, Ω,
M or E or v) in meters and radians,circular orbit parameters (a, ex, ey, i,
Ω, αM or αE or αv) in meters
and radians,Cartesian orbit parameters (x, y, z, vx,
vy, vz) in meters and meters per seconds.
The following code snippet shows a typical setting for Low Earth Orbit propagation in equinoctial parameters and true longitude argument:
final T zero = field.getZero(); final T dP = zero.add(0.001); final T minStep = zero.add(0.001); final T maxStep = zero.add(500); final T initStep = zero.add(60); final double[][] tolerance = FieldNumericalPropagator.tolerances(dP, orbit, OrbitType.EQUINOCTIAL); AdaptiveStepsizeFieldIntegrator<T> integrator = new DormandPrince853FieldIntegrator<>(field, minStep, maxStep, tolerance[0], tolerance[1]); integrator.setInitialStepSize(initStep); propagator = new FieldNumericalPropagator<>(field, integrator);
By default, at the end of the propagation, the propagator resets the initial state to the final state,
thus allowing a new propagation to be started from there without recomputing the part already performed.
This behaviour can be chenged by calling FieldAbstractIntegratedPropagator.setResetAtEnd(boolean).
Beware the same instance cannot be used simultaneously by different threads, the class is not thread-safe.
FieldSpacecraftState,
ForceModel,
FieldOrekitStepHandler,
FieldOrekitFixedStepHandler,
FieldIntegratedEphemeris,
FieldTimeDerivativesEquationsFieldAbstractIntegratedPropagator.MainStateEquations<T extends CalculusFieldElement<T>>DEFAULT_MASS| Constructor and Description |
|---|
FieldNumericalPropagator(Field<T> field,
FieldODEIntegrator<T> integrator)
Create a new instance of NumericalPropagator, based on orbit definition mu.
|
FieldNumericalPropagator(Field<T> field,
FieldODEIntegrator<T> integrator,
AttitudeProvider attitudeProvider)
Create a new instance of NumericalPropagator, based on orbit definition mu.
|
| Modifier and Type | Method and Description |
|---|---|
void |
addForceModel(ForceModel model)
Add a force model to the global perturbation model.
|
protected FieldStateMapper<T> |
createMapper(FieldAbsoluteDate<T> referenceDate,
T mu,
OrbitType orbitType,
PositionAngle positionAngleType,
AttitudeProvider attitudeProvider,
Frame frame)
Create a mapper between raw double components and spacecraft state.
|
List<ForceModel> |
getAllForceModels()
Get all the force models, perturbing forces and Newtonian attraction included.
|
protected FieldAbstractIntegratedPropagator.MainStateEquations<T> |
getMainStateEquations(FieldODEIntegrator<T> integrator)
Get the differential equations to integrate (for main state only).
|
OrbitType |
getOrbitType()
Get propagation parameter type.
|
PositionAngle |
getPositionAngleType()
Get propagation parameter type.
|
TimeStampedFieldPVCoordinates<T> |
getPVCoordinates(FieldAbsoluteDate<T> date,
Frame frame)
Get the
FieldPVCoordinates of the body in the selected frame. |
void |
removeForceModels()
Remove all perturbing force models from the global perturbation model.
|
void |
resetInitialState(FieldSpacecraftState<T> state)
Reset the propagator initial state.
|
void |
setIgnoreCentralAttraction(boolean ignoreCentralAttraction)
Set the flag to ignore or not the creation of a
NewtonianAttraction. |
void |
setInitialState(FieldSpacecraftState<T> initialState)
Set the initial state.
|
void |
setMu(T mu)
Set the central attraction coefficient μ.
|
void |
setOrbitType(OrbitType orbitType)
Set propagation orbit type.
|
void |
setPositionAngleType(PositionAngle positionAngleType)
Set position angle type.
|
static <T extends CalculusFieldElement<T>> |
tolerances(T dP,
FieldOrbit<T> orbit,
OrbitType type)
Estimate tolerance vectors for integrators.
|
static <T extends CalculusFieldElement<T>> |
tolerances(T dP,
T dV,
FieldOrbit<T> orbit,
OrbitType type)
Estimate tolerance vectors for integrators when propagating in orbits.
|
addAdditionalDerivativesProvider, addAdditionalEquations, addEventDetector, afterIntegration, beforeIntegration, clearEventsDetectors, getAdditionalDerivativesProviders, getBasicDimension, getCalls, getEphemerisGenerator, getEventsDetectors, getInitialIntegrationState, getIntegrator, getManagedAdditionalStates, getMu, initMapper, isAdditionalStateManaged, isMeanOrbit, propagate, propagate, setAttitudeProvider, setResetAtEnd, setUpEventDetector, setUpUserEventDetectorsaddAdditionalStateProvider, getAdditionalStateProviders, getAttitudeProvider, getField, getFrame, getInitialState, getMultiplexer, getStartDate, initializePropagation, setStartDate, stateChanged, updateAdditionalStates, updateUnmanagedStatesclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitclearStepHandlers, setStepHandler, setStepHandler@DefaultDataContext public FieldNumericalPropagator(Field<T> field, FieldODEIntegrator<T> integrator)
addForceModel is not
called after creation, the integrated orbit will follow a Keplerian
evolution only. The defaults are OrbitType.EQUINOCTIAL
for propagation
orbit type and PositionAngle.TRUE for position angle type.
This constructor uses the default data context.
integrator - numerical integrator to use for propagation.field - Field used by defaultFieldNumericalPropagator(Field, FieldODEIntegrator, AttitudeProvider)public FieldNumericalPropagator(Field<T> field, FieldODEIntegrator<T> integrator, AttitudeProvider attitudeProvider)
addForceModel is not
called after creation, the integrated orbit will follow a Keplerian
evolution only. The defaults are OrbitType.EQUINOCTIAL
for propagation
orbit type and PositionAngle.TRUE for position angle type.field - Field used by defaultintegrator - numerical integrator to use for propagation.attitudeProvider - attitude law to use.public void setIgnoreCentralAttraction(boolean ignoreCentralAttraction)
NewtonianAttraction.ignoreCentralAttraction - if true, NewtonianAttraction is not
added automatically if missingpublic void setMu(T mu)
Setting the central attraction coefficient is
equivalent to add
a NewtonianAttraction force model.
setMu in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>mu - central attraction coefficient (m³/s²)addForceModel(ForceModel),
getAllForceModels()public void addForceModel(ForceModel model)
If this method is not called at all, the integrated orbit will follow a Keplerian evolution only.
model - perturbing ForceModel to addremoveForceModels(),
setMu(CalculusFieldElement)public void removeForceModels()
Once all perturbing forces have been removed (and as long as no new force model is added), the integrated orbit will follow a Keplerian evolution only.
addForceModel(ForceModel)public List<ForceModel> getAllForceModels()
addForceModel(ForceModel),
setMu(CalculusFieldElement)public void setOrbitType(OrbitType orbitType)
setOrbitType in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>orbitType - orbit type to use for propagationpublic OrbitType getOrbitType()
getOrbitType in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>public void setPositionAngleType(PositionAngle positionAngleType)
The position parameter type is meaningful only if propagation orbit type
support it. As an example, it is not meaningful for propagation
in Cartesian parameters.
setPositionAngleType in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>positionAngleType - angle type to use for propagationpublic PositionAngle getPositionAngleType()
getPositionAngleType in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>public void setInitialState(FieldSpacecraftState<T> initialState)
initialState - initial statepublic void resetInitialState(FieldSpacecraftState<T> state)
resetInitialState in interface FieldPropagator<T extends CalculusFieldElement<T>>resetInitialState in class FieldAbstractPropagator<T extends CalculusFieldElement<T>>state - new initial state to considerpublic TimeStampedFieldPVCoordinates<T> getPVCoordinates(FieldAbsoluteDate<T> date, Frame frame)
FieldPVCoordinates of the body in the selected frame.getPVCoordinates in interface FieldPVCoordinatesProvider<T extends CalculusFieldElement<T>>getPVCoordinates in class FieldAbstractPropagator<T extends CalculusFieldElement<T>>date - current dateframe - the frame where to define the positionprotected FieldStateMapper<T> createMapper(FieldAbsoluteDate<T> referenceDate, T mu, OrbitType orbitType, PositionAngle positionAngleType, AttitudeProvider attitudeProvider, Frame frame)
The position parameter type is meaningful only if propagation orbit type
support it. As an example, it is not meaningful for propagation
in Cartesian parameters.
createMapper in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>referenceDate - reference datemu - central attraction coefficient (m³/s²)orbitType - orbit type to use for mappingpositionAngleType - angle type to use for propagationattitudeProvider - attitude providerframe - inertial frameprotected FieldAbstractIntegratedPropagator.MainStateEquations<T> getMainStateEquations(FieldODEIntegrator<T> integrator)
getMainStateEquations in class FieldAbstractIntegratedPropagator<T extends CalculusFieldElement<T>>integrator - numerical integrator to use for propagation.public static <T extends CalculusFieldElement<T>> double[][] tolerances(T dP, FieldOrbit<T> orbit, OrbitType type)
The errors are estimated from partial derivatives properties of orbits, starting from a scalar position error specified by the user. Considering the energy conservation equation V = sqrt(mu (2/r - 1/a)), we get at constant energy (i.e. on a Keplerian trajectory):
V r² |dV| = mu |dr|So we deduce a scalar velocity error consistent with the position error. From here, we apply orbits Jacobians matrices to get consistent errors on orbital parameters.
The tolerances are only orders of magnitude, and integrator tolerances are only local estimates, not global ones. So some care must be taken when using these tolerances. Setting 1mm as a position error does NOT mean the tolerances will guarantee a 1mm error position after several orbits integration.
T - elements typedP - user specified position errororbit - reference orbittype - propagation type for the meaning of the tolerance vectors elements
(it may be different from orbit.getType())public static <T extends CalculusFieldElement<T>> double[][] tolerances(T dP, T dV, FieldOrbit<T> orbit, OrbitType type)
The errors are estimated from partial derivatives properties of orbits, starting from scalar position and velocity errors specified by the user.
The tolerances are only orders of magnitude, and integrator tolerances are only local estimates, not global ones. So some care must be taken when using these tolerances. Setting 1mm as a position error does NOT mean the tolerances will guarantee a 1mm error position after several orbits integration.
T - elements typedP - user specified position errordV - user specified velocity errororbit - reference orbittype - propagation type for the meaning of the tolerance vectors elements
(it may be different from orbit.getType())Copyright © 2002-2022 CS GROUP. All rights reserved.