Differences between revisions 15 and 29 (spanning 14 versions)
Revision 15 as of 2015-05-06 11:15:24
Size: 689
Editor: localhost
Comment: converted to 1.6 markup
Revision 29 as of 2016-01-15 14:50:06
Size: 1471
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
= nofit = = 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 are faulty.

 * find_nofitP - this routine shows which maplet created during iteration are faulty.

All of the routines listed above determine, which maplets are faulty by going through every .OOT file in the working directory, which are produced at the end of tiling and iteration.
Line 11: Line 24:
 * LMKNM - minor issue
 * *LMKNM - major issue
 * 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)
Line 14: Line 29:

 {{{ Example
=== Example ===
{{{

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 are faulty.
  • find_nofitP - this routine shows which maplet created during iteration are faulty.

All of the routines listed above determine, which maplets are faulty by going through every .OOT file in the working directory, which are produced at the end of tiling and iteration.

Input

  • stdin: none
  • Works in local directory.
  • CORRECT? - Reads all of the ????.OOT files in the local directory

Output

  • ! - currently running (logfile isn't complete) or there was an error
  • 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

 !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

find_nofit (last edited 2016-06-06 13:08:35 by DianeLambert)