Uploaded image for project: 'GMAT'
  1. GMAT
  2. GMT-5985

Incorrect reporting of Thrust Scale Factor Solve-for

    Details

      Description

      See attached script (received from DJC unit tests) that first simulates and then solves for an overall thrust scale factor.

      The script sets the initial estimate for the solve-for as follows:

      Thruster1_SetPoint1_Est.ThrustScaleFactor = 0.96

      Run the attached script - you can stop the run after the initial iteration. I would expect that the a priori state would reflect this value of 0.96 but it does not as shown below:

      a priori state:
         Estimation Epoch:
             23430.500370768306 A.1 modified Julian
          ..
         ODProp_ForceModel.Thruster1_SetPoint1_Est.ThrustScaleFactor.1 = 0
      

      Perhaps, GMAT is just reporting a "Delta" from the estimate. If so, this should be an easy reporting fix.

      Build used is GMAT-R2015a-TSF_Solve_For_Build-x86.zip delivered 9/22/2016.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 days
                  3d
                  Remaining:
                  Remaining Estimate - 3 days
                  3d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified