Description
LatLon_tiling is a way to increase the resolution of a shape model similar to Basic_tiling. The major difference between the two is that Basic_tiling increases the resolution of the shape model one bigmap at a time while LatLon_tiling increases the resolution of the shape model all at once by placing maplets at selected latitude and longitude locations.
The key advantage of LatLon_tiling is that it is faster than Basic_tiling because bigmaps don't have to be created. However, when the resolution needs to be high (below 75 centimeters) a much larger amount of maplets/landmarks need to be created at various coordinates than when the resolution is lower. A large amount of maplets have to be made when doing LatLon_tiling at high resolution because the maplets get smaller as resolution increases and the maplets have to cover the entire surface of the shape model along with overlap. The larger amount of maplets will make LatLon_tiling difficult to manage.
An example of LatLon_tiling being difficult to manage is when it is done at a high resolution, which leads to thousands of maplets/landmarks being produced. When find_nofitT is used to look at the bad landmarks, hundreds if not thousands of errors may pop up. All of those bad landmarks will have to be fixed using Lithos and that sucks. When Basic_tiling is used and regions of the shape model are tiled into bigmaps instead of the entire shape model, then each bigmap will be composed of only hundreds of landmarks, which will most likely have a a lot less misaligned landmarks.
Thus, it is best to use Basic_tiling at higher resolutions because then the various maplets used to create topography are done by region (bigmaps), which leads to better organization. Furthermore, each bigmap will have a lot less bad landmarks than the entire shape model when LatLon tiling is performed, which leads to less landmark clean up for the individual when work for Basic_tiling is distributed by region among others.
LatLon_tiling Outline
1. Set up the files for the rn
2. Run and monitor
Step1
Overview
The will use XXXXXX and XXX020.SEED to generate a suite of files to tile a bigmap.
Output will be exact (diff)
Prep
Copy the reference map to XXXXXX (because Bob likes it that way)
cp MAPFILES/REFMAP.MAP MAPFILES/XXXXXX.MAP
Add map name and seed to the top of the output from make_tilefile, which should be named make_scriptT.in
It should look like this:
XXXXXX
XXX020.SEED
50 50
100 50
150 50
200 50
250 50
300 50
350 50
400 50
450 50
500 50
550 50
600 50
...
900 950
950 950
END
Run
~/bin/make_scriptT
Output
- INN files (1 to 361)
- rem_script.b
- run_script.b
- dsp_list.txt
Step 2
Run
Run, just run the script to make the whole thing go (in the background)
nohup sh run_script.b &
Monitor
Track the progress with find_nofitT
~/bin/find_nofitT
If there are problems with the processing, you'll get a list of landmarks with issues
just listed - no significant issue * very bad - must fix ! not too bad - should fix