Differences between revisions 9 and 11 (spanning 2 versions)
Revision 9 as of 2016-01-22 16:45:26
Size: 2501
Editor: tcampb
Comment:
Revision 11 as of 2016-01-29 15:41:51
Size: 3247
Editor: BMittan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
===== (Compiled by TC) =====
Line 5: Line 4:
DYNAMICS augments the nominals file by appending the nominal inertial This program augments the nominals file by appending the nominal inertial
Line 9: Line 8:
realistic state. DYNAMICS also allows for different mission phases to have different "sigmas" via [[DYNAMICS.TXT]]. realistic state. This program also allows for different mission phases to have different "sigmas" via [[DYNAMICS.TXT]].

=== Required Files ===
 * [[DYNAMICS.TXT]]
 * [[NOMINALS]]/
 * [[SUMFILES]]/

=== Output Files ===
 * Updated NOMINALS file

-----

== Using dynamics ==

Input for the program in DYNAMICS.TXT includes values for 3 parameters and lists of nominals to which they apply. For additional information, see [[DYNAMICS.TXT]].

The following sample is based on excerpts from a DYNAMICS.TXT file for
DAWN at Vesta:

{{{
FRAME='BOD_FRAME' APPROACH
ETLM= 1800, 1.D-6
VSIG= 0.200, 0.200, 0.200
PSIG= 0.0001, 0.0001, 0.0001
 F11A0001225
 F11A0001241
 ...
 F21A0003895
 F21A0003910
Line 11: Line 38:
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:
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
}}}
Line 17: Line 50:

A typical ETLIM= record is:
Line 21: Line 56:
A record FRAME= specifies how to interpret the sigmas in
spacecraft position found in the nominals file. The choices are
ETLIM= gives
a maximum time difference in seconds that limits the neighboring
images to be used. This is followed by an estimate of the velocity uncertainty that
goes into an uncertainty estimate included in the added records.

FRAME= has these three choices:
Line 28: Line 67:
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.
FRAME= specifies how to interpret the sigmas in
spacecraft position found in the nominals file.
Line 40: Line 70:
A record VSIG= allows the user to change the position sigmas from
those in the original nominals file. The record:
 * '''dxR_FRAME''' 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 the Doppler data.
Line 43: Line 72:
 * '''Dxr_FRAME''' 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.

 * '''BOD_FRAME''' simply uses the components in the body-fixed frame, generally with equal uncertainties in each direction.

The VSIG= record has three components:
Line 47: Line 81:
sets the uncertainties in the three components to 100 m, 100 m and VSIG= allows the user to change the position sigmas from
those in the original nominals file. The record in the sample,
sets the uncertainties in the three components to 100 m, 100 m and
Line 49: Line 84:
change, another such record would be added to affect subsequent change, another VSIG= record would be added to affect subsequent
Line 52: Line 87:
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:
The PSIG= record has three components:
Line 59: Line 91:
PSIG= allows the user to change the pointing sigmas in the
nominal files. The three components refer to rotations about the
three camera axes. The sample shows the approximate values expected for OSIRIS_REx with a larger twist uncertainty since there is only one star tracker.
Line 60: Line 95:
with a larger twist uncertainty since there is only one star tracker.

== Requires ==
 * [[DYNAMICS.TXT]]
 * [[NOMINALS]]/
 * [[SUMFILES]]/

== Outputs ==
 * Updated NOMINALS
-----
''(Compiled by TC) ''

dynamics

Description

This program 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. This program also allows for different mission phases to have different "sigmas" via DYNAMICS.TXT.

Required Files

Output Files

  • Updated NOMINALS file


Using dynamics

Input for the program in DYNAMICS.TXT includes values for 3 parameters and lists of nominals to which they apply. For additional information, see DYNAMICS.TXT.

The following sample is based on excerpts from a DYNAMICS.TXT file for DAWN at Vesta:

FRAME='BOD_FRAME' APPROACH
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

A typical ETLIM= record is:

ETLM=  1800, 1.D-6

ETLIM= gives a maximum time difference in seconds that limits the neighboring images to be used. This is followed by an estimate of the velocity uncertainty that goes into an uncertainty estimate included in the added records.

FRAME= has these three choices:

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

FRAME= specifies how to interpret the sigmas in spacecraft position found in the nominals file.

  • dxR_FRAME 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 the Doppler data.

  • Dxr_FRAME 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.

  • BOD_FRAME simply uses the components in the body-fixed frame, generally with equal uncertainties in each direction.

The VSIG= record has three components:

VSIG= 0.100, 0.100, 0.040

VSIG= allows the user to change the position sigmas from those in the original nominals file. The record in the sample, 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 VSIG= record would be added to affect subsequent nominals files.

The PSIG= record has three components:

PSIG= 0.0003, 0.0003, 0.0005

PSIG= allows the user to change the pointing sigmas in the nominal files. The three components refer to rotations about the three camera axes. The sample shows the approximate values expected for OSIRIS_REx with a larger twist uncertainty since there is only one star tracker.


(Compiled by TC)

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