|
Size: 2501
Comment:
|
← Revision 20 as of 2018-10-30 10:46:47 ⇥
Size: 4323
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| ===== (Compiled by TC) ===== | ||Category B||Version 3.0|| |
| Line 5: | Line 6: |
| DYNAMICS augments the nominals file by appending the nominal inertial | This program augments the nominals file by appending the nominal inertial |
| Line 7: | Line 8: |
| to two images before and after. This information is used to | to four images before and after. This information is used to |
| Line 9: | Line 10: |
| 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]]. In version 3.1, the number of images that is used before/after is set in [[INIT_LITHOS.TXT]] with keyword DYNO. Dynamics will use[[INIT_LITHOS.TXT]] to set the parameters for SPICE. This is set with keyword PCK. Typically, we set the leap second kernel and the PCK. If you want to have these the images before/after impact the location of the spacecraft, then the PICWTS option 5 (WT) must be set to 1 (or a non-zero value) in [[INIT_LITHOS.TXT]] === Required Files === * [[DYNAMICS.TXT]] * [[NOMINALS]]/ * [[SUMFILES]]/ * [[INIT_LITHOS.TXT]] === 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 47: |
| 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 59: |
A typical '''ETLIM=''' record is: |
|
| Line 21: | Line 65: |
| 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. The images that are included in dynamics are limited by both this number, as well as number of images. Dynamics will stop including images when either of these limits are reached. The second number in ETLM is an estimate of the velocity uncertainty that goes into an uncertainty estimate included in the added records. This velocity uncertainty is used to determine the sigma in position associated with dynamics. A typical value is 1 mm/s; the same as in the example. A larger value will weight the dynamics solution less, while I a smaller value will weight the dynamics solution more. '''FRAME=''' has these three choices: |
| Line 28: | Line 76: |
| 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 79: |
| 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 81: |
| * '''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 90: |
| 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 93: |
| change, another such record would be added to affect subsequent | change, another '''VSIG=''' record would be added to affect subsequent |
| Line 52: | Line 96: |
| 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 100: |
| '''PSIG=''' allows the user to change the pointing sigmas in the nominal files, which are in rad. 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 104: |
| with a larger twist uncertainty since there is only one star tracker. | ---------- |
| Line 62: | Line 106: |
| == Requires == * [[DYNAMICS.TXT]] * [[NOMINALS]]/ * [[SUMFILES]]/ |
''(Compiled by TC) '' |
| Line 67: | Line 108: |
| == Outputs == * Updated NOMINALS |
CategoryPrograms |
dynamics
Category B |
Version 3.0 |
Description
This program augments the nominals file by appending the nominal inertial space position differences between the current image and up to four 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.
In version 3.1, the number of images that is used before/after is set in INIT_LITHOS.TXT with keyword DYNO.
Dynamics will useINIT_LITHOS.TXT to set the parameters for SPICE. This is set with keyword PCK. Typically, we set the leap second kernel and the PCK.
If you want to have these the images before/after impact the location of the spacecraft, then the PICWTS option 5 (WT) must be set to 1 (or a non-zero value) in INIT_LITHOS.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. The images that are included in dynamics are limited by both this number, as well as number of images. Dynamics will stop including images when either of these limits are reached. The second number in ETLM is an estimate of the velocity uncertainty that goes into an uncertainty estimate included in the added records. This velocity uncertainty is used to determine the sigma in position associated with dynamics. A typical value is 1 mm/s; the same as in the example. A larger value will weight the dynamics solution less, while I a smaller value will weight the dynamics solution more.
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, which are in rad. 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)