Differences between revisions 7 and 9 (spanning 2 versions)
Revision 7 as of 2016-01-22 11:58:45
Size: 3071
Editor: tcampb
Comment:
Revision 9 as of 2016-01-22 16:45:26
Size: 2501
Editor: tcampb
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
DYNAMIS augments the nominals file by appending the nominal inertial
space position differences dW=W1-W0 between the current image and up
DYNAMICS augments the nominals file by appending the nominal inertial
space position differences between the current image and up
Line 8: Line 8:
constrain the solution in the subroutine IPL2SOBJPTG so that the
s/c
position solution does not deviate too much from a dynamically
realistic state.  An entry ETLIM= in the input DYNAMIS.TXT gives
constrain the solution so that the spacecraft position solution does not deviate too much from a dynamically
realistic state. DYNAMICS also allows for different mission phases to have different "sigmas" via [[DYNAMICS.TXT]].
 
An entry ETLIM= in the input [[DYNAMICS.TXT]]
gives
Line 16: Line 17:
{{{
Line 17: Line 19:
}}}
Line 18: Line 21:
A record FRAME= tells IPL2SOBJPTG how to interpret the sigmas in
spacecrafe position found in the nominals file. The choices are
A record FRAME= specifies how to interpret the sigmas in
spacecraft position found in the nominals file. The choices are
Line 21: Line 24:
{{{
Line 22: Line 26:
}}}
Line 23: Line 28:
The first one uses tha radial direction (R) as prime for the third The first one uses the radial direction (R) as prime for the third
Line 38: Line 43:
{{{
Line 39: Line 45:
}}}
Line 49: Line 56:
{{{
Line 50: Line 58:
}}}
Line 53: Line 62:
The DYNAMIS.TXT file looks just like the PITLIST.TXT file in that
there is a space in the first column. Excerpts from such a file for
DAWN at Vesta are:

FRAME='BOD_FRAME' APPROAH
ETLM= 1800, 1.D-6
VSIG= 0.200, 0.200, 0.200
PSIG= 0.0001, 0.0001, 0.0001
 F11A0001225
 F11A0001241
 ...
 F21A0003895
 F21A0003910
FRAME='dxR_FRAME' SURVEY
ETLM= 1800, 1.D-6
VSIG= 0.100, 0.100, 0.040
PSIG= 0.0001, 0.0001, 0.0001
 F21A0003931
 F21A0003932
 ...
 F21A0032347
 F21A0032348
END

There were a number of parameter changes as the mission progressed
from Approach to Survey to HAMO to LAMO to HAMO2 to Departure, with
transitions between phases requiring parameters of their own.

== Inputs ==
== Requires ==
Line 83: Line 64:
 * NOMINALSMS  * [[NOMINALS]]/
 * [[SU
MFILES]]/
Line 86: Line 68:
 * Updated NOMINALSD  * Updated NOMINALS

dynamics

(Compiled by TC)

Description

DYNAMICS augments the nominals file by appending the nominal inertial space position differences between the current image and up to two images before and after. This information is used to constrain the solution so that the spacecraft position solution does not deviate too much from a dynamically realistic state. DYNAMICS also allows for different mission phases to have different "sigmas" via DYNAMICS.TXT.

An entry ETLIM= in the input DYNAMICS.TXT gives a maximum time difference in seconds that limits the neighboring images to be used, and an estimate of the velocity uncertainty that goes into an uncertainty estimate also is included in the added records. A typical record is:

ETLM=  1800, 1.D-6

A record FRAME= specifies how to interpret the sigmas in spacecraft position found in the nominals file. The choices are

FRAME= ['dxR_FRAME', 'Dxr_FRAME', 'BOD_FRAME']

The first one uses the radial direction (R) as prime for the third component with the second component being the cross track direction (X) and the first component, roughly in the downtrack direction completing the right-handed coordinate system. This is used in orbital operations around large bodies, where the radial component is well known from from the Doppler data. The second choice is used during approach where the downtrack velocity is best known. The "radial" (impact parameter) direction is crossed with the downtrack to give the crosstrack direction. The third option simply uses the components in the body-fixed frame, generally with equal uncertainties in each direction.

A record VSIG= allows the user to change the position sigmas from those in the original nominals file. The record:

VSIG= 0.100, 0.100, 0.040

sets the uncertainties in the three components to 100 m, 100 m and 40 m respectively. If, during another mission phase, these sigmas change, another such record would be added to affect subsequent nominals files.

A record PSIG= allows the user to change the pointing sigmas in the nominal files. The three components refer to rotations about the three camera axes. For OSIRIS_REx we expect something like:

PSIG= 0.0003, 0.0003, 0.0005

with a larger twist uncertainty since there is only one star tracker.

Requires

Outputs

  • Updated NOMINALS

dynamics (last edited 2018-10-30 10:46:47 by EricPalmer)