Interface FieldPropagator<T extends org.hipparchus.RealFieldElement<T>>

    • Field Detail

      • DEFAULT_LAW

        static final AttitudeProvider DEFAULT_LAW
        Default attitude provider.
      • EPHEMERIS_GENERATION_MODE

        static final int EPHEMERIS_GENERATION_MODE
        Indicator for ephemeris generation mode.
        See Also:
        Constant Field Values
    • Method Detail

      • getInitialState

        FieldSpacecraftState<T> getInitialState()
        Get the propagator initial state.
        Returns:
        initial state
      • resetInitialState

        void resetInitialState​(FieldSpacecraftState<T> state)
        Reset the propagator initial state.
        Parameters:
        state - new initial state to consider
      • addAdditionalStateProvider

        void addAdditionalStateProvider​(FieldAdditionalStateProvider<T> additionalStateProvider)
        Add a set of user-specified state parameters to be computed along with the orbit propagation.
        Parameters:
        additionalStateProvider - provider for additional state
      • getAdditionalStateProviders

        List<FieldAdditionalStateProvider<T>> getAdditionalStateProviders()
        Get an unmodifiable list of providers for additional state.
        Returns:
        providers for the additional states
      • isAdditionalStateManaged

        boolean isAdditionalStateManaged​(String name)
        Check if an additional state is managed.

        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.

        Parameters:
        name - name of the additional state
        Returns:
        true if the additional state is managed
      • getManagedAdditionalStates

        String[] getManagedAdditionalStates()
        Get all the names of all managed states.
        Returns:
        names of all managed states
      • getAttitudeProvider

        AttitudeProvider getAttitudeProvider()
        Get attitude provider.
        Returns:
        attitude provider
      • setAttitudeProvider

        void setAttitudeProvider​(AttitudeProvider attitudeProvider)
        Set attitude provider.
        Parameters:
        attitudeProvider - attitude provider
      • getFrame

        Frame getFrame()
        Get the frame in which the orbit is propagated.

        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.

        Returns:
        frame in which the orbit is propagated
        See Also:
        resetInitialState(FieldSpacecraftState)
      • propagate

        FieldSpacecraftState<T> propagate​(FieldAbsoluteDate<T> target)
        Propagate towards a target date.

        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.

        Parameters:
        target - target date towards which orbit state should be propagated
        Returns:
        propagated state
      • propagate

        FieldSpacecraftState<T> propagate​(FieldAbsoluteDate<T> start,
                                          FieldAbsoluteDate<T> target)
        Propagate from a start date towards a target date.

        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.

        Parameters:
        start - start date from which orbit state should be propagated
        target - target date to which orbit state should be propagated
        Returns:
        propagated state