Differences between revisions 32 and 53 (spanning 21 versions)
Revision 32 as of 2016-01-15 14:54:42
Size: 1710
Comment:
Revision 53 as of 2016-06-06 13:08:35
Size: 4324
Editor: DianeLambert
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from find_nofitT.e
Line 2: Line 3:
= nofitT/nofitP/nofit = = find_nofit =
Line 4: Line 5:
Compiled by KD ||Category B||Version 3.0||
Line 8: Line 9:
At the end of each tiling or iteration, a form of find_nofit (T or P) is used to check for bad landmarks. This program searches batch processing output files to identify landmarks or images which may need further work.
Line 10: Line 11:
 * find_nofitT - this routine shows which maplets created during tiling are faulty. '''find_nofit''' is a useful utility for identifying landmarks which may require further work following batch processing tasks such as those that use [[make_scriptF]] or [[make_scriptR]].
Line 12: Line 13:
 * find_nofitP - this routine shows which maplet created during iteration are faulty. === Required Files ===
 * [[make_script.in]] - input file for batch processes such as [[make_scriptF]], [[make_scriptR]], [[make_scriptA]] or [[make_scriptAP]].
 . Either:
  * <LMRKNM>.OOT files - output by a batch process such as [[make_scriptF]].
 . Or:
  * <PICNM>.OOT files - output by a batch process such as [[make_scriptR]], [[make_scriptA]] or [[make_scriptAP]].
Line 14: Line 20:
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. === Output Files ===
Either:
 * [[redo.txt]] - list of landmarks that
  * 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 that have been eliminated from at least one image due to low or no correlation.
Line 16: Line 29:
----------
Line 17: Line 31:
=== Input ===
 * <3 digit number>.OOT files in the working directory
== Using find_nofit ==
Line 20: Line 33:
=== 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)
The batch processes initiated by [[make_scriptF]], [[make_scriptR]], [[make_scriptA]] and [[make_scriptAP]] produce output files <LMKNM>.OOT or <PICNM>.OOT. These are basically listings of the outputs of procedures [[lithos]], [[register]], [[autoregister]] and [[autoregisterP]] respectively for each input landmark or image. '''find_nofit''' looks through these output files for each landmark or picture listed in the [[make_script.in]] file to identify landmarks or images that may need further work.
Line 27: Line 35:
== Example of Output == === For lithos ===

If the entries in the [[make_script.in]] file are landmarks ([[make_script.in]] for [[lithos]] runs), the '''find_nofit''' procedure identifies:
Line 29: Line 39:
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
! 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 produces 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]].

=== For register ===

If the entries in the [[make_script.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.

Here is an annotated sample output from '''find_nofit''':
{{{
* cat EE0017.OOT <- maplets not correlating with at least one image
   cat EE0019.OOT <- low correlation for at least one overlap
   cat EE0022.OOT
. cat EE0027.OOT <- no correlation for at least one overlap
+ cat EE0034.OOT <- maplets correlating weakly with at least one image
* cat EE0042.OOT
* cat EE0044.OOT
+ cat EE0045.OOT
! cat EE0051.OOT <- process still running or terminated in error
! cat EE0053.OOT
+ cat EE0054.OOT
   cat EE0055.OOT
! cat EE0063.OOT
   cat EE0067.OOT
   cat EE0069.OOT
   cat EE0081.OOT
Line 41: Line 75:
Here is an annotated sample [[redo.txt]] file from '''find_nofit''':
{{{
* EE0017 <- maplets not correlating with at least one image
+ EE0034 <- maplets correlating weakly with at least one image
* EE0042
* EE0044
+ EE0045
EE0051 <- process still running or terminated in error
EE0053
+ EE0054
EE0063
END
}}}
Line 42: Line 89:
== John's notes ==
!ZN0205 cat 023.OOT process still running (okay) or process didn’t finish normally (bummer).
Here is an annotated sample [[REMOVED.TXT]] file from '''find_nofit''':
{{{
AA0001 <- maplet eliminated from an image for low or no correlation
AF0023
}}}
Line 45: Line 95:
ZN0205 cat 023.OOT no correlation in at least one maplet overlap. Probably no big deal. ----------
''(Compiled by DL)''
Line 47: Line 98:
* ZN0205 cat 023.OOT small or no correlation in at least one maplet-image overlap. Should be checked by hand in LITHOS.

----

find_nofit

Category B

Version 3.0

Description

This program searches batch processing output files to identify landmarks or images which may need further work.

find_nofit is a useful utility for identifying landmarks which may require further work following batch processing tasks such as those that use make_scriptF or make_scriptR.

Required Files

Output Files

Either:

  • redo.txt - list of landmarks that

    • 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 that have been eliminated from at least one image due to low or no correlation.


Using find_nofit

The batch processes initiated by make_scriptF, make_scriptR, make_scriptA and make_scriptAP produce output files <LMKNM>.OOT or <PICNM>.OOT. These are basically listings of the outputs of procedures lithos, register, autoregister and autoregisterP respectively for each input landmark or image. find_nofit looks through these output files for each landmark or picture listed in the make_script.in file to identify landmarks or images that may need further work.

For lithos

If the entries in the make_script.in file are landmarks (make_script.in for lithos 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 produces 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.

For register

If the entries in the make_script.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.

Here is an annotated sample output from find_nofit:

*  cat EE0017.OOT              <- maplets not correlating with at least one image
   cat EE0019.OOT              <- low correlation for at least one overlap
   cat EE0022.OOT
.  cat EE0027.OOT              <- no correlation for at least one overlap
+  cat EE0034.OOT              <- maplets correlating weakly with at least one image
*  cat EE0042.OOT
*  cat EE0044.OOT
+  cat EE0045.OOT
!  cat EE0051.OOT              <- process still running or terminated in error
!  cat EE0053.OOT
+  cat EE0054.OOT
   cat EE0055.OOT
!  cat EE0063.OOT
   cat EE0067.OOT
   cat EE0069.OOT
   cat EE0081.OOT

Here is an annotated sample redo.txt file from find_nofit:

* EE0017              <- maplets not correlating with at least one image
+ EE0034              <- maplets correlating weakly with at least one image
* EE0042
* EE0044
+ EE0045
EE0051                <- process still running or terminated in error
EE0053
+ EE0054
EE0063
END

Here is an annotated sample REMOVED.TXT file from find_nofit:

AA0001                <- maplet eliminated from an image for low or no correlation
AF0023


(Compiled by DL)

CategoryPrograms

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