source: branches/lib/HELP_SOURCE/source/pm_spec_param.hlp

Last change on this file was 19532, checked in by westram, 4 months ago
  • reintegrates 'help' into 'trunk'
    • tweak arb documentation:
      • automatically link
        • ticket references to arb bug tracker (only affects html version).
        • found URLs.
      • page titles
        • warn about long titles.
        • introduce SUBTITLEs (automatically triggered by multi-line titles in source files).
        • increase allowed length (limited by subwindow width).
      • cleanup header sections in all helpfiles.
      • fix and/or update several help files.
      • document syntax of help sources.
      • build issues:
        • when xml validation fails, next build no longer uses invalid xml ⇒ keeps failing.
        • remove output files on error (including files below ARBHOME/lib).
        • pipe output through logs to ensure proper wrapping in Entering/Leaving lines.
    • moves Tree admin + NDS menu entries to top of menu
  • adds: log:branches/help@18783:19531
File size: 1.3 KB
Line 
1#       main topics:
2UP      arb.hlp
3UP      glossary.hlp
4
5#       sub topics:
6#SUB     subtopic.hlp
7
8# format described in ../help.readme
9
10
11TITLE           Probe match (Expert)
12
13OCCURRENCE      ARB_NT/Probes/Match Probes/EXPERT
14
15DESCRIPTION     See LINK{bonds.hlp} for upper area.
16
17                Define how many N-matches are accepted:
18
19                       'Accepted N-matches' defines the amount of N-matches that
20                       are accepted without causing a mismatch.
21
22                       'N-match limit' defines an upper limit for N-matches. Whenever
23                       that limit is reached inside one probe, all N-matches count as
24                       mismatches.
25
26                Define max. results:
27
28                       The number of hits is limited to 1 million by default.
29
30                       This is just there to protect you from waiting several
31                       hours for match results, just because your settings were
32                       too lax.
33
34                       Changing it to 0 disables the limitation.
35
36NOTES           An N-Match is caused either by Ns in the matched probe or
37                by Ns in the hit target region.
38
39EXAMPLES        None
40
41WARNINGS        Specifying high values for N-matches and then matching a probe containing
42                many Ns, may keep your machine busy for days. Use with care.
43
44BUGS            No bugs known
Note: See TracBrowser for help on using the repository browser.