Differences between revisions 5 and 6
Revision 5 as of 2016-08-09 12:10:47
Size: 2762
Editor: EricPalmer
Comment:
Revision 6 as of 2016-08-09 12:28:46
Size: 3270
Editor: EricPalmer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 70: Line 70:
 * TEST06  * TEST07
Line 77: Line 77:
 * TEST06  * TEST07
Line 92: Line 92:



== Resetting the albedo in lithos ==
If you have some topography that isn't good in your template, you may want to replace it. If you can load the data from another maplet, that works well. However, if you cannot, you can remove the template, setting it to 0. Then as you build a template, you are not fighting bad data.

Within [[lithos]] and the landmark is already loaded
 * a - reset albedo menu
 * y - reset slopes
 * y - reset albedo
Then you can do several "build templates" (0 0 44)

Building a shape model

The normal way (Bob's way) is described in a text file called "densify.txt". I have created a script to automate things in a standard way.

  • Copy the directory "shape3/support3" and put it in the working directory and call it support
     cd <workingDir>
     cp -r ../shape3/support3 support
  • Edit the buildShape.sh file
    • Change the suffix to H2-Test1-
    • Comment out (#) the line that runs dummer
      • dumber < tmpRun.txt | tee -a shape.log # normally used

    • Remove the comment (#) from the line
      • #cp SHAPEFILES/SHAPE.TXT SHAPEFILES/dumb$suffix # used only with initial base model Q=32

This will create several different resolution shape models, each with a factor of 2 higher resolution. The 512 is the highest resolution model, with 1.6 million vectors.

One you create the high resolution model, you can install it in the directory SHAPEFILES. This is done by removing the symbolic link to SHAPE.TXT and replacing it with the new file that you've created.

  •   ln -s shapeH2-Test1-512 SHAPE.TXT

You can run register and load the shape model to see how the new shape model looks.

Note, this shape model does not have albedo in it. If you want to have that, then you need to change the program from densify to densifyA.

  • Run the program
     buildShape.sh
  • When it is done, it will have already run view_shape (via another script viewShape.sh)
  • Look at the files view_01.jpg (01 to 10) and shape.gif

Bigmap

  • Create a bigmap using the TAG site definition.
     bigmap < MTAG15.in
  • Display the map
     showmap
     MTAG15
     convert MTAG15.pgm mtag15.jpg
     open mtag15.jpg

coverage

You can use coverage_p to show how well a region has been tiled.

  •  map_coverage
     MTAG15
     0 .0012
     convert coverage_m.pgm coverage.jpg

Building maplets using bigmap

Previously, we created maplets with the initial topography from the shape model. Once we go beyond 75cm (for Bennu), then the bigmap will have the higher resolution, which will be needed. To do this, we "fill" the maplet with the data from the bigmap rather than the shape model.

Running lithos

  • c
  • TEST07
  • m
  • MTAG15
  • 200 200
  • .00075 49
  • i
  • TEST07
  • y
  • .5
  • n
  • e
  • n
  • 0 50 .2 .2 0 4
  • b - fill with map
  • y - list possibilities
  • n - Auto pick
  • MTAG15

Then just continue processing like normal. It is unlikely that you will need to align to a picture. You now have decent topography with albedo, so you should be able to just 'auto align' to get the images aligned -- that is option "1" and submenu "0" auto align

Resetting the albedo in lithos

If you have some topography that isn't good in your template, you may want to replace it. If you can load the data from another maplet, that works well. However, if you cannot, you can remove the template, setting it to 0. Then as you build a template, you are not fighting bad data.

Within lithos and the landmark is already loaded

  • a - reset albedo menu
  • y - reset slopes
  • y - reset albedo

Then you can do several "build templates" (0 0 44)

Notes for Day 3 (last edited 2016-08-09 19:57:46 by EricPalmer)