|
Size: 1979
Comment:
|
Size: 2739
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| === Description === In general, make_sumfiles ingests images into SPC. It takes in, as a standard input, the name and camera position of the images. 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]. |
== Description == In general, this program ingests images into SPC, building the sumfiles and nominals. |
| Line 6: | Line 6: |
| Builds the sumfile and nominals | '''make_sumfiles''' takes in the name and camera position of the images from [[make_sumfiles.in]]. 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]] |
| Line 8: | Line 11: |
| B-Frame let's you set the NOM and SUM to the body fixed frame. | == User Warnings == |
| Line 10: | Line 13: |
| /!\ '''''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.''''' | |
| Line 11: | Line 15: |
| You must update the ck and spk entries in [[make_sumfiles.txt]]. You must have entries that cover the time of all of your images. | /!\ '''''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.''''' |
| Line 13: | Line 17: |
| /!\ '''''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.''''' | |
| Line 14: | Line 19: |
| 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. === Input - files === |
=== Input Files === |
| Line 19: | Line 22: |
| * [[make_sumfiles.in]] - list of files from [[process_img]] | * [[make_sumfiles.in]] - list of files from [[process_fits]] |
| Line 21: | Line 24: |
| === 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''': |
|
| Line 23: | Line 37: |
| ~/bin/e.make_sumfiles | ~/bin/e.make_sumfiles |
| Line 28: | Line 42: |
| 2. Update old SUMFILES | 2. Update old SUMFILES |
| Line 30: | Line 44: |
| Line 33: | Line 46: |
| == Output == | (./) Do we need something about what "Use B-Frame" means and why to choose 'n'? |
| Line 35: | Line 48: |
| * [[PICTLIST.TXT]] * [[NOMINALS]] - nominal navigation information and uncertainties * [[SUMFILES]] - camera properties and navigation information |
Enter the appropriate option: |
| Line 39: | Line 50: |
| * '''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: |
|
| Line 40: | Line 54: |
== Example for Mercator == * Image name (the name of the image in pgm format, and stored in [NEW_IMAGES]) {{{ A1_05 |
{{{ Update UTC? (y/n) Update image thresholds? (y/n) Update camera parameters? (y/n) Reset geometry? (y/n) Reset sigmas? (y/n) |
| Line 48: | Line 62: |
| * Image time {{{ 410256.22608 (this is GPS time, but sometimes UTC is used) }}} |
(./) Do we need descriptions (default or suggested choices?) for each of these and what happens? |
| Line 53: | Line 64: |
| * Camera Location {{{ 31.69495, -110.62658, 17716.61873 (for Mercator, this is Lat/Lon and altitude of the aircraft) }}} |
== Additional Reference == |
| Line 59: | Line 67: |
| * Combines the converted image file with the image number, spacecraft state, spacecraft position & velocity and pointing information along with the associated calculated errors (Sigmas) | Combines the converted image file with the image number, spacecraft state, spacecraft position & velocity and pointing information along with the associated calculated errors (Sigmas). ---------- ''(Compiled by KD)'' CategoryPrograms |
make_sumfiles
Description
In general, this program ingests images into SPC, building the sumfiles and nominals.
make_sumfiles takes in the name and camera position of the images from make_sumfiles.in. 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.
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
Do we need something about what "Use B-Frame" means and why to choose 'n'?
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)
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).
(Compiled by KD)