Differences between revisions 8 and 27 (spanning 19 versions)
Revision 8 as of 2011-11-29 16:41:18
Size: 620
Editor: EricPalmer
Comment:
Revision 27 as of 2016-01-15 14:47:39
Size: 1317
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= nofit = ## page was renamed from find nofit.e
= nofitT/nofitP/nofit =

Compiled by KD

= Description =

find_nofitT - this routine shows which maplets created during tiling are faulty.

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

find_nofit -

All of the routines listed above determine, which maplets are faulty by going through every .OOT file in the working directory.
Line 10: 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 13: Line 29:
=== Example ===
{{{
 !ZN0205 cat 023.OOT process still running (okay) or process didn’t finish normally (bummer).
Line 14: Line 33:
 * Examples:
  - ! 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.
Line 17: Line 35:
  - LMKNM 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.
}}}
Line 19: Line 38:
  - * LMKNM cat 023.OOT small or no correlation in at least one maplet-image overlap. Should be checked by hand in LITHOS. ----
CategoryPrograms

nofitT/nofitP/nofit

Compiled by KD

Description

find_nofitT - this routine shows which maplets created during tiling are faulty.

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

find_nofit -

All of the routines listed above determine, which maplets are faulty by going through every .OOT file in the working directory.

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)