nofitT/nofitP/nofit

Compiled by KD

Requires

• .OOT files output by a batch process such as make_scriptF, make_scriptT, make_scriptP, make_scriptR, make_scriptA or make_scriptAP.

Output

Either:

• redo.txt - list of landmarks which terminated in error, do not correlate with at least one image, or correlate weakly with at least one image.

Or:

• REMOVED.TXT - list of landmarks which have been eliminated from at least one image due to low or no correlation.

Description

The batch processes initiated by make_scriptF, make_scriptA and make_scriptAP produce output files LMKNM.OOT or PICNM.OOT, basically listings of the outputs of procedures lithos, lithosP, register, autoregister and autoregisterP for each input landmark or image. find_nofit looks through these output files to find places where the landmarks or images may need further work.

If the entries in the .in file are landmarks (make_script.in or make_scriptT.in for lithos or [lithosP]] runs), the find_nofit procedure identifies:

• ! cat LMKNM.OOT: process still running or terminated in error.
• * cat LMKNM.OOT: maplets not correlating with at least one image.
• + cat LMKNM.OOT: maplets correlating weakly with at least one image.
• . cat LMKNM.OOT: no correlation for at least one overlap.
• cat LMKNM.OOT: low correlation for at least one overlap.

The cat LMKNM.OOT will produce a listing of the output file for more complete diagnostics. The program also produces a redo.txt file listing those landmarks that failed one of the first three tests. The limit for weak correlation is set by the 'NOFIT=' keyword in INIT_LITHOS.TXT.

If the entries in the .in file are images (make_script.in for register, autoregister and autoregisterP runs), the find_nofit procedure identifies:

• . cat PICNM.OOT image not correlating with at least one maplet.

The cat PICNM.OOT will produce a listing of the output file for more complete diagnostics. The program also produces a REMOVED.TXT file listing those landmarks that were eliminated from one of the images for low or no correlation.

It is clear that find_nofit does far more in the LITHOS batch than in the AUTOREGISER batch. This is a relic from the distant past when a "one size fits all" routine was attempted. In the future, the latter may be removed and a find_nofitA program will be written to replace that part.

The procedure could use some major editing, but this will not be done until it can be tested. If it ain't broke ...

At the end of each tiling or iteration, a form of find_nofit (T or P) is used to check for bad landmarks.

• find_nofitT - this routine shows which maplets created during tiling that are faulty.
• find_nofitP - this routine shows which maplet created during iteration that are faulty.

The routines listed above determine faulty maplets by going through every .OOT file in the working directory, which are produced at the end of tiling and iteration when run_script.sh or run.sh are used.

Input

• <3 digit number>.OOT files in the working directory

Output

• ! - currently running (logfile isn't complete) or there was an error and the landmark was deleted
• (blank space) LMKNM - minor issue
• * LMKNM - major issue (at least one image didn't correlate at all the with the map)
• . LMKNM - minor issue (at least one maplet overlap error)
• + LMKNM - moderate issue (at least one image had a correlation below the value set in init_lithos - usually .3 or .4)

Example of Output

EQ0004:   cat 004.OOT 
EP0002:   cat 005.OOT 
EP0003:   cat 006.OOT 
EO0003:   cat 007.OOT 
EN0003: * cat 008.OOT 
EN0004: * cat 009.OOT 
EM0003: . cat 010.OOT 
EM0004: * cat 011.OOT 
132 deleted
   !  cat 132.OOTThe 

John's notes

!ZN0205 cat 023.OOT process still running (okay) or process didn’t finish normally (bummer).

ZN0205 cat 023.OOT no correlation in at least one maplet overlap. Probably no big deal.

* ZN0205 cat 023.OOT small or no correlation in at least one maplet-image overlap. Should be checked by hand in LITHOS.

CategoryPrograms