Size: 4337
Comment:
|
Size: 4224
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
= nofitT/nofitP/nofit = | = find_nofit = |
Line 5: | Line 5: |
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. |
|
Line 18: | Line 8: |
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. | This program searches batch processing output files to identify landmarks or images which may need further work. |
Line 20: | Line 10: |
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]]. |
'''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 28: | Line 12: |
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. |
== 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 32: | Line 19: |
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. | == 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 34: | Line 28: |
The procedure could use some major editing, but this will not be done until it can be tested. If it ain't broke ... | == Using find_nofit == |
Line 36: | Line 30: |
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 37: | Line 32: |
At the end of each tiling or iteration, a form of find_nofit (T or P) is used to check for bad landmarks. | === For lithos === |
Line 39: | Line 34: |
* find_nofitT - this routine shows which maplets created during tiling that are faulty. | 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]]. |
Line 41: | Line 44: |
* find_nofitP - this routine shows which maplet created during iteration that are faulty. | === For register === |
Line 43: | Line 46: |
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. | 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. |
Line 45: | Line 52: |
=== 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 == |
Here is a sample output from '''find_nofit''': |
Line 58: | Line 54: |
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 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 70: | Line 72: |
Here is a 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 71: | Line 86: |
== John's notes == !ZN0205 cat 023.OOT process still running (okay) or process didn’t finish normally (bummer). |
Here is a sample [[REMOVED.TXT]] file from '''find_nofit''': {{{ AA0001 <- maplet eliminated from an image for low or no correlation AF0023 }}} |
Line 74: | Line 92: |
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 |
---------- ''(Compiled by DL)'' |
find_nofit
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
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.
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 a 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 a 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 a sample REMOVED.TXT file from find_nofit:
AA0001 <- maplet eliminated from an image for low or no correlation AF0023
(Compiled by DL)