Differences between revisions 19 and 22 (spanning 3 versions)
Revision 19 as of 2016-01-21 18:00:26
Size: 3801
Editor: DianeLambert
Comment:
Revision 22 as of 2016-02-11 10:54:16
Size: 4470
Editor: BMittan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
(Compiled by DL)
Line 4: Line 3:
'''Purpose:''' Generates the run script and .INN files required to batch autoregister new images using parallel processing. == Description ==
Line 6: Line 5:
=== Requires === This program generates the run script and .INN files required to batch autoregister new images using parallel processing.
Line 8: Line 7:
 * [[make_script.in]] - text file containing the names of the images to batch autoregister.
 * [[make_scriptA.seed]] - text file containing the [[autoregisterP]] option commands for batch registering images.
 * [[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.
=== 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.
Line 13: Line 16:
NB: [[autoregisterP]] requires a number of directories and files - refer to relevant guide.  /!\ '''autoregisterP''' requires a number of directories and files. Refer to [[autoregiserP]] for more information.
Line 15: Line 18:
=== Output === === Output Files ===
Line 17: Line 20:
make_scriptAP outputs: '''make_scriptAP outputs''':
Line 23: Line 26:
 * .INN files - autoregisterP seed file for each image.  * .INN files - [[autoregisterP]] seed file for each image.
Line 25: Line 28:
run_script''nn''.b output: '''run_script''nn''.b output''':
Line 27: Line 30:
 * TESTFILES1/ - a copy of LMRK_DISPLAYnn.pgm (output by [[autoregisterP]]) is saved for each image; '''processed files outputs''':
* [[TESTFILES1]]/ - a copy of LMRK_DISPLAYnn.pgm (output by [[autoregisterP]]) is saved for each image;
Line 31: Line 35:
== 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.

----------
Line 33: Line 42:
=== Create Input Files ===  1. Create Input Files
Line 35: Line 44:
Example '''make_script.in''' file: Here is a sample [[make_script.in]] file (see that entry for further information):
Line 44: Line 53:
NB: A space must precede each image filename.  /!\ You must precede each image filename with a space.
Line 46: Line 55:
Example '''make_scriptA.seed''' file (see [[make_scriptA.seed]] for further details): Here is a sample [[make_scriptA.seed]] file (see that entry for further information):
Line 65: Line 74:
== Run make_scriptAP ==  1.#2 Run [[make_scriptA]]
Line 67: Line 76:
make_scriptAP generates a .INN file for each image (the image filename appended with the autoregisterP options contained in the make_scriptA.seed file. Example '''P00045000450.INN''' file: [[make_scriptA]] 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 a sample .INN file for image '''P00045000450''':
Line 70: Line 81:
nn <-two character USR name to distinguish between processes. nn <- two character USR name to distinguish between processes.
Line 88: Line 99:
make_scriptAP also generates the '''run.sh script''': '''make_scriptAP''' also generates the '''run.sh''' script. Here is a sample run script file for image '''POOO45000450''':
Line 101: Line 112:
and the '''run_script01.b''', '''run_script02.b''', etc: '''make_scriptAP''' also generates the '''run_script01.b''', '''run_script02.b''' files, which look like this:
Line 112: Line 123:
== Batch Autoregister Images Using Parallel Processing ==  1.#3 Batch Autoregister Images Using Parallel Processing
Line 114: Line 125:
[[autoregisterP]] uses the file [[LMRKLISTX.TXT]] to pre- screen the maplets, so if maplets have been added or deleted recently, the procedure [[make_lmrklistX]] should be run.  /!\ '''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''':
Line 120: Line 133:
The autoregisterP standard output for each image is captured in the .OOT files. The user must review the .OOT files to ascertain the success of the batch image autoregistration process. (A ''find-nofit'' program does not currently exist for batch image autoregistration.) 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.
Line 122: Line 135:
== Clean Working Directory ==  (!) There is currently no '''find-nofit''' program for batch image autoregistration.
Line 124: Line 137:
rem_script.b can be used to clean out the directory of make_scriptAP working files once autoregistration is complete and user has quality checked the image correlations:
 1.#4 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
:
Line 132: Line 150:
== User Warnings ==
 * The user must ensure that the correct number of core processors is set for USRMX, a variable contained in [[INIT_LITHOS]], refer to relevant guide for further details.
----------

''(Compiled by DL)''

CategoryPrograms

make_scriptAP

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:

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_scriptnn.b output:

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

  1. Create Input Files

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

 P00045000450
 P00045000451
 P00045000452
END
  • /!\ You must precede each image filename with a space.

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

a
0,65,.25,0,3
1
2
n
0
n
o
.5
4
b
0
q
END   
  1. Run make_scriptA

make_scriptA 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 a sample .INN file for image P00045000450:

nn              <- two character USR name to distinguish between processes.
P00045000450
a
0,65,.25,0,3
1
2
n
0
n
o
.5
4
b
0
q
END   

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.OOT
cp LMRK_DISPLAY01.pgm ./TESTFILES1/P00045000450.pgm
rm -f P00045000452.OOT
/usr/local/bin/AUTOREGISTERP < P00045000451.INN > P00045000451.OOT
cp LMRK_DISPLAY01.pgm ./TESTFILES1/P00045000451.pgm
  1. 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 *.INN
rm -f *.OOT
rm -f run_script*


(Compiled by DL)

CategoryPrograms

make_scriptAP (last edited 2016-07-24 09:42:58 by BMittan)