|
Size: 2222
Comment:
|
Size: 2613
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
||Category B||Version 3.0.1|| |
|
| Line 7: | Line 9: |
| '''make_sumfiles.in''' contains these 5 columns: | '''make_sumfiles.in''' contains these 6 columns: |
| Line 12: | Line 14: |
| * bin (./) clarify: (not sure what this means) | * bin |
| Line 14: | Line 16: |
(./) says 5 columns but lists 6. The last seems to be optional (only used on OR???). How to show that here??? |
|
| Line 20: | Line 20: |
| The following sample '''make_sumfiles.inn''' is from OSIRIS_Rex. | The following sample '''make_sumfiles.in''' is from OSIRIS_REx. |
| Line 22: | Line 22: |
| /!\ This sample is in the format necessary for the OSIRIS-ORex mission. UTC time may not be needed for other missions and the spacecraft time might be in another format. | /!\ This sample is in the format necessary for the OSIRIS-OREx mission. UTC time may not be needed for other missions and the spacecraft time might be in another format. |
| Line 24: | Line 24: |
| (!) Spacecraft time is needed to use CK kernels while epoch time is needed for spk kernels. Spacecraft, UTC, and epoch time can be transformed into one another pretty easily using spice, which SPC uses. It is unclear why two types of time are included in the OSIRIS-REx '''make_sumfiles.in'''. However, the legendary Bob Gaskell probably knows why. | (!) Spacecraft time is needed to use CK kernels while epoch time is needed for spk kernels. Spacecraft, UTC, and epoch time can be transformed into one another pretty easily using spice, which SPC uses. |
| Line 27: | Line 27: |
| P595650043F2 1/0595649979.53969 3 1 1 2018-11-16T14:19:35.816_ P595650073F2 1/0595650009.53969 3 1 1 2018-11-16T14:20:05.816_ P595650103F2 1/0595650039.53969 3 1 1 2018-11-16T14:20:35.816_ P595650136F2 1/0595650072.53969 3 1 1 2018-11-16T14:21:08.816_ |
P596924821J3 3/0596924726.30615 3 1 1 -25.50 270 20181201T082552S75100Z_pol_L0_V002.fits P601296494J3 1/0601296429.38732 3 1 1 -25.50 270 2019-01-20T22-47-05.541_PCAM_L0b_V004.fits |
| Line 34: | Line 32: |
| Here is another sample '''make_sumfiles.in''' file from another mission: | Column Definitions || Image Name || ET || camera || NS || Binning || Camera Temperature || Filter/Focal || Source filename || Filter Number -- MapCam has filters based upon its position -- in degrees || Position || Filter Number|| || 0 || 0 || || 720 || 0 || || 600 || 0 || || 480 || 0 || || 360 || 0 || || 240 || 0 || || 120 || 0 || Focal Position -- PolyCam NQ=FLT * The motor position, 0 to 17,400 |
| Line 36: | Line 48: |
| FC21A0014662 377642737:125 2 1 1 FC21A0014663 377642812:125 2 1 1 FC21A0014664 377642887:126 2 1 1 FC21A0016638 379008279:125 2 1 1 ... |
where: d is the distance the camera is focused at in m For practical reasons the infinity setting we use in the lab is actually ~4.3 km (PolyCam step 17,400) not actual infinity. At that setting we measured the effective focal length 627.8mm. Based on the formula above it means our CBE for finf is 628.9mm so until we get a better number from post launch calibration images we should use f(d) = 628.9 - 2684 * d ^ -0.9376 |
| Line 42: | Line 62: |
| Line 47: | Line 72: |
| '''Figure 00: Sample make_sumfiles.in File with Headers''' | |
| Line 51: | Line 77: |
| CategoryFiles | [[make_sumfiles.in-3.0A2]] CategoryFiles CategoryInputFiles |
make_sumfiles.in
Category B |
Version 3.0.1 |
Description
This text file is a list of the image files needed by make_sumfiles to create SUMFILES and NOMINALS. It is created by process_fits an becomes an input for make_sumfiles.
make_sumfiles.in contains these 6 columns:
image name loaded into process_fits
- spacecraft time of each image
- camera number that took the image
- spacecraft number for mission
- bin
- UTC time of each image
The vectors in the sumfiles and nominals are calculated directly from the kernels in make_sumfiles.txt by using the time for each image obtained from make_sumfiles.in.
The following sample make_sumfiles.in is from OSIRIS_REx.
![/!\](/wiki/classic/img/alert.png "/!\")
This sample is in the format necessary for the OSIRIS-OREx mission. UTC time may not be needed for other missions and the spacecraft time might be in another format. 
Spacecraft time is needed to use CK kernels while epoch time is needed for spk kernels. Spacecraft, UTC, and epoch time can be transformed into one another pretty easily using spice, which SPC uses.
P596924821J3 3/0596924726.30615 3 1 1 -25.50 270 20181201T082552S75100Z_pol_L0_V002.fits P601296494J3 1/0601296429.38732 3 1 1 -25.50 270 2019-01-20T22-47-05.541_PCAM_L0b_V004.fits ...
Column Definitions
Image Name |
ET |
camera |
NS |
Binning |
Camera Temperature |
Filter/Focal |
Source filename |
Filter Number -- MapCam has filters based upon its position -- in degrees
Position |
Filter Number |
0 |
0 |
720 |
0 |
600 |
0 |
480 |
0 |
360 |
0 |
240 |
0 |
120 |
0 |
Focal Position -- PolyCam NQ=FLT
- The motor position, 0 to 17,400
where: d is the distance the camera is focused at in m For practical reasons the infinity setting we use in the lab is actually ~4.3 km (PolyCam step 17,400) not actual infinity. At that setting we measured the effective focal length 627.8mm. Based on the formula above it means our CBE for finf is 628.9mm so until we get a better number from post launch calibration images we should use f(d) = 628.9 - 2684 * d ^ -0.9376
The following sample includes column headings for easy reference:
Figure 00: Sample make_sumfiles.in File with Headers
(Compiled by KD)