• make_scriptP

make_scriptP

(Compiled by DL)

Purpose: Generates the run script and .INN files required to iterate maplets using lithosP.

Requires

• make_script.in - text file containing a list of the landmarks to be processed, appended with the end-of-file identifier, 'END'.

• make_scriptP.seed - test file containing the lithosP option commands for iterating each maplet.

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

NB: lithosP requires a number of directories and files - refer to relevant guide.

Output

make_scriptP outputs:

• run.sh - controlling run script for batch maplet iteration using parallel processing;
  • run script for each core processor:
    • run_script01.b
    • run_script02.b
    • etc ...

• .INN files - lithosP seed file for each maplet.

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

run_scriptnn.b outputs:

• .OOT files - standard output from lithosP for each landmark.

• SUMFILES/ - S/C and camera information are updated by lithosP as image shifts are accepted. New landmarks and limb fits are added to the SUMFILEs;

• LMKFILES/ - LMKFILES are updated by lithosP.

• MAPFILES/ - MAPFILES are updated by lithosP.

• a number of information text and display files in the working directory are modified by lithosP; please refer to the relevant guide for details.

Using make_scriptP

For guidance with iteration procedures, refer to the 'How-To': Standard_iteration.

Create Input Files

The make_script.in file comprises the list of landmark names for the landmarks which should be processed. It is standard procedure to ensure that the list is ordered by:

• highest-to-lowest maplet ground sample distance;

• name (region identifier (e.g.: FF), unique numeric identifier (e.g.: 0001);

and the user should ensure that duplicate entries do not exist. The program duplicates can be used to generate the make_script.in file.

Example make_script.in file:

EE0001
EE0002
EE0003
etc...
END

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.