|
Size: 2312
Comment:
|
Size: 4575
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| ||Category B ||Version 3.0.1 || | |
| Line 3: | Line 4: |
| Compiled by KD | |
| Line 6: | Line 6: |
| In general, make_sumfiles ingests images into SPC. It takes in, as a standard input, the name and camera position of the images from [[make_sumfiles.in]]. It will convert the image into the <filename>.DAT format in [[IMAGEFILES]]. It will also generate <filename>.SUM in [[SUMFILES]] and <filename>.NOM in [[NOMINALS]]. Finally, it will append the image name onto [[PICTLIST.TXT]]. | In general, this program ingests images into SPC, building the sumfiles and nominals. |
| Line 8: | Line 8: |
| In other words, make_sumfiles builds the sumfiles and nominals. The user should know that all the vectors in the sumfiles and nominals are in a body fixed frame with the origin at the center of the target body (the origin might be off a little bit, which means [[shift]] will have to be used eventually). Furthermore, for make_sumfiles to work, the ck and spk kernel names in [[make_sumfiles.txt]] must cover the time span of all the images being ingested. | '''make_sumfiles''' takes in the name and some other data about the images from [[make_sumfiles.in]], and position and pointing data from the kernels. The program then |
| Line 10: | Line 10: |
| This program is non-standard. While the goal is to make a single version that does it all, each mission has a different image format. This program frequently has different versions for different missions to get the data in a form usable by SPC. | * converts the image into the <filename>.DAT format in [[IMAGEFILES]] * generates <filename>.SUM in [[SUMFILES]] and <filename>.NOM in [[NOMINALS]] * appends the image name onto [[PICTLIST.TXT]] |
| Line 12: | Line 14: |
| == Input - files == | == User Warnings == . /!\ '''''All the vectors in the sumfiles and nominals are in a body fixed frame with the origin at the center of the target body. The origin might be off a little bit, which means you may have to use [[shift]] eventually.''''' /!\ '''''The ck and spk kernel names in [[make_sumfiles.txt]] must cover the time span of all the images being ingested. Otherwise, make_sumfiles will not work.''''' /!\ '''''This program is non-standard. It frequently requires different versions for different missions to get the data in a form usable by SPC. Although the goal is to make a single version that does it all, each mission has a different image format.''''' /!\ '''''If the image name is already listed in PICTLIST.TXT, make_sumfiles will not make NOMINALS or SUMFILES when you select option "0". (See below)''''' === Input Files === |
| Line 15: | Line 23: |
| * [[make_sumfiles.in]] - list of files from [[process_img]] | * [[make_sumfiles.in]] - list of files from [[process_fits]] |
| Line 17: | Line 25: |
{{{ ~/bin/e.make_sumfiles Use B-Frame? (y/n) n 0. Create SUMFILES & NOMINALS and .. 1. Update old NOMINALS and .. 2. Update old SUMFILES 0 }}} == Output == |
=== Output Files === |
| Line 36: | Line 31: |
| ---------- == Using make_sumfiles == The following sample shows the standard inputs and the list of options for '''make_sumfiles''': |
|
| Line 37: | Line 35: |
| {{{ ~/bin/e.make_sumfiles Use B-Frame? (y/n) n 0. Create SUMFILES & NOMINALS and .. 1. Update old NOMINALS and .. 2. Update old SUMFILES 0 }}} Usually, the B-Frame is not selected. The author has never selected it. |
|
| Line 38: | Line 46: |
| == Example for Mercator Mission == | Enter the appropriate option: |
| Line 40: | Line 48: |
| * Image name (the name of the image in pgm format, and stored in [NEW_IMAGES]) {{{ A1_05 |
* '''0 Create SUMFILES & NOMINALS and ..''' - Completes both operations and ends. * '''1 Update old NOMINALS and ..''' - Completes NOMINALS operation and ends. * '''2 Update old SUMFILES''' - Issues the following prompts: {{{ Update UTC? (y/n) Update image thresholds? (y/n) Update camera parameters? (y/n) Reset geometry? (y/n) Reset sigmas? (y/n) |
| Line 45: | Line 59: |
| * Image time {{{ 410256.22608 (this is GPS time, but sometimes UTC is used) |
* Update UTC - Updates time a picture was taken. * Update image thresholds - Changes image constraints. * Update camera parameters - Changes the camera focal length, K-matrix, etc. * Reset geometry - Resets position and pointing back to nominal. * Reset sigmas - Resets uncertainty back to nominal. (./) Do we need descriptions (default or suggested choices?) for each of these and what happens? == Additional Reference == === Alternative Description === Combines the converted image file with the image number, spacecraft state, spacecraft position & velocity and pointing information along with the associated calculated errors (Sigmas). [from MAKE_SUMFILES.f] {{{ Option 0 creates .SUM and .NOM files for any new images but leaves all others C unchanged. Additionally, option 1 updates all .NOM files. Option 2 dies all of the C above and makes changes in all .SUM files. The possible changes, specified in new C entries in make_sumfiles.txt, are: C C Update UTC? (y/n) C Update image thresholds? (y/n) C Update camera parameters? (y/n) C Reset geometry? (y/n) C Reset sigmas? (y/n) C C The procedure first uses SPKEZ to calculate the spcaecraft - object vector SCOBJ and C the unit vector to the Sun in inertial space at the ephemeris time ET of an image. C It also determines the light time LT from the s/c to the target. It then determines C the transformation matrix from the camera frame (INST) to inertial space (TTVI) at C time ET using the SPICELIB routine PXFORM. Now all relevant quantities are available in C inertial space. In SPC all these quantities are used in the body-fixed frame, so we again C use PXFORM to translate from inertial to body-fixed (TIPM). We do this not at ET but at C ET-LT, since this is when the light forming the image left the target body. |
| Line 49: | Line 94: |
| ---------- ''(Compiled by KD)'' |
|
| Line 50: | Line 97: |
| * Camera Location {{{ 31.69495, -110.62658, 17716.61873 (for Mercator, this is Lat/Lon and altitude of the aircraft) }}} == Alternative Description == Combines the converted image file with the image number, spacecraft state, spacecraft position & velocity and pointing information along with the associated calculated errors (Sigmas). |
[[make_sumfiles-3.0A2]] ---- CategoryThreeOhOne |
make_sumfiles
Category B |
Version 3.0.1 |
Description
In general, this program ingests images into SPC, building the sumfiles and nominals.
make_sumfiles takes in the name and some other data about the images from make_sumfiles.in, and position and pointing data from the kernels. The program then
converts the image into the <filename>.DAT format in IMAGEFILES
generates <filename>.SUM in SUMFILES and <filename>.NOM in NOMINALS
appends the image name onto PICTLIST.TXT
User Warnings
![/!\](/wiki/classic/img/alert.png "/!\")
All the vectors in the sumfiles and nominals are in a body fixed frame with the origin at the center of the target body. The origin might be off a little bit, which means you may have to use shift eventually. The ck and spk kernel names in make_sumfiles.txt must cover the time span of all the images being ingested. Otherwise, make_sumfiles will not work. This program is non-standard. It frequently requires different versions for different missions to get the data in a form usable by SPC. Although the goal is to make a single version that does it all, each mission has a different image format. If the image name is already listed in PICTLIST.TXT, make_sumfiles will not make NOMINALS or SUMFILES when you select option "0". (See below)
Input Files
- Spice kernel file (SPICE)
make_sumfiles.txt - list of SPICE kernels
make_sumfiles.in - list of files from process_fits
Output Files
IFRAME.TXT - picture properties
PICTLIST.TXT - list of pictures
NOMINALS - nominal navigation information and uncertainties
SUMFILES - camera properties and navigation information
Using make_sumfiles
The following sample shows the standard inputs and the list of options for make_sumfiles:
~/bin/e.make_sumfiles Use B-Frame? (y/n) n 0. Create SUMFILES & NOMINALS and .. 1. Update old NOMINALS and .. 2. Update old SUMFILES 0
Usually, the B-Frame is not selected. The author has never selected it.
Enter the appropriate option:
0 Create SUMFILES & NOMINALS and .. - Completes both operations and ends.
1 Update old NOMINALS and .. - Completes NOMINALS operation and ends.
2 Update old SUMFILES - Issues the following prompts:
Update UTC? (y/n) Update image thresholds? (y/n) Update camera parameters? (y/n) Reset geometry? (y/n) Reset sigmas? (y/n)
- Update UTC - Updates time a picture was taken.
- Update image thresholds - Changes image constraints.
- Update camera parameters - Changes the camera focal length, K-matrix, etc.
- Reset geometry - Resets position and pointing back to nominal.
- Reset sigmas - Resets uncertainty back to nominal.
Do we need descriptions (default or suggested choices?) for each of these and what happens?
Additional Reference
Alternative Description
Combines the converted image file with the image number, spacecraft state, spacecraft position & velocity and pointing information along with the associated calculated errors (Sigmas).
[from MAKE_SUMFILES.f]
Option 0 creates .SUM and .NOM files for any new images but leaves all others C unchanged. Additionally, option 1 updates all .NOM files. Option 2 dies all of the C above and makes changes in all .SUM files. The possible changes, specified in new C entries in make_sumfiles.txt, are: C C Update UTC? (y/n) C Update image thresholds? (y/n) C Update camera parameters? (y/n) C Reset geometry? (y/n) C Reset sigmas? (y/n) C C The procedure first uses SPKEZ to calculate the spcaecraft - object vector SCOBJ and C the unit vector to the Sun in inertial space at the ephemeris time ET of an image. C It also determines the light time LT from the s/c to the target. It then determines C the transformation matrix from the camera frame (INST) to inertial space (TTVI) at C time ET using the SPICELIB routine PXFORM. Now all relevant quantities are available in C inertial space. In SPC all these quantities are used in the body-fixed frame, so we again C use PXFORM to translate from inertial to body-fixed (TIPM). We do this not at ET but at C ET-LT, since this is when the light forming the image left the target body.
(Compiled by KD)