Differences between revisions 27 and 46 (spanning 19 versions)
Revision 27 as of 2015-06-02 23:58:23
Size: 2725
Editor: EricPalmer
Comment:
Revision 46 as of 2016-02-08 06:27:40
Size: 5935
Editor: BMittan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 4: Line 3:
This generates a bigmap from a set of maplets. This can be used to generate shape models or images. == Description ==
This procedure creates a large topographical/albedo map with the same file structure as a maplet.
Line 6: Line 6:
=== Requires (created) ===
 * LMKFILES/
 * LMRKLIST/
 * [[LMRKLIST.TXT]] - Required. List of landmarks
 * MAPFILES/
 * SHAPEFILES/
 * [[BIGFILES]]/ - directory of LMK for each of the required bigmaps - directory must be created, but changes are made within.
 * [[SUMFILES]] / - info about the maplets
The location of the map center is specified by one of three choices:
Line 15: Line 8:
=== Requires (created & unique) ===
 * [[BIGLIST.TXT]] - list of needed mapfiles (bigmaps) used to construct the working bigmap
 * [[INSIDE.TXT]] - (Created) The maplets that fall completely within the planned bigmap. Possibility created by bigmap.e
 * [[USED_MAPS]] - (Crated) All the maps used to create the bigmap.
 * Many files must be unique. All directories can be linked to a master.
 * '''p''' - pixel/line location in a picture
 * '''l''' - latitude and west longitude
 * '''m''' - pixel line location in a bigmap or maplet
Line 21: Line 12:
=== Optional ===
 * [[BIGMAP.IN]] - a list of landmarks that you want to use for bigmap. It allows you to reduce the number of files and avoid low resolution images.
 * [[LMRKLIST.TXT]] - Same as above, but only used if [[BIGMAP.IN]] is missing (used for historical purposes)
 * If there are neither of these files, then it will build the list of files that are included in the coverage
A second set of inputs contains:
 * the bigmap scale in km/px
 * the half-size (qsz)
 * an integer random seed
 * a maximum maplet scale in case lower resolution maplets are to be excluded

The program first determines the body-fixed vector to the map center and the approximate
surface normal vector (Uz). It then projects the shape model onto this surface and determines a
second approximation of Uz by fitting a plane to the heights. It repeats this
process one more time. The new map coordinate frame is then oriented so that East is to
the right.

The program checks to see if any these files exist:
 * BIGMAP.IN
 * LMRKLISTR.TXT
 * LMRKLIST.TEXT
It takes the maplets to be used from the first of these files that it finds.

If LMKLX=.TRUE. in [[INIT_LITHOS.TXT]], '''bigmap''' will read LMRKLISTX.TXT. This will speed up the program by determining which maplets will be used without opening their .LMK files.

 (./) ORIGINAL: The maplets to be used in the construction are taken from the first of the files
BIGMAP.IN, LMRKLISTR.TXT or LMRKLIST.TXT found to exist. However, if LMKLX=.TRUE. in the
INIT_LITHOS.TXT file, the program will read LMRKLISTX.TXT. If there are a great many
maplets, the latter choice will speed up the procedure by determining whether a maplet
needs to be used without having to open its .LMK file.

The bigmap reference plane has (2*qsz+1)^2 points at locations:

{{{
p(i,j) = V + j*Ux +i*Uy (i,j = -qsz,qsz)
}}}

A line from each of these points in the normal (Uz) direction will pierce a number of
maplets. For each i,j the program keeps track of:
 * the weighted accumulation of the heights to the piercing points
 * the squares of those heights
 * the slopes and albedos of the maplets at the piercing points

Once these arrays are filled, '''bigmap''' computes the average heights and albedos at each point of the
reference plane, as well as the standard deviation of the heights. This
provides a convenient measure of the height uncertainty at each point. Displaying
[[SIGMAS.pgm]] provides a quick means of identifying possible problem areas.
Line 27: Line 56:
=== Input stdin ===
 * A long set of commands are sent into this program that are usually contained within a file
 /!\ Longitude is in west longitude (meaning that you need a negative to match what is used in [[spheremapB.e]]
== Required Files ==
 * [[LMKFILES]]/ - Directory of .LMK files for each maplet.
 * [[LMRKLIST.TXT]] - Required. List of landmarks.
 * [[MAPFILES]]/ - Directory of .MAP files.
 * [[SHAPEFILES]]/ - Directory of built shapes.
 * [[BIGFILES]]/ - Directory of .LMK files for each of the required bigmaps. This directory must be created, but changes are made within.
 * [[SUMFILES]]/ - Info about the maplets.
 (!) Many files must be unique. All directories can be linked to a master.
Line 31: Line 65:
 * example: == Optional Files ==
 * [[BIGMAP.IN]] - A list of landmarks that you want to use for bigmap. This file allows you to reduce the number of files and avoid low resolution images.
 * [[LMRKLIST.TXT]] - Same as above, but only used if [[BIGMAP.IN]] is missing (used for historical purposes).
 (!) If neither of these files exists, the program will build the list of files that are included in the coverage.

== Output Files ==
 * [[INSIDE.TXT]] - The maplets that fall completely within the planned bigmap. Created by '''bigmap'''.
 * [[USED_MAPS.TXT]] - All the maps used to create the bigmap.
 * [[BIGLIST.TXT]] - List of needed mapfiles (bigmaps) used to construct the working bigmap.
 * [[USED_PICS.TXT]] - List of all pictures used in the creation of most recent bigmap.
 * bigmap - The name is based on the input (e.g., ZN0208.IN).
 * slope.pgm - Image that shows the slope in both horizontal and vertical.
 * [[SIGMAS.TXT]] - Each time BIGMAP is run, it adds a line to this file showing the current sigma values.
 * SIGMAS.pgm - Graphically shows the highest level of error (sigma) for maplets.


== Using bigmap ==

The input for '''bigmap''' consists of a long set of commands that are usually contained within a file (./) what is file name??

 /!\ Longitude is in west longitude. You must use a negative to match what is used in [[spheremapB.e]].

 /!\ The location of '''bigmap''' depends on your server. The default location is /usr/local/bin

Here is a sample input for '''bigmap''':
Line 33: Line 92:
 ~/bin/bigmap.e < ZN0208.IN  ~/bin/bigmap < ZN0208.IN
Line 36: Line 95:
=== Input file ===
The format is normally something like this.
The following sample shows the normal format for the input file (./) what's it called??:
Line 42: Line 100:
   0.06250 500 1.23400 (scale, qsz (number of pixels), seed)    0.06250 500 1.23400 1000 (scale, qsz (number of pixels), seed, max maplet res)
Line 47: Line 105:
1 (end, continue, change weight, smooth, 1 is continue integrating)
1 (end, continue, change weight, smooth, 1 is continue integrating)
1 (end, continue, change weight, smooth, 1 is continue integrating)
0 (end, continue, change weight, smooth, 0 is end iteration)
0 (no, square or round template, 0 is No Template)
1 (end, continue, or change weight, 1 is continue integrating)
0 (end, continue, or change weight, 0 is end iteration)
0 (no, square, or round template, 0 is No Template)
1 (end, continue, or change weight, 1 is continue integrating)
1 (end, continue, or change weight, 1 is continue integrating)
1 (end, continue, or change weight, 1 is continue integrating)
1 (end, continue, or change weight, 1 is continue integrating)
1 (end, continue, or change weight, 1 is continue integrating)
1 (end, continue, or change weight, 1 is continue integrating)
0 (end, continue, or change weight, 0 is end iteration)
0 (no, square, or round template, 0 is No Template)
Line 55: Line 119:
=== Output ===
 * bigmap with the name based on the input (e.g. ZN0208.IN).
 * slopeb.pgm image, that shows the slope in both in horizontal and vertical.
 * SIGMAS.TXT - Each time BIGMAP is run, it will add a line to this file showing the current sigma values
 * SIGMAS.pgm - {{attachment:sig2.jpg}} - It graphically shows the highest level of error (sigma) is for maplets.
Here is a sample of sigmas.pgm:
Line 61: Line 121:
{{attachment:sig2.jpg}}
Line 62: Line 123:
----------
Line 63: Line 125:
CategoryPrograms CategoryPrograms ''(Compiled by TC)''

CategoryPrograms

bigmap

Description

This procedure creates a large topographical/albedo map with the same file structure as a maplet.

The location of the map center is specified by one of three choices:

  • p - pixel/line location in a picture

  • l - latitude and west longitude

  • m - pixel line location in a bigmap or maplet

A second set of inputs contains:

  • the bigmap scale in km/px
  • the half-size (qsz)
  • an integer random seed
  • a maximum maplet scale in case lower resolution maplets are to be excluded

The program first determines the body-fixed vector to the map center and the approximate surface normal vector (Uz). It then projects the shape model onto this surface and determines a second approximation of Uz by fitting a plane to the heights. It repeats this process one more time. The new map coordinate frame is then oriented so that East is to the right.

The program checks to see if any these files exist:

  • BIGMAP.IN
  • LMRKLISTR.TXT
  • LMRKLIST.TEXT

It takes the maplets to be used from the first of these files that it finds.

If LMKLX=.TRUE. in INIT_LITHOS.TXT, bigmap will read LMRKLISTX.TXT. This will speed up the program by determining which maplets will be used without opening their .LMK files.

  • (./) ORIGINAL: The maplets to be used in the construction are taken from the first of the files

BIGMAP.IN, LMRKLISTR.TXT or LMRKLIST.TXT found to exist. However, if LMKLX=.TRUE. in the INIT_LITHOS.TXT file, the program will read LMRKLISTX.TXT. If there are a great many maplets, the latter choice will speed up the procedure by determining whether a maplet needs to be used without having to open its .LMK file.

The bigmap reference plane has (2*qsz+1)^2 points at locations:

p(i,j) = V + j*Ux +i*Uy   (i,j = -qsz,qsz)

A line from each of these points in the normal (Uz) direction will pierce a number of maplets. For each i,j the program keeps track of:

  • the weighted accumulation of the heights to the piercing points
  • the squares of those heights
  • the slopes and albedos of the maplets at the piercing points

Once these arrays are filled, bigmap computes the average heights and albedos at each point of the reference plane, as well as the standard deviation of the heights. This provides a convenient measure of the height uncertainty at each point. Displaying SIGMAS.pgm provides a quick means of identifying possible problem areas.

Required Files

  • LMKFILES/ - Directory of .LMK files for each maplet.

  • LMRKLIST.TXT - Required. List of landmarks.

  • MAPFILES/ - Directory of .MAP files.

  • SHAPEFILES/ - Directory of built shapes.

  • BIGFILES/ - Directory of .LMK files for each of the required bigmaps. This directory must be created, but changes are made within.

  • SUMFILES/ - Info about the maplets. (!) Many files must be unique. All directories can be linked to a master.

Optional Files

  • BIGMAP.IN - A list of landmarks that you want to use for bigmap. This file allows you to reduce the number of files and avoid low resolution images.

  • LMRKLIST.TXT - Same as above, but only used if BIGMAP.IN is missing (used for historical purposes). (!) If neither of these files exists, the program will build the list of files that are included in the coverage.

Output Files

  • INSIDE.TXT - The maplets that fall completely within the planned bigmap. Created by bigmap.

  • USED_MAPS.TXT - All the maps used to create the bigmap.

  • BIGLIST.TXT - List of needed mapfiles (bigmaps) used to construct the working bigmap.

  • USED_PICS.TXT - List of all pictures used in the creation of most recent bigmap.

  • bigmap - The name is based on the input (e.g., ZN0208.IN).
  • slope.pgm - Image that shows the slope in both horizontal and vertical.
  • SIGMAS.TXT - Each time BIGMAP is run, it adds a line to this file showing the current sigma values.

  • SIGMAS.pgm - Graphically shows the highest level of error (sigma) for maplets.

Using bigmap

The input for bigmap consists of a long set of commands that are usually contained within a file (./) what is file name??

  • /!\ Longitude is in west longitude. You must use a negative to match what is used in spheremapB.e.

    /!\ The location of bigmap depends on your server. The default location is /usr/local/bin

Here is a sample input for bigmap:

 ~/bin/bigmap < ZN0208.IN

The following sample shows the normal format for the input file (./) what's it called??:

l   (select location, 1 is lat/lon)
    20    -40    (latitude, west longitude)
   0.06250       500   1.23400   1000  (scale, qsz (number of pixels), seed, max maplet res) 
ZN0208           (filename)
1                (end or integrate, 1 is integrate)
.005             (input fraction)
.025             (input weight)
1                (end, continue, or change weight, 1 is continue integrating)
0                (end, continue, or change weight, 0 is end iteration)
0                (no, square, or round template, 0 is No Template)
1                (end, continue, or change weight, 1 is continue integrating)
1                (end, continue, or change weight, 1 is continue integrating)
1                (end, continue, or change weight, 1 is continue integrating)
1                (end, continue, or change weight, 1 is continue integrating)
1                (end, continue, or change weight, 1 is continue integrating)
1                (end, continue, or change weight, 1 is continue integrating)
0                (end, continue, or change weight, 0 is end iteration)
0                (no, square, or round template, 0 is No Template)

Here is a sample of sigmas.pgm:

sig2.jpg


(Compiled by TC)

CategoryPrograms

bigmap (last edited 2018-06-07 19:51:32 by EricPalmer)