make_scriptAP

Category B	Version 3.0

Description

This program generates the run script and .INN files required to batch autoregister new images using parallel processing.

Required Files

input file :

make_script.in - Text file containing the names of the images to batch autoregister.

seed file :

make_scriptA.seed - Text file containing the autoregisterP option commands for batch registering images.

processed files :

INIT_LITHOS - make_scriptAP reads the USRMX (maximum number of core processors) value.

TESTFILES1/ - Directory in which to store copies of LMRK_DISPLAYnn.pgm (output by autoregisterP) for each image.

/!\ autoregisterP requires a number of directories and files. Refer to autoregiserP for more information.

Output Files

make_scriptAP outputs :

run.sh - Controlling run script for batch image auto registration using parallel processing.

run script for each core processor:

run_script01.b

run_script02.b

etc..

.INN files - autoregisterP seed file for each image.

rem_script.b - Script for removal of temporary files (working directory clean-up)

run_script nn .b output :

.OOT files - Standard output from autoregisterP for each image.

processed files outputs :

TESTFILES1/ - A copy of LMRK_DISPLAYnn.pgm (output by autoregisterP) is saved for each image.

SUMFILES/ - Landmarks are added to the image's SUMFILE. Spacecraft/camera position/attitude are updated upon user acceptance of alignment shifts.

LMKFILES/ - Image names are added to the LMKFILES.

User Warnings

/!\ You must set the correct number of core processors for USRMX, a variable contained in INIT_LITHOS. Refer to that entry for further information.

Using make_scriptAP

Create Input Files

Here is a sample make_script.in file (see that entry for further information):

P00045000450 P00045000451 P00045000452END

/!\ You must precede each image filename with a space.

Here is a sample make_scriptA.seed file (see that entry for further information):

a0,65,.25,0,312n0no.54b0qEND

Run make_scriptAP

make_scriptAP generates a .INN file for each image. It consists of the image filename followed by the autoregister options contained in the make_scriptA.seed file.

Here is an annotated sample .INN file for image P00045000450 :

nn <- two character USR name to distinguish between processes.P00045000450a0,65,.25,0,312n0no.54b0qEND

make_scriptAP also generates the run.sh script. Here is a sample run script file for image POOO45000450 :

chmod +x run_script01.b chmod +x run_script02.b ''etc..'' ./run_script01.b & ./run_script02.b & ''etc...''

make_scriptAP also generates the run_script01.b , run_script02.b files, which look like this:

rm -f P00045000450.OOT/usr/local/bin/AUTOREGISTERP < P00045000450.INN > P00045000450.OOTcp LMRK_DISPLAY01.pgm ./TESTFILES1/P00045000450.pgmrm -f P00045000452.OOT/usr/local/bin/AUTOREGISTERP < P00045000451.INN > P00045000451.OOTcp LMRK_DISPLAY01.pgm ./TESTFILES1/P00045000451.pgm

Batch Autoregister Images Using Parallel Processing

/!\ autoregister uses the file LMRKLISTX.TXT to prescreen the maplets. If you have added or deleted maplets recently, you should run make_lmrklistX.

Here is a sample command line for running run.sh :

sh run.sh

The autoregister standard output for each image is captured in the .OOT files. The LMRKDISPLAY1.pgm file output by autoregister is copied and stored in TESTFILES/ once an image has been processed. You must review the .OOT files to ascertain the success of the batch image autoregistration process.

(!) There is currently no find-nofit program for batch image autoregistration.

Clean Working Directory

You can use rem_script.b to clean out the directory of make_scriptAP working files once autoregistration is complete and you have quality checked the image correlations.

Here is a sample rem_script.b file:

rm -f *.INNrm -f *.OOTrm -f run_script*

(Compiled by DL)

CategoryPrograms