FieldPVCoordinatesProvider<T>
FieldBoundedPropagator<T>
FieldAbstractAnalyticalPropagator
, FieldAbstractIntegratedPropagator
, FieldAbstractPropagator
, FieldEcksteinHechlerPropagator
, FieldIntegratedEphemeris
, FieldKeplerianPropagator
, FieldNumericalPropagator
public interface FieldPropagator<T extends RealFieldElement<T>> extends FieldPVCoordinatesProvider<T>
This interface is the top-level abstraction for orbit propagation. It only allows propagation to a predefined date. It is implemented by analytical models which have no time limit, by orbit readers based on external data files, by numerical integrators using rich force models and by continuous models built after numerical integration has been completed and dense output data as been gathered.
Modifier and Type | Field | Description |
---|---|---|
static AttitudeProvider |
DEFAULT_LAW |
Default attitude provider.
|
static double |
DEFAULT_MASS |
Default mass.
|
static int |
EPHEMERIS_GENERATION_MODE |
Indicator for ephemeris generation mode.
|
static int |
MASTER_MODE |
Indicator for master mode.
|
static int |
SLAVE_MODE |
Indicator for slave mode.
|
Modifier and Type | Method | Description |
---|---|---|
void |
addAdditionalStateProvider(FieldAdditionalStateProvider<T> additionalStateProvider) |
Add a set of user-specified state parameters to be computed along with the orbit propagation.
|
<D extends FieldEventDetector<T>> |
addEventDetector(D detector) |
Add an event detector.
|
void |
clearEventsDetectors() |
Remove all events detectors.
|
List<FieldAdditionalStateProvider<T>> |
getAdditionalStateProviders() |
Get an unmodifiable list of providers for additional state.
|
AttitudeProvider |
getAttitudeProvider() |
Get attitude provider.
|
Collection<FieldEventDetector<T>> |
getEventsDetectors() |
Get all the events detectors that have been added.
|
Frame |
getFrame() |
Get the frame in which the orbit is propagated.
|
FieldBoundedPropagator<T> |
getGeneratedEphemeris() |
Get the ephemeris generated during propagation.
|
FieldSpacecraftState<T> |
getInitialState() |
Get the propagator initial state.
|
String[] |
getManagedAdditionalStates() |
Get all the names of all managed states.
|
int |
getMode() |
Get the current operating mode of the propagator.
|
boolean |
isAdditionalStateManaged(String name) |
Check if an additional state is managed.
|
FieldSpacecraftState<T> |
propagate(FieldAbsoluteDate<T> target) |
Propagate towards a target date.
|
FieldSpacecraftState<T> |
propagate(FieldAbsoluteDate<T> start,
FieldAbsoluteDate<T> target) |
Propagate from a start date towards a target date.
|
void |
resetInitialState(FieldSpacecraftState<T> state) |
Reset the propagator initial state.
|
void |
setAttitudeProvider(AttitudeProvider attitudeProvider) |
Set attitude provider.
|
void |
setEphemerisMode() |
Set the propagator to ephemeris generation mode.
|
void |
setMasterMode(FieldOrekitStepHandler<T> handler) |
Set the propagator to master mode with variable steps.
|
void |
setMasterMode(T h,
FieldOrekitFixedStepHandler<T> handler) |
Set the propagator to master mode with fixed steps.
|
void |
setSlaveMode() |
Set the propagator to slave mode.
|
getPVCoordinates
static final double DEFAULT_MASS
static final AttitudeProvider DEFAULT_LAW
static final int SLAVE_MODE
static final int MASTER_MODE
static final int EPHEMERIS_GENERATION_MODE
int getMode()
void setSlaveMode()
This mode is used when the user needs only the final orbit at the target time. The (slave) propagator computes this result and return it to the calling (master) application, without any intermediate feedback.
This is the default mode.
void setMasterMode(T h, FieldOrekitFixedStepHandler<T> handler)
This mode is used when the user needs to have some custom function called at the end of each finalized step during integration. The (master) propagator integration loop calls the (slave) application callback methods at each finalized step.
h
- fixed stepsize (s)handler
- handler called at the end of each finalized stepsetSlaveMode()
,
setMasterMode(FieldOrekitStepHandler)
,
setEphemerisMode()
,
getMode()
,
MASTER_MODE
void setMasterMode(FieldOrekitStepHandler<T> handler)
This mode is used when the user needs to have some custom function called at the end of each finalized step during integration. The (master) propagator integration loop calls the (slave) application callback methods at each finalized step.
handler
- handler called at the end of each finalized stepsetSlaveMode()
,
setMasterMode(RealFieldElement, FieldOrekitFixedStepHandler)
,
setEphemerisMode()
,
getMode()
,
MASTER_MODE
void setEphemerisMode()
This mode is used when the user needs random access to the orbit state at any time between the initial and target times, and in no sequential order. A typical example is the implementation of search and iterative algorithms that may navigate forward and backward inside the propagation range before finding their result.
Beware that since this mode stores all intermediate results, it may be memory intensive for long integration ranges and high precision/short time steps.
FieldBoundedPropagator<T> getGeneratedEphemeris() throws IllegalStateException
IllegalStateException
- if the propagator was not set in ephemeris
generation mode before propagationsetEphemerisMode()
FieldSpacecraftState<T> getInitialState() throws OrekitException
OrekitException
- if state cannot be retrievedvoid resetInitialState(FieldSpacecraftState<T> state) throws OrekitException
state
- new initial state to considerOrekitException
- if initial state cannot be resetvoid addAdditionalStateProvider(FieldAdditionalStateProvider<T> additionalStateProvider) throws OrekitException
additionalStateProvider
- provider for additional stateOrekitException
- if an additional state with the same name is already presentList<FieldAdditionalStateProvider<T>> getAdditionalStateProviders()
boolean isAdditionalStateManaged(String name)
Managed states are states for which the propagators know how to compute
its evolution. They correspond to additional states for which an
additional state provider
has been registered
by calling the addAdditionalStateProvider
method. If the propagator is an integrator-based
propagator
, the states for which a set of additional equations
has
been registered by calling the addAdditionalEquations
method are also counted as managed additional states.
Additional states that are present in the initial state
but have no evolution method registered are not considered as managed states.
These unmanaged additional states are not lost during propagation, though. Their
value will simply be copied unchanged throughout propagation.
name
- name of the additional stateString[] getManagedAdditionalStates()
<D extends FieldEventDetector<T>> void addEventDetector(D detector)
D
- class type for the generic versiondetector
- event detector to addclearEventsDetectors()
,
getEventsDetectors()
Collection<FieldEventDetector<T>> getEventsDetectors()
addEventDetector(FieldEventDetector)
,
clearEventsDetectors()
void clearEventsDetectors()
AttitudeProvider getAttitudeProvider()
void setAttitudeProvider(AttitudeProvider attitudeProvider)
attitudeProvider
- attitude providerFrame getFrame()
The propagation frame is the definition frame of the initial state, so this method should be called after this state has been set, otherwise it may return null.
resetInitialState(FieldSpacecraftState)
FieldSpacecraftState<T> propagate(FieldAbsoluteDate<T> target) throws OrekitException
Simple propagators use only the target date as the specification for computing the propagated state. More feature rich propagators can consider other information and provide different operating modes or G-stop facilities to stop at pinpointed events occurrences. In these cases, the target date is only a hint, not a mandatory objective.
target
- target date towards which orbit state should be propagatedOrekitException
- if state cannot be propagatedFieldSpacecraftState<T> propagate(FieldAbsoluteDate<T> start, FieldAbsoluteDate<T> target) throws OrekitException
Those propagators use a start date and a target date to compute the propagated state. For propagators using event detection mechanism, if the provided start date is different from the initial state date, a first, simple propagation is performed, without processing any event computation. Then complete propagation is performed from start date to target date.
start
- start date from which orbit state should be propagatedtarget
- target date to which orbit state should be propagatedOrekitException
- if state cannot be propagatedCopyright © 2002-2018 CS Systèmes d'information. All rights reserved.