Size: 1792
Comment:
|
Size: 3822
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
== make_sumfiles.txt == | = make_sumfiles.txt = |
Line 3: | Line 3: |
This is a configure file that contains basic camera distortion data and a list of available SPICE kernels. As far as I can tell, it is created by hand. | Compiled by KD == Description == This is a configure file that contains basic camera distortion data and a list of available SPICE kernels. As far the extravagant Eric Palmer can tell, make_sumfiles.txt is created by hand. The file, make_sumfiles.txt, is used by [[make_sumfiles]] as a configuration file when generating [[SUMFILES]] and [[NOMINALS]]. == Camera Data Definitions == * NCAM is the number of cameras that the file maintains. Then the cameras are listed in order. * Camera Name * Pixels (sample and rows) * Focal length, center pixel (x/y) * K Matrix -- distortion matrix * Min and max expected DN for this data type * sigV0 - The uncertainty of the spacecraft position [km] * sigPt - The uncertainty of the camera pointing [Rad] == Kernel list Needed == When in doubt just list off all the available kernels, but here is a list of kernels that are known to make [[make_sumfiles]] work: * SPK kernels (.bsp) for spacecraft and target object - ephemeris * CK kernels (.bc) - orientation/attitude of spacecraft and other structures (like camera) * SCLK kernels (.tsc) - spacecraft clock coefficients * IK kernels (.ti) - instrument geometry for camera taking pictures * LSK kernels (.tls) - leap seconds * FK kernels (.tf) - reference frame specifications * PCK kernels (.tpc) - text form of planetary/asteroidal constants The user should know that the SPICE kernels list starts at a row with just "KERNELS" and just an "#" in the next row. The SPICE kernels list ends with at a row with just "END_KRNLS". Furthermore, three rows giving the names of the ID of the target body, body fixed frame in the kernels, and aberration correction desired should be put before the "KERNELS" row as shown in the example. Also, if the SPICE kernels are not in the directory the user is working in a row giving the path to the kernels can be added before the "KERNELS" row as shown. == Example of make_sumfiles.txt == |
Line 26: | Line 57: |
'../ORex/DATA/' PREFIX | |
Line 33: | Line 65: |
... END_KRNLS |
|
Line 35: | Line 69: |
When processing ["make_sumfiles"] . if you get the "NOFRAMECONNECT" error (where it says, "At epoch...", then you likely need a ck KERNEL (<filename>.bc). |
When processing [[make_sumfiles]] . If you get the "NOFRAMECONNECT" error (where it says, "At epoch...", then you likely need a CK Kernel (<filename>.bc). |
Line 38: | Line 72: |
=== Same make_sumfiles.txt Example but with more Comments === {{attachment:make_sumfiles.txt.jpg||width=700}} |
make_sumfiles.txt
Compiled by KD
Description
This is a configure file that contains basic camera distortion data and a list of available SPICE kernels. As far the extravagant Eric Palmer can tell, make_sumfiles.txt is created by hand. The file, make_sumfiles.txt, is used by make_sumfiles as a configuration file when generating SUMFILES and NOMINALS.
Camera Data Definitions
- NCAM is the number of cameras that the file maintains. Then the cameras are listed in order.
- Camera Name
- Pixels (sample and rows)
- Focal length, center pixel (x/y)
- K Matrix -- distortion matrix
- Min and max expected DN for this data type
- sigV0 - The uncertainty of the spacecraft position [km]
- sigPt - The uncertainty of the camera pointing [Rad]
Kernel list Needed
When in doubt just list off all the available kernels, but here is a list of kernels that are known to make make_sumfiles work:
- SPK kernels (.bsp) for spacecraft and target object - ephemeris
- CK kernels (.bc) - orientation/attitude of spacecraft and other structures (like camera)
- SCLK kernels (.tsc) - spacecraft clock coefficients
- IK kernels (.ti) - instrument geometry for camera taking pictures
- LSK kernels (.tls) - leap seconds
- FK kernels (.tf) - reference frame specifications
- PCK kernels (.tpc) - text form of planetary/asteroidal constants
The user should know that the SPICE kernels list starts at a row with just "KERNELS" and just an "#" in the next row. The SPICE kernels list ends with at a row with just "END_KRNLS". Furthermore, three rows giving the names of the ID of the target body, body fixed frame in the kernels, and aberration correction desired should be put before the "KERNELS" row as shown in the example.
Also, if the SPICE kernels are not in the directory the user is working in a row giving the path to the kernels can be added before the "KERNELS" row as shown.
Example of make_sumfiles.txt
2 NCAM 'DAWN_FC1' 1024 1024 NPXA, NLNA 150.0664382826180 512.5 512.5 MMFLA, PX0A, LN0A 71.4286, 0, 0, 0.003374864380978, -71.441109720651326, 0 KMATA 0, 0, 0, 0 DA 400, 16383 T1,T2 'DAWN_FC2' 1024 1024 NPXB, NLNB 150.0732773452877 512.5 512.5 MMFLB, PX0B, LN0B 71.4286, 0, 0, 0.003862501939093, -71.44341298478835, 0 KMATB 0, 0, 0, 0 DB 400, 16383 T1,T2 1 NSC -203 DAWN 2.d-1 2.d-1 2.d-1 sigV0 1.d-4 1.d-4 1.d-4 sigPT 2000004 VESTA 'VESTA_FIXED' BFRAME 'LT+S' ABCORR '../ORex/DATA/' PREFIX KERNELS # naif0009.tls dawn_fc_v01.ti dawn_v05.tf dawn_ceres_v00.tf dawn_vesta_v00.tf ... END_KRNLS
When processing make_sumfiles
If you get the "NOFRAMECONNECT" error (where it says, "At epoch...", then you likely need a CK Kernel (<filename>.bc).
If you get the "SPKINSUFFDATA" error (where it says, "Insufficient...", the you likely need a SPK Kernel (<filename>.bsp).
Same make_sumfiles.txt Example but with more Comments