Differences between revisions 25 and 48 (spanning 23 versions)
Revision 25 as of 2016-01-19 09:23:21
Size: 4527
Comment:
Revision 48 as of 2016-02-17 14:53:44
Size: 5333
Editor: BMittan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= residuals.e = = residuals =
Line 4: Line 4:
Residuals tests the landmarks to look for problems. It will give you a report based on landmarks, pictures and maps. == Description ==
Line 6: Line 6:
=== Input - files ===
 * [[LMKFILES]]
 * [[IMAGEFILES]]
 * [[PICTLIST.TXT]]
 * [[LMRKLIST.TXT]]
This program shows how well SPC has performed. '''residuals''' tests the landmarks to look for problems and gives reports about how well the landmarks were processed. The reports it generates are listed in the Output section.
Line 12: Line 8:
=== Input - stdin === === Input Files ===
 * [[LMKFILES]]/ - a directory containing the full suite of landmarks
 * [[NOMINALS]]/ - a directory containing the image .NOM files (starting solution image, S/C and camera information)
 * [[SUMFILES]]/ - a directory containing the image .SUM files (updated solution image, S/C and camera information, lmrks and limbs)
 * [[IMAGEFILES]] - a directory containing the image .DAT files
 * [[PICTLIST.TXT]] - list of picture names generated by [[make_sumfiles]]
 * [[LMRKLIST.TXT]] - a list of the landmarks contained in the solution
Line 14: Line 16:
 enter plim (px,km,km)

 * The number of pixels an image needs to be "off" (in maplet resolution?) to throw the chevron (>>) flag (in RESIDUALS.TXT)
 * The standard deviation (that is allowed? ask EEP) of the center of each landmark (calculated by taking the vectors from the spacecraft to the center of a landmark; one vector per image in the landmark)
 * Sets the "bin" size for the final histogram (basically how many images are in which categories). This histogram is found at the bottom of PICINFO.TXT.

 input operation list
{{{
     2.5, 1, 001
}}}
=== Optional Files ===
 * [[PICTLISTS.TXT]] - user-generated list of picture names. (If this file exists, it is used instead of [[PICTLIST.TXT]].)
Line 26: Line 20:
=== Output === === Output Files ===
Line 31: Line 25:
 * [[check.txt]] - List of landmarks and overlaps for landmarks whose linear residual is greater than the user-specified limit.
 * [[EMPTY.TXT]] - [[lithos]] seed file for batch deletion of landmarks which are not contained in any pictures or limbs.
 * [[FLATLIST.TXT]] - List of flat maps (landmarks containing no topography).
 * [[LMKVECS.TXT]] - Landmark vectors for every landmark contained in [[LMRKLIST.TXT]].
 * [[MAPCHK.TXT]] - List of maplets whose difference between predicted and observed pixel/line locations in attached images is greater than a user-specified limit, or who have two or fewer overlaps attached to them.
 * [[MAPRES.TXT]] - Maplet resolution information for maplets contained in at least one picture or limb.
 * [[New_Limbs.in]] - [[lithos]] seed file to attach map to limbs for every landmark contained in [[LMRKLIST.TXT]].
 * [[no_update.txt]] - List of landmarks whose associated pictures are not listed by increasing mission time in the .LMK file.
 * [[PRUNE.TXT]] - List of landmarks for which the number of pictures in which they are contained exceeds the default limit of 500, or the user-specified limit, PRNLM, set within [[INIT_LITHOS.TXT]].
 * [[RANGES_SOLVED.TXT]] - Date and range information for each picture listed in [[PICTLISTS.TXT]] or [[PICTLIST.TXT]].
 * [[veto.txt]] - [[lithos]] seed file to detach from landmarks and limbs a map with a linear residual greater than the user-specified limit.
Line 32: Line 37:
== PowerPoint Notes == == Using residuals ==
Line 34: Line 39:
=== Description ===
 * Compares predicted and observed pixel, line position of the landmarks in the images
 * Produces RSS of the diagonal convariance elements of each control point
  * Describes landmark position uncertainty
 * Flags landmarks with residuals over specified pixel value
After you invoke the program, it prompts:
{{{
enter 3 values (px,km,km)
}}}
Line 40: Line 44:
=== Control Points ===  '''value 1''' - the value of the pixel residual limit. Images and maplets are flagged for a pixel residual limit greater than this.
 '''value 2''' - the value of the linear residual beyond which images and maplets are flagged.
  '''value 3''' - the max scale (km/px) that sets the scale for the histogram at the end of [[PICINFO.TXT]].
Line 42: Line 48:
 * Inputs are weights for S/C uncertainties from measurement uncertainties and from a-prior shape constraints
 * Control points solution results in a 3x3 output covariance for each control point. Diagonal elements are uncertainties along maplet coord. system axes, i.e. two horizontal directions & height. Typically SPC produces comparable horizontal & height uncertainties. Results are summarized as a scalar standard deviation per degree of freedom in meters
 * Residuals check automatically flags errors beyond certain input values in dump file for ease of inspection
Here is a sample of inputs for '''residuals''':
Line 46: Line 50:
===== Example ===== {{{
     10, 0.01, 0.01
}}}


Here is a sample [[MAPINFO.TXT]] file:
Line 49: Line 59:
=== Image Residuals === Here is a sample of a single landmark in [[RESIDUALS.TXT]]:
Line 51: Line 61:
 * The post-fit residuals between predicted and actual control point positions in all images are captured in the residuals file
 * The post-fit residuals between predicted and actual control point difference between adjacent, overlapping maplets are captured in the residuals file
 * Outliers in both quantities are flagged automatically based on input threshold criteria

===== Example of a single landmark in RESIDUALS.TXT =====
 * The 1st column is a list of 1. IMAGEFILES included in the landmark 2. overlaps with other landmarks 3. Limbs
 * The 2nd column is the error in deltaX (# pixels in image resolution)
 * The 3rd column is the error in deltaY (# pixels in image resolution)
 * The 4th column is the magnitude of the error (combines deltaX and deltaY)
 * The 5th column is the error in physical units (km)
Line 63: Line 63:
=== Bad & Fixed Image === The following shows what a bad and a fixed image looks like:
Line 67: Line 67:
== Additional Reference ==
Line 68: Line 70:
'''residuals''' is not the only way to check how well SPC performed. You can simply observe the maplets generated.
Line 69: Line 72:
 * Qualitative checks are important to verify that the quantitative error estimates are believable
 * Render a single maplet, or a DEM synthesized by a collection of maplets, at the same geometry & illumination conditions as the images themselves
  * Do all the features in the images appear in the DEM ?
  * Are the smallest discernible features in the images, e.g., boulders, craters etc. visible in the DEM as well ?
  * Is the relative albedo solution such that the relative brightness of adjacent image features matches that of the DEM ?
  * Are the heights solution such that the length and overall appearance of the shadows in the DEM matches that of the image ?
Here is a list of what to look for when you visually inspect a maplet to judge its quality:
Line 76: Line 74:
=== How are Uncertainties Introduced in the Data ===  * Verify that the quantitative error estimates are believable.
 * Render a single maplet, or a DEM synthesized by a collection of maplets, at the same geometry and illumination conditions as the images themselves.
 * Determine if all the features in the images appear in the DEM.
 * Determine if the smallest discernible features in the images (e.g., boulders, craters etc.) are visible in the DEM as well.
 * Determine if the relative albedo solution is such that the relative brightness of adjacent image features matches that of the DEM.
 * Determine if the heights solution is such that the length and overall appearance of the shadows in the DEM match those of the image.
Line 78: Line 81:
 * Main types of uncertainties:
  * S/C trajectory, camera pointing, image timestamp
   * Manifest themselves mostly in the projection of image template onto the surface. Corrected by global geometry solution
  * Image noise, artifacts, smear, overall image quality
   * Manifest themselves in predicted image template brightness and in its fit to the extracted image brightness
  * Photometric model and reflectance function models
   * Show up in slopes & heights integration
  * Poor choice of a-priori parameters & data weights
   * Evident at end of each estimation step; data won’t fit well
=== How Uncertainties are Introduced in the Data ===
Line 88: Line 83:
 * Often above contributions are correlated; individual contributors may not be separated until many processing steps have been taken These are the main types of uncertainties and how they manifest:
 * S/C trajectory, camera pointing, image timestamp
  * Manifest themselves mostly in the projection of image template onto the surface.
  Corrected by global geometry solution.
 * Image noise, artifacts, smear, overall image quality
  * Manifest themselves in predicted image template brightness and in its fit to the extracted image brightness.
 * Photometric model and reflectance function models
  * Show up in slopes & heights integration
 * Poor choice of a-priori parameters and data weights
  * Are evident at the end of each estimation step. Data won’t fit well.
Line 90: Line 94:
---- Often the above contributions are correlated; you may not be able to separate individual contributors until you have taken many processing steps.

-----------

''(Compiled by KD)''

residuals

Description

This program shows how well SPC has performed. residuals tests the landmarks to look for problems and gives reports about how well the landmarks were processed. The reports it generates are listed in the Output section.

Input Files

  • LMKFILES/ - a directory containing the full suite of landmarks

  • NOMINALS/ - a directory containing the image .NOM files (starting solution image, S/C and camera information)

  • SUMFILES/ - a directory containing the image .SUM files (updated solution image, S/C and camera information, lmrks and limbs)

  • IMAGEFILES - a directory containing the image .DAT files

  • PICTLIST.TXT - list of picture names generated by make_sumfiles

  • LMRKLIST.TXT - a list of the landmarks contained in the solution

Optional Files

Output Files

  • MAPINFO.TXT

  • PICINFO.TXT

  • LIMINFO.TXT

  • RESIDUALS.TXT

  • check.txt - List of landmarks and overlaps for landmarks whose linear residual is greater than the user-specified limit.

  • EMPTY.TXT - lithos seed file for batch deletion of landmarks which are not contained in any pictures or limbs.

  • FLATLIST.TXT - List of flat maps (landmarks containing no topography).

  • LMKVECS.TXT - Landmark vectors for every landmark contained in LMRKLIST.TXT.

  • MAPCHK.TXT - List of maplets whose difference between predicted and observed pixel/line locations in attached images is greater than a user-specified limit, or who have two or fewer overlaps attached to them.

  • MAPRES.TXT - Maplet resolution information for maplets contained in at least one picture or limb.

  • New_Limbs.in - lithos seed file to attach map to limbs for every landmark contained in LMRKLIST.TXT.

  • no_update.txt - List of landmarks whose associated pictures are not listed by increasing mission time in the .LMK file.

  • PRUNE.TXT - List of landmarks for which the number of pictures in which they are contained exceeds the default limit of 500, or the user-specified limit, PRNLM, set within INIT_LITHOS.TXT.

  • RANGES_SOLVED.TXT - Date and range information for each picture listed in PICTLISTS.TXT or PICTLIST.TXT.

  • veto.txt - lithos seed file to detach from landmarks and limbs a map with a linear residual greater than the user-specified limit.

Using residuals

After you invoke the program, it prompts:

enter 3 values (px,km,km)
  • value 1 - the value of the pixel residual limit. Images and maplets are flagged for a pixel residual limit greater than this. value 2 - the value of the linear residual beyond which images and maplets are flagged.

    • value 3 - the max scale (km/px) that sets the scale for the histogram at the end of PICINFO.TXT.

Here is a sample of inputs for residuals:

     10, 0.01, 0.01

Here is a sample MAPINFO.TXT file:

residuals_controlpoint1.jpg

Here is a sample of a single landmark in RESIDUALS.TXT:

residuals_imageresiduals.jpg

The following shows what a bad and a fixed image looks like:

residuals_WhatWentWrong.jpg

Additional Reference

Qualitative Checks

residuals is not the only way to check how well SPC performed. You can simply observe the maplets generated.

Here is a list of what to look for when you visually inspect a maplet to judge its quality:

  • Verify that the quantitative error estimates are believable.
  • Render a single maplet, or a DEM synthesized by a collection of maplets, at the same geometry and illumination conditions as the images themselves.
  • Determine if all the features in the images appear in the DEM.
  • Determine if the smallest discernible features in the images (e.g., boulders, craters etc.) are visible in the DEM as well.
  • Determine if the relative albedo solution is such that the relative brightness of adjacent image features matches that of the DEM.
  • Determine if the heights solution is such that the length and overall appearance of the shadows in the DEM match those of the image.

How Uncertainties are Introduced in the Data

These are the main types of uncertainties and how they manifest:

  • S/C trajectory, camera pointing, image timestamp
    • Manifest themselves mostly in the projection of image template onto the surface. Corrected by global geometry solution.
  • Image noise, artifacts, smear, overall image quality
    • Manifest themselves in predicted image template brightness and in its fit to the extracted image brightness.
  • Photometric model and reflectance function models
    • Show up in slopes & heights integration

  • Poor choice of a-priori parameters and data weights
    • Are evident at the end of each estimation step. Data won’t fit well.

Often the above contributions are correlated; you may not be able to separate individual contributors until you have taken many processing steps.


(Compiled by KD)

CategoryPrograms

residuals (last edited 2018-12-20 11:59:10 by JohnWeirich)