= make_scriptR = (Compiled by DL) '''Purpose:''' Generates the run script and .INN files required to batch register new images. === Requires === * make_script.in - text file containing the names of the images to batch register. * [[make_scriptR.seed]] - text file containing the register option commands for batch registering images. NB: [[register]] requires a number of directories and files - refer to relevant guide. === Output === make_scriptR outputs: * run_script.b - run script for batch image registration. * .INN files - register seed file for each image. run_script.b output: * .OOT files - standard output from register for each image. * [[NOMINALS]]/ - if the seed file includes the option to update the NOMINAL file, starting S/C and camera information will be updated (an option not typically selected); * [[SUMFILES]]/ - S/C and camera information are updated as image shifts are made. == Using make_scriptR == === Create Input Files === Example '''make_script.in''' file: {{{ P3T11S2H0409.DAT P3T11S2H0410.DAT P3T11S2H0411.DAT END }}} NB: A space must precede each image filename. Example '''make_scriptR.seed''' file (see [[make_scriptR.seed]] for further details): {{{ s 20 3 y XSTOP 1 10 3 y XSTOP 0 y n n q }}} == Run make_scriptR == make_scriptR generates a .INN file for each image (the image filename appended with the register options contained in the make_scriptR.seed file. Example '''P3T11S2H0409.INN''' file: {{{ P3T11S2H0409 s 20 3 y XSTOP 1 10 3 y XSTOP 0 y n n q }}} make_scriptR also generates the run script - '''run_script.b''': {{{ rm -f P3T11S2H0409.OOT /usr/local/bin/REGISTER < P3T11S2H0409.INN > P3T11S2H0409.OOT cp TEMPFILE.pgm ./TESTFILES/P3T11S2H0409.pgm rm -f P3T11S2H0410.OOT /usr/local/bin/REGISTER < P3T11S2H0410.INN > P3T11S2H0410.OOT cp TEMPFILE.pgm ./TESTFILES/P3T11S2H0410.pgm rm -f P3T11S2H0411.OOT /usr/local/bin/REGISTER < P3T11S2H0411.INN > P3T11S2H0411.OOT cp TEMPFILE.pgm ./TESTFILES/P3T11S2H0411.pgm }}} == Batch Register Images == {{{ sh run_script.b }}} The register 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 registration process. (A ''find-nofit'' program does not currently exist for batch image registration.)