Small Footprint Processing


In order to avoid overwriting files, we create separate directories for each batch tiling job that we do. However, with the landmarks and mapfiles growing so much (50,000 files each), it is becoming unwieldily.

File Structure

There are two directories that are needed for this system to work.

1. run-master. This directory contains a full set of what is needed to do all SPC tasks (either actual or symbolic links). Basically, I will make symbolic links to the ~/Dropbox/Dawn-shape/Vesta directory for images, seed files, etc. Then for items that get changed, such as landmarks and mapfiles, I have my own copy. I use an rsync script, to keep my copy of these files up to date which what is in the Dropbox.

2. run - This is the working directory that will actually do the processing. I like to number them run1, run2, run3, etc.

Running things

There are two major things that are needed to be done. First, setup the file structure, which is done only once (tasks 1 and 2). Second, setup and run a tiling operation for a big map, something that is done numerous times (tasks 3, 4, 5 and 6)


1. Copy scripts. Get your own copies of the scripts and change the paths as required. Note, an absolute path is needed for symbolic links when used for

2. Setup the run-master directory. The run-master has everything in it that you need to do almost everything (tiling, coverage, bigmaps, shape, etc.) I assume that you have a directory structure with a work directory for your files. Once both and have been run, the run-master directory will be a full and complete directory that can run about any program.

3. Create a working (or run) directory.

Basically, you need a directory similar to ~/Dropbox/Dawn-shape/work_generic, but without the landmarks and mapfiles. You can create it from scratch by taking a blank directory and running just the script. Everything else should be generated by the script.

4. Configure (or just check) the parameters that you will be using for the run. You will do then whenever you need to deal with different overlap of landmarks (usually when you finish a swatch of the surface, such as when you finish the set from ZS0200 to ZS0270). will generate a new based on parameters in the file. Change the left, right, top and bottom to set the boundaries for the file. The default for a empty region (no previous overlap) would be left and top = 50, and right and bottom = 950. If there is overlap, you can change those value to limit the generation of landmarks (such as left=200, right=800). If the autogenerated doesn't work for you, just replace it with something that you tailored by hand and run make_scriptT.e

5. In the working directory, run the with the bigmap name that you want to tile. You must be in your working directory because it will copy everything into that one. It will update the run-master directory and do processing within that file structure, to include changing files. will remove all old files, create directories and symbolic links. Then it will run bigmap which is a "cheat" to figure out the overlapping mapfiles that must be exported. bigmap uses the <mapname>.IN file that are located in the Dropbox/Dawn-shape/Vesta directory. Then it exports the needed files and configures them in the working directory. Finally, it will auto-generate and run make_scriptT.e. The whole process takes about 5 minutes.

You will have to explicitly start the tiling process (and I suggest you check things to ensure they make sense).

6. Run the generated script, run_script.b which was also created by make_scriptT.e. I suggest checking to see if it makes sense. Also, an ls *INN will show all the parameter files that lithos will be using.

7. Watch things run. You can use find_nofitT.e to see the progress

Small_Footprint_Processing (last edited 2016-01-13 15:20:31 by JohnWeirich)