nofitT/nofitP/nofit

Compiled by KD

Description

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