1   /* Copyright 2010-2011 Centre National d'Études Spatiales
2    * Licensed to CS GROUP (CS) under one or more
3    * contributor license agreements.  See the NOTICE file distributed with
4    * this work for additional information regarding copyright ownership.
5    * CS licenses this file to You under the Apache License, Version 2.0
6    * (the "License"); you may not use this file except in compliance with
7    * the License.  You may obtain a copy of the License at
8    *
9    *   http://www.apache.org/licenses/LICENSE-2.0
10   *
11   * Unless required by applicable law or agreed to in writing, software
12   * distributed under the License is distributed on an "AS IS" BASIS,
13   * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14   * See the License for the specific language governing permissions and
15   * limitations under the License.
16   */
17  package org.orekit.propagation.integration;
18  
19  import org.hipparchus.CalculusFieldElement;
20  import org.orekit.propagation.FieldSpacecraftState;
21  import org.orekit.time.FieldAbsoluteDate;
22  
23  /** This interface allows users to add their own differential equations to a numerical propagator.
24   *
25   * <p>
26   * In some cases users may need to integrate some problem-specific equations along with
27   * classical spacecraft equations of motions. One example is optimal control in low
28   * thrust where adjoint parameters linked to the minimized Hamiltonian must be integrated.
29   * Another example is formation flying or rendez-vous which use the Clohessy-Whiltshire
30   * equations for the relative motion.
31   * </p>
32   * <p>
33   * This interface allows users to add such equations to a {@link
34   * org.orekit.propagation.numerical.FieldNumericalPropagator numerical propagator}. Users provide the
35   * equations as an implementation of this interface and register it to the propagator thanks to
36   * its {@link org.orekit.propagation.numerical.FieldNumericalPropagator#addAdditionalEquations(FieldAdditionalEquations)}
37   * method. Several such objects can be registered with each numerical propagator, but it is
38   * recommended to gather in the same object the sets of parameters which equations can interact
39   * on each others states.
40   * </p>
41   * <p>
42   * The additional parameters are gathered in a simple p array. The additional equations compute
43   * the pDot array, which is the time-derivative of the p array. Since the additional parameters
44   * p may also have an influence on the equations of motion themselves that should be accumulated
45   * to the main state derivatives (for example an equation linked to a complex thrust model may
46   * induce an acceleration and a mass change), the {@link #computeDerivatives(FieldSpacecraftState,
47   * CalculusFieldElement[]) computeDerivatives} method can return a double array that will be
48   * <em>added</em> to the main state derivatives. This means these equations can be used as an
49   * additional force model if needed. If the additional parameters have no influence at all on
50   * the main spacecraft state, a null reference may be returned.
51   * </p>
52   * <p>
53   * This interface is the numerical (read not already integrated) counterpart of
54   * the {@link org.orekit.propagation.FieldAdditionalStateProvider} interface.
55   * It allows to append various additional state parameters to any {@link
56   * org.orekit.propagation.numerical.FieldNumericalPropagator numerical propagator}.
57   * </p>
58   * @see AbstractIntegratedPropagator
59   * @see org.orekit.propagation.FieldAdditionalStateProvider
60   * @author Luc Maisonobe
61   * @deprecated as of 11.1, replaced by {@link FieldAdditionalDerivativesProvider}
62   */
63  @Deprecated
64  public interface FieldAdditionalEquations<T extends CalculusFieldElement<T>> {
65  
66      /** Get the name of the additional state.
67       * @return name of the additional state
68       */
69      String getName();
70  
71      /**
72       * Initialize the equations at the start of propagation.
73       *
74       * <p>
75       * This method will be called once at propagation start,
76       * before any calls to {@link #computeDerivatives(FieldSpacecraftState , CalculusFieldElement[])}.
77       * </p>
78       *
79       * <p>
80       * The default implementation of this method does nothing.
81       * </p>
82       *
83       * @param initialState initial state information at the start of propagation.
84       * @param target       date of propagation. Not equal to {@code
85       *                     initialState.getDate()}.
86       */
87      default void init(final FieldSpacecraftState<T> initialState, final FieldAbsoluteDate<T> target) {
88          // nothing by default
89      }
90  
91      /** Compute the derivatives related to the additional state parameters.
92       * <p>
93       * When this method is called, the spacecraft state contains the main
94       * state (orbit, attitude and mass), all the states provided through
95       * the {@link org.orekit.propagation.AdditionalStateProvider additional
96       * state providers} registered to the propagator, and the additional state
97       * integrated using this equation. It does <em>not</em> contains any other
98       * states to be integrated alongside during the same propagation.
99       * </p>
100      * @param s current state information: date, kinematics, attitude, and
101      * additional state
102      * @param pDot placeholder where the derivatives of the additional parameters
103      * should be put
104      * @return cumulative effect of the equations on the main state (may be null if
105      * equations do not change main state at all)
106      */
107     T[] computeDerivatives(FieldSpacecraftState<T> s,  T[] pDot);
108 
109 }