BIGMAP.IN
Description
This user-created file contains the list of landmarks you want to use when creating a bigmap.
If BIGMAP.IN exists when the bigmap command is run, the only landmarks that will be used in the construction of the bigmap are taken from this list. This is useful when you want to use only specific landmarks, such as only those of a certain resolution.
![/!\](/wiki/classic/img/alert.png "/!\")
BIGMAP.IN should be treated as a temporary file and either renamed or deleted after use.
Here is a sample of a BIGMAP.IN file:
EE0001 EE0002 EE0003 EE0004 EE0005 EE0006 EE0007 EE0008 EE0009 EE0010 EE0011 EE0012 EE0013 EE0014 EE0015 EE0016 END
(Compiled by TC)
DYNAMICS.TXT
Description
This input file allows you to specify different uncertainty values in different coordinate frames for different segments of a mission. The program dynamics reads this file and assigned these values for images contained therein.
The file looks just like the PICTLIST.TXT file in that there is a space in the first column before the picture name.
Here is a sample of 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
There were a number of parameter changes as the mission progressed from Approach to Survey to HAMO to LAMO to HAMO2 to Departure, with transitions between phases requiring parameters of their own.
(Compiled by TC)
IFRAME.TXT
Description
This text file contains the nominal spacecraft to object center vector and camera orientation all in inertial space (J2000) for each picture. IFRAME.TXT is created by the routine make_sumfiles.
In IFRAME.TXT, the SCOBJ vector is in meters. RA, DEC, and TWIST are in degrees. SRA and SDEC are the error in RA and DEC, respectively, in milli-arcseconds.
IFRAME.TXT used to be created by IFRAME.f with the understanding that, if it was needed, it would be run right after make_sumfiles. However, that was confusing and fraught with peril.
IFRAME.TXT is now used by OMEGA. It lets you get an approximate solution for the transformation from inertial to body-fixed and, if desired, to update the sumfile accordingly. Of course, since there are uncertainties in the nominal values, this isn't quite right, and you must run REGISTER to align with the current shape model.
Here is a sample IFRAME.TXT file:
PICNM UTC SCOBJx SCOBJy SCOBJz RA DEC TWIST SRA SDEC P595033964F2 2018 NOV 09 11:11:36.008 0.1393877134D+03 -0.2052581418D+02 -0.9569192088D+01 -8.37947 -3.88812 88.65648 176.39833 2.27588 P595034390F2 2018 NOV 09 11:18:42.324 0.1393248422D+03 -0.2052504806D+02 -0.9564763229D+01 -8.37947 -3.88812 88.65648 176.40259 2.27349 P595034816F2 2018 NOV 09 11:25:48.640 0.1392619628D+03 -0.2052427823D+02 -0.9560332270D+01 -8.37947 -3.88812 88.65648 176.40685 2.27109 P595035242F2 2018 NOV 09 11:32:54.955 0.1391990760D+03 -0.2052351109D+02 -0.9555902818D+01 -8.38640 -3.88409 88.66071 176.41111 2.26869 ...
(Compiled by KD)
INIT_LITHOS.TXT
Category B |
Version 3.0.3 |
Description
This text file sets limits, definitions, and logicals for SPC.
Here is a sample to show the keywords used in INIT_LITHOS.TXT.
Operational settings for INIT_LITHOS.TXT. There are other options, but they are not needed or supported for the OSIRIS-REx mission. # as the first character denotes a comment.
USR= '0' USRMX=12 BODY='RQ36' IDCODE=2101955 #BFRAME='RQ36_FIXED' BFRAME='IAU_BENNU' PCK='DATA/naif0011.tls' PCK='DATA/bennu_v10.tpc' UNIT='METER' ASIG= 0.05 SSIG= 0.15 CHI0= 1.0 BLIM= 0.5 MXSLP=0.6 BLOOM=0.2 SEED= 1.3827453 #REFLECT= 'VESTA' NEWLIM=.TRUE. find new limbs in LITHOSP SOFTEN=1 MAPONLY=.FALSE. #GEOPIC='pict1.txt' RENAME=.FALSE. REGFLG=.FALSE. REG='J0' KB=1 RPLUSE=.TRUE. RECVR=.FALSE. #RECVR=.TRUE. ALPAD=.TRUE. NEWLIM=.TRUE. DISTORT= 'M###########' 'OWEN' 6 0.00000D+00 0.00000D+00 0.0000000-06 0.00000D+00 0.00000D+00 0.000000D-05 0.0000000D-07 DISTORT= 'P###########' 'OWEN' 6 0.00000D+00 0.00000D+00 0.000000D-06 0.00000D+00 0.00000D+00 0.000000D-07 0.0000000D-06 #SHAPERF= 'SHAPEFILES/SHAPE00.TXT' #SIGMARF= .05 LMKWTS= 1, 1, 1, 0 WB, WO, WL, WR PICWTS= 1, 1, 0, 1, 0 WB, WL, WC, WS, WT LPCORLM= 0.2 ALCORLM= 0.3 GDCORLM= 0.3 HTCORLM= 0.2 CORRFLG= 3 0:LAP, 1:ALB, 2:GRD, 3:L+A RESLM= 4 PIXEL<RESLM*SCALE [SCALE>PIXEL/RESLM] PICLM=2 NUMLM=200 SIZLM= 1.5 ^ LOWERS PIXEL/SCALE END
Explanation
USR |
Not used |
USRMX |
When running any batch script program (make_scriptP, make_scriptAP), this value defines the number of processors that will be used |
BODY |
The is the name of the object |
IDCODE |
The is the number that NAIF uses to denote the object. Bennu's official asteroid designator is 2101955 |
BFRAME |
Contains the variable used to define the body fixed coordinate frame. This is defined by NAIF and used in the kernels |
PCK |
These define the planetary constants for a variety of objects. naif0011.tls is for the whole solar system. bennu_v10.tpc is the current version for Bennu. Many programs will read these line to do SPICE function calls. |
UNIT |
Sets the units that the tables report out units. Options are KILOMETER and METER |
ASIG |
The weighting that is placed upon the albedo solution (a priori albedo sigma). Typical is 0.05. EDIT JRW 09 May 2017: This value determines how much to change albedo during 0-0-40. Setting it small (1e-10) means albedo won't change. |
SSIG |
The weighting that is placed upon the asteroid's topographic solution. (a priori slope sigma). Typical is 0.15 |
CHI0 |
Background limit. Typical is 1.0. |
BLIM |
Minimum overlap in LITHOS b option. Typical is 0.5. |
MXSLP |
Sets the limit for slope. Previous use at 0.6 ensures no vertical slopes. Suggest removing or 0 for Bennu and boulders. |
BLOOM |
Enables limb detection when blooming is present. Typical is 0.02. |
SEED |
The seed value used for the random function call. |
REFLECT |
What photometric model to use. If not defined, SPC uses McEwin . |
SOFTEN |
This decreases the weight of the change when a solution is found. Typical is 1.0. |
MAPONLY |
If .TRUE., we ignore mapless landmarks in GEOMETRY. Standard is FALSE |
REGFLG |
If .TRUE., it uses an alternate LANDMARK naming convention. |
REG |
If REGFLG=.TRUE., it uses these two characters as the lead character for LANDMARKS. |
KB |
Beginning number in sequence for LANDMARKS. Typical is 1 |
RPLUSE |
Use PICTLISTX or PICLTLISTR for netpictures. Typical is .TRUE. |
RECVR |
If .TRUE., prevents high res maplets from effecting low-resolution topography. Typical is .FALSE. |
ALPAD |
Perform extra albedo solution after each iteration. Typical .TRUE. |
NEWLIM |
Tells lithosP to run the detect new limb routing when running an iteration. |
DISTORT |
Distortion matrix. It has four parameters. The first is an image name template where # is a wildcard. If the image name fits the template, then it will apply this distortion matrix. The next parameter is the distortion type. The third parameter is how many terms the distortion matrix has. The fourth parameter is the distortion matrix. (Note: The zeroth distortion matrix element is a fractional focal length change for the particular filter.) |
SHAPEREF |
If you want to constrain the model using a starting shape model (GEOMETRY option 1), that model is defined here. Typical is "SHAP00.TXT. |
SIGMARF |
Simga is km for above constraint. Typical is 0.5. |
LMKWTS |
Weights for generation for the LANDMARK position (GEOMETRY option 1). Typical is 1, 1, 1, 0 (see details below) |
PICWTS |
Weights for generation for the S/C position and pointing (GEOMETRY option 2). Typical is 1, 1, 1, 1, 0 |
LPCORLM |
Correlation limit for laplacian cor. Typical is 0.2. |
ALCORLM |
Correlation limit for albedo cor. Typical is 0.3. |
GDCORLM |
Correlation limit for gradient cor. Typical is 0.3. |
HTCORLM |
Correlation limit for height cor. Typical is 0.2. |
CORRFLG |
Overlap correlation option. 0:LAP, 1:ALB, 2:GRD, 3:L+A. Typical is 3. |
RESLM |
PIXEL<RESLM*SCALE [SCALE>PIXEL/RESLM]. Limits image or maplet resolution in search. Typical is 4. |
PICLM |
Minimum number of images in a LANDMARK. If it doesn't this many, the LANDMARK is deleted. Typical is 6. |
NUMLM |
Number of images before RESLM kits in. If you have more that this number of images, don't add in resolutions ratios beyond RESLM. Typical is 200. |
SIZLM |
Minimum ratio of map to image sizes. MAPSIZE < SIZLM * PICSIZE. ^ LOWERS PIXEL/SCALE. Typical is 1.5. |
BLEMISHES='FC2#########' |
Reference to a template contained in BLEMISHES/ for masking bad pixels which are common to all FC2 images (example taken from DAWN). The template name is 12 characters, with the characters common to all affected images in the correct positions and '#' everywhere else. There may be multiple BLEMISH entries, each referring to BLEMISH template files. |
PRNLM=100 |
Prune limit used by residuals to alert you if the number of pictures containing a landmark exceeds the limit. Landmarks exceeding the limit are listed in the output file PRUNE.TXT. |
|| FTM || Frame transfer time. Allows you to change the default charge transfer time for PROCESS_FITS. If it is not there, it uses the default value in the source code (1.044).
Weighting values for landmark and picture calculations.
Within INIT_LITHOS.TXT, we have weighting that goes into the solution. The actual weight that is included is the sqrt of the value provided. Thus, if you want to double the weight, you would use 4.
LMKWTS -- Landmark Weights
These weights are used to influence the position of the central vector -- the middle of the landmark.
- WB - Body. Use the position from the pixel/line location based on the images.
- WO - Overlap. Condition the solution with the overlapping maplets
- WL - Limbs. Use images that contain the current landmark on its limb to condition the solution
- WR - Reference. If there is a reference object (SHAPEREF='SHAPEFILES/SHAPE00.TXT'), it will ensure the solution does not deviation too far from that baseline shape. This may be used at the start, but it is unlikely to be needed as the model gets more mature.
PICWTS -- Picture Weights
These weights are what is used when solving for the spacecraft position and camera pointing.
- WB - Body. Body is where it uses the position of all the landmarks and minimizes the spacecraft pointing/position.
- WL - Limbs. This uses landmarks that have detected that this image is on the limb to constrain its position.
WC - Camera. The uncertainty value for SIGMA_PTG in SUMFILES will constrain how far away the camera pointing solution can be from the value stored in NOMINALS
WS - SCOBJ. The uncertainty value for SIGMA-VSO in SUMFILES will constrain how far away the spacecraft object (SCOBJ) solution can be from the value stored in NOMINALS
WT - Trajectory. When dynamics is being used (the preceding two and trailing two images are stored in the NOMINALS file), this will constrain how far the spacecraft object can deviate from the nearby images.
(Compiled by KD)
LIMBLIST1.TXT
This list is a list of images and will be created by the user, and will be used by make_list. See make_list for further details.
Example of LIMBLIST1.TXT:
P596675130F2 P596675146F2 P596675162F2 P596675177F2 END
(Compiled by ??)
LMRKLIST.TXT
Category ? |
Version 3.0 |
Description
This input file includes a list of landmarks that lithos will use.
LMRKLIST.TXT can be created by hand by listing the LMKFILES directory.
If it's present, LMRKLISTO.TXT is used to calculate overlaps, rather than LMRKLIST.TXT.
Here is a sample LMRKLIST.TXT file:
EE0001 EE0002 EE0003 EE0004 EE0005 EE0006 EE0007 EE0008 EE0009 EE0010 EE0011 EE0012 EE0013 EE0014 EE0015 END
To build a LMRKLIST.TXT file, enter the following at the command line:
cd LMKFILES /bin/ls > ../LMRKLIST.TXT cd .. echo END >> LMRKLIST.TXT
Another important input file which should be read instead of LMRKLIST.TXT is LMRKLISTX.TXT. In the limit of a very large number of landmarks > 20 K, reading the LMRKLISTX.TXT file when you load a landmark into lithos will result in substantial time savings compared to reading the LMRKLIST.TXT file.
(Compiled by DL)
LMRKLIST1.TXT
Description
This text file contains a list of newly created landmarks.
LMRKLIST1.TXT can be deleted at any time with no repercussions. However, it is useful for various things.
For example, if you delete LMRKLIST1.TXT right before tiling at 35cm, then after you have finished tiling you will have a list of all the landmarks at 35cm. You can then save this list in a different file and store it for future use.
Also, the landmarks in LMRKLIST1.TXT are read by EXPORT, and these are the only landmarks that get exported. If a program tries to use LMRKLIST1.TXT but it does not exist, that program creates an LMRKLIST1.TXT.
Another important input file which should be read instead of LMRKLIST.TXT is LMRKLISTX.TXT. In the limit of a very large number of landmarks > 20 K, reading the LMRKLISTX.TXT file when you load a landmark into lithos will result in substantial time savings compared to reading the LMRKLIST.TXT file.
(Compiled by JRW)
LMRKLISTO.TXT
Description
This text file contains a list of all maplets that could possibly overlap a new map created in the same location used to make a bigmap.
If it's present, programs use LMRKLISTO.TXT to calculate overlaps, rather than using LMRKLIST.TXT. This enables lithos and lithosP to run faster because they only search for overlaps among a limited set of landmarks.
When bigmap runs, it keeps track of all the maplets that went into its construction and puts this list into USED_MAPS.TXT. If you want to use this reduced set of landmarks, you can get it from USED_MAPS.TXT after you run bigmap. Once it is complete, LMRKLISTO.TXT contains all the maplets that could possibly overlap a new map created in the same location used to make the bigmap. Moreover, as LITHOS creates new maplets, it automatically adds them to LMRKLISTO.TXT.
cp USED_MAPS.TXT LMRKLISTO.TXT
(Compiled by JRW and EEP)
LMRKLISTR.TXT
Description
This input file is a user created file that is a restricted list (hence the "R" in LMRKLISTR.TXT as compared to LMRKLIST.TXT.) Typically SPC uses all landmarks that have been created, but at times you may want to reduce the number of landmarks that are used, which is why you would create a restricted list of landmarks. This must be used with caution, because most programs will check for the LMRKLISTR.TXT and use it if it exists.
- If you don't remove the LMRKLISTR.TXT file once you're done with it, you'll be working with a partial dataset.
This file is used by various programs, if it exists. One program that uses LMRKLISTR.TXT is regres.
If LMRKLISTR.TXT does not exist, then the program uses LMRKLIST1.TXT or LMRKLIST.TXT.
(Compiled by JRW)
LMRKLISTX.TXT
Description
This input file is output by make_lmrklistX. LMRKLISTX.TXT summarizes the following landmark information (in column order):
- lmrk name
- Q size
- number of images containing the lmrk
- VLM - lmrk position vector from the center of the body to the center of the lmrk
- scale (km)
lithosP uses LMRKLISTX.TXT to quickly determine what landmark files need to be used for the overlap computation.
Here is a sample LMRKLISTX.TXT file:
EE0001 49 355 -0.789971D-02 0.260998D+00 -0.115266D-01 0.350000D-03 EE0002 49 360 -0.203250D-01 0.262210D+00 -0.116002D-01 0.350000D-03 EE0003 49 320 -0.328776D-01 0.260667D+00 -0.112363D-01 0.350000D-03 EE0004 49 298 -0.454681D-01 0.259987D+00 -0.111565D-01 0.350000D-03 EE0005 49 356 -0.782921D-02 0.261745D+00 -0.242790D-01 0.350000D-03 EE0006 49 359 -0.203874D-01 0.261724D+00 -0.242330D-01 0.350000D-03 EE0007 49 360 -0.328300D-01 0.262109D+00 -0.243155D-01 0.350000D-03 EE0008 49 360 -0.453950D-01 0.261565D+00 -0.241885D-01 0.350000D-03 EE0009 49 293 -0.787332D-02 0.258487D+00 -0.364896D-01 0.350000D-03 EE0010 49 358 -0.202152D-01 0.260056D+00 -0.365461D-01 0.350000D-03 EE0011 49 357 -0.328579D-01 0.261480D+00 -0.369930D-01 0.350000D-03 EE0012 49 360 -0.453167D-01 0.261334D+00 -0.369408D-01 0.350000D-03 EE0013 49 150 -0.100607D-01 0.261914D+00 -0.139179D-01 0.180000D-03 EE0014 49 165 -0.170069D-01 0.262132D+00 -0.138891D-01 0.180000D-03 EE0015 49 150 -0.239728D-01 0.262338D+00 -0.138081D-01 0.180000D-03 END
(Compiled by DL)
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.
- This sample is in the format necessary for the OSIRIS-OREx mission.
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
PICNM |
CLK |
NC |
NS |
SCL |
TC |
NQ |
FITSNM |
SPC-OREx Naming |
UTC or ET |
Camera 1-5 |
Spacecraft Number |
Binning (none) |
Temperature in C |
Filter/Focal |
Source filename |
Filter Number -- MapCam has filters based upon its position -- in degrees
Position |
Filter Number |
0 |
0 |
720 |
0 |
630 |
1 |
540 |
2 |
450 |
3 |
360 |
4 |
270 |
5 |
180 |
6 |
90 |
7 |
30 |
7 |
Filter Number --SamCam has filters based upon its position -- in degrees
Position |
Filter Number |
0 |
0 |
720 |
0 |
600 |
1 |
480 |
2 |
360 |
3 |
240 |
4 |
120 |
5 |
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
(Compiled by EP)
old - make_sumfiles.in-3.0A2
make_sumfiles.txt
Category ? |
Version 3.0 |
Description
This configuration file contains basic camera distortion data and a list of available SPICE kernels. It is used by make_sumfiles as a configuration file when generating SUMFILES and NOMINALS. At this time, make_sumfiles.txt is created by hand.
Creating make_sumfiles.txt
Here is a sample make_sumfiles.txt file. Annotations on the right indicate what the data elements are.
4 NCAM 'ORX_OCAMS_MAPCAM' 1024 1024 NPXB, NLNB 125.0 512.5 512.5 MMFLB, PX0B, LN0B 117.647, 0, 0, 0, 117.647, 0 KMATB -1, -2, 3 PROJECT CAMERA AXES 5, 16383 T1,T2 'ORX_OCAMS_SAMCAM' 1024 1024 NPXC, NLNC 24.0 512.5 512.5 MMFLC, PX0C, LN0C 117.647, 0, 0, 0, 117.647, 0 KMATC 1, 2, 3 PROJECT CAMERA AXES 5, 16383 T1,T2 'ORX_OCAMS_POLYCAM' 1024 1024 NPXA, NLNA 611.0 512.5 512.5 MMFLA, PX0A, LN0A 117.647, 0, 0, 0, 117.647, 0 KMATA -1, -2, 3 PROJECT CAMERA AXES 5, 16383 T1,T2 'ORX_NAVCAM' 2592 1944 NPXC, NLNC 7.6 1296.5 972.5 MMFLC, PX0C, LN0C 454.54, 0, 0, 0, 454.54, 0 KMATC 1, 2, 3 PROJECT CAMERA AXES 5, 4096 T1,T2 1 NSC -64 ORX 1.d0 1.d0 1.d0 sigV0 1.d-3 1.d-3 1.d-3 sigPT 2101955 BENNU 'IAU_BENNU' BFRAME 'NONE' ABCORR '../ORex/DATA/' PREFIX KERNELS sb-101955-76.bsp bennu_v10.tpc de421.bsp naif0011.tls orex_ocams_v02.ti orx_aux_v01.ti orx_v03.tf pck00010.tpc ApproachPrelim_Perturbed.bsp DetailedSurvey_Perturbed.bsp OrbitalB_Perturbed.bsp ORX_SCLKSCET.00000.example.tsc F3A_AllObs_20181109T000000_20181118T000000_Perturbed.bc F3A_BD_AllObs_20190113T000000_20190122T120000_p.bc F3A_ES_Obs1_20190127T094200_20190127T161200_p.bc F3A_ES_Obs2_20190203T094300_20190203T161300_p.bc F3A_ES_Obs3_20190210T100500_20190210T163500_p.bc ... END_KRNLS
Description of codes
NCAM |
Number of cameras in the file |
NPXV, NLNB or NPXC, NLNC, or NPXA, NLNA |
Number of pixels and lines for the camera image |
MMFLB, PX0B, LN0B |
focal length and center pixel/line of the camera |
PROJECT CAMERA AXIS |
The axis of the camera mounted onto the spacecraft. This is the same thing that is described in all the frame kernels |
T1, T2 |
The min and maximum value of "accepted" values for the image's DN. Below and above this threshold, it denotes no data |
ORX |
NAIF base code for the spacecraft |
sigV0 |
The default value for the spacecraft object uncertainty, in km. Can be overwritten by DYNAMICS |
sigPT |
The default value for the camera pointing uncertainty, in Rad. Can be overwritten by DYNAMICS |
BENNU |
Asteroid number for the object. Used for SPICE Calls |
BFRAME |
Object that defines the body fixed frame to be used in SPC |
ABCORR |
Correction needed for adjustment for light speed (Aberration correction indicates the aberration corrections to be applied to the state of the target body to account for one-way light time and stellar aberration.) |
KERNELS |
Here one lists all of the kernels that are needed to properly project spacecraft camera pointing onto the body-fixed surface |
The make_sumfiles.txt file consists of three sections:
Camera Data Definitions
Enter the number of cameras that the file maintains (NCAM). List the following for each camera:
- 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
Enter sigV0 - The uncertainty of the spacecraft position [km] Enter sigPt - The uncertainty of the camera pointing [Rad]
The PROJECT CAMERA AXIS relates to how the camera is mounted to the spacecraft (it's orientation). I *think* this could be handled by frame kernels, but it isn't done that way right now. Thus, we have to put in a camera orientation matrix. From my testing, it appears that there are 4 orientations that valid.
- 1 2 3
- -1 -2 3
- -2 1 3
- 2 -1 3
Target Information
Enter the follow three rows:
- the names of the ID of the target body
- body fixed frame in the kernels
- aberration correction desired
Kernel List
If the SPICE kernels are not in your working directory, give the path to the kernels (PREFIX).
Start the SPICE kernels list with these two rows:
KERNELS #
List each kernel on a separate row.
- When in doubt, list all the available kernels.
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
End the kernels list with this row:
END_KRNLS
When processing make_sumfiles
If you get the "NOFRAMECONNECT" error (display says, "At epoch...") - You likely need a CK Kernel (<filename>.bc). Additional questions can be answered by referencing NAIF's SPICE website. http://naif.jpl.nasa.gov
If you get the "SPKINSUFFDATA" error (display says, "Insufficient...") - You likely need a SPK Kernel (<filename>.bsp).
Additional Reference
Here is the same make_sumfiles.txt but with additional comments:
Figure 00: Illustration of make_sumfiles.txt File with Explanations
(Compiled by KD)
MAPLIST.TXT
This is a user created text file that is a list of all the maplets. This is created from the *.MAP files, but doesn't contain the ".MAP" at the end. Requires an "END" on the last line.
Example MAPLIST.TXT
AA0001 AA0002 AA0003 AA0004 AA0005 AA0006 AB0001 AB0002 AB0003 AB0004 AB0005 ... IQ0001 IQ0002 IQ0003 IQ0004 IR0001 IR0002 IR0003 IR0004 END
These programs use MAPLIST.TXT.
(Compiled by JRW)
PICTLISTR.TXT
Description
This is a restricted version of PICTLIST.TXT. The user creates this file by pairing down PICTLIST.TXT to only process a subset of pictures in lithos or regres.
For information on its structure, see PICTLIST.TXT.
(Compiled by JW)
PICTLIST.TXT
Category ? |
Version 3.0 |
Description
This text file contains the core list of images that SPC will use. make_sumfiles creates or adds to PICTLIST.TXT when it runs and it lists all the images from make_sumfiles.in. The file terminates with the keyword "END" at the end. The image name starts on column 2, allowing for special characters to be placed in column 1. A space is the normal character before the image name, allowing it to be used.
In SPC, this file would contain all of the images in the entire system. This file is not designed to be changed by hand, but various tools within SPC will make modifications to it. If the image has the symbol # or ! as the first character (rather than a space), that image will be skipped.
lithos will update this file if the command "tuck" is used. Tuck will add or remove a "!" as the first character of an image. This routine is used if there are problems with the image and you don't want to ever use the image (i.e. all SPC routines will ignore this image).
- Warning. If it's present, PICTLISTX.TXT is used before PICTLIST.TXT.
This file is used to make things run faster. However, you must be it is updated with make_pictlistX when new images are added (or tucked). If not, then the old list of images will be used rather than the updated PICTLIST.TXT.
When you run lithos, if you are using PICTLIST.TXT, it will limit images with an emission angle less than 75 degrees.
N585107273F3 N585107729F3 N585107957F3 N585108413F3 N585108641F3 ... ... N585109097F3 N585109325F3 !N585109781F3 !N585110009F3 END
Creating PICTLIST.TXT
If necessary, you can create PICTLIST.TXT by hand by listing the IMAGEFILES directory. This should not normally be needed, and is only likely to be needed if a user mistakenly deleted the original one.
- If you create the file by hand, you must add a space as the first character on each line. Without the leading space, SPC will read the image name wrong, neglecting the first character. You can use "sed" to fix this by using the substitute pattern of "s/^/ /", which is before the 1st character, add a space. SPC uses "!" as the first character to indicate "don't use this image" (also known as a "tucked" image).
The following set of commands show an easy way to create a PICTLIST.TXT file:
cd IMAGES /bin/list > ../PICTLIST.TXT cd .. echo END >> PICTLIST.TXT vi PICTLIST.TXT :%s/^/ / :wq
Here is a sample PICTLIST.TXT file:
FC11A0001225 FC11A0001241 FC11A0001257 FC11A0001258 FC11A0001259 FC11A0001260 ... END
(Compiled by KD)
PICTLISTS.TXT
Description
PICTLISTS.TXT is a user-generated alternative list of picture names used by residuals and geometry. If PICTLISTS.TXT exists then residuals and geometry will use it instead of PICTLIST.TXT to obtain the picture set to work on.
Example PICTLIST.TXT
FC11A0001225 FC11A0001241 FC11A0001257 FC11A0001258 FC11A0001259 FC11A0001260 END
- Note: A space must be included before the picture name and the list must end with the end-of-file identifier, END.
(Compiled by DL)
PICTLISTX.TXT
Description
This text file exists in order to precompute metadata so that other programs run faster. The precomputing is done via make_pictlistX, and only when run explicitly by the user.
make_pictlistX uses PICTLIST.TXT to create PICTLISTX.TXT.
If it's present, PICTLISTX.TXT is used before PICTLIST.TXT.
When you run lithos, if you are using PICTLISTX.TXT, it will limit images with an emission angle less than 85 degrees.
Here is a sample PICTLISTX.TXT file:
FC11A0001225 0.93497E+03 0.998 -0.656 0.439 -0.614 -0.569 0.365 -0.737 FC11A0001241 0.93563E+03 0.998 -0.628 0.520 -0.579 -0.554 0.441 -0.706 FC11A0001257 0.93631E+03 0.998 -0.589 0.599 -0.542 -0.527 0.518 -0.674 FC11A0001258 0.93699E+03 0.998 -0.540 0.673 -0.505 -0.490 0.590 -0.642 FC11A0001259 0.93770E+03 0.998 -0.482 0.741 -0.467 -0.443 0.659 -0.608 FC11A0001260 0.93845E+03 0.998 -0.412 0.805 -0.428 -0.385 0.725 -0.572 ... END
The data included are:
column 1 - Picture name
column 2 - Range from spacecraft to body center
column 3 - Cosine of half the maximum field of view
column 4 - First component of the unit vector from spacecraft to the targets center in BF frame
column 5 - Second component of the unit vector from spacecraft to the targets center in BF frame
column 6 - Third component of the unit vector from spacecraft to the targets center in BF frame
column 7 - First compost of the unit bore sight vector belonging to the camera in BF frame
column 8 - Second compost of the unit bore sight vector belonging to the camera in BF frame
column 9 - Third compost of the unit bore sight vector belonging to the camera in BF frame
(Compiled by KD)
PICTLISTRX.TXT
Description
This user-created file contains a subset (restricted list) of the images in PICTLISTX.TXT. It is similar to PICTLISTR.TXT.
For information on its structure, see PICTLIST.TXT.
(Compiled by JW)