Line | |
---|
1 | #Please insert up references in the next lines (line starts with keyword UP) |
---|
2 | UP arb.hlp |
---|
3 | UP glossary.hlp |
---|
4 | |
---|
5 | #Please insert subtopic references (line starts with keyword SUB) |
---|
6 | #SUB bonds.hlp |
---|
7 | |
---|
8 | # Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain} |
---|
9 | |
---|
10 | #************* Title of helpfile !! and start of real helpfile ******** |
---|
11 | TITLE Probe match (Expert) |
---|
12 | |
---|
13 | OCCURRENCE ARB_NT/Probes/Match Probes/EXPERT |
---|
14 | |
---|
15 | DESCRIPTION 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 | |
---|
36 | NOTES An N-Match is caused either by Ns in the matched probe or |
---|
37 | by Ns in the hit target region. |
---|
38 | |
---|
39 | EXAMPLES None |
---|
40 | |
---|
41 | WARNINGS 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 | |
---|
44 | BUGS No bugs known |
---|
Note: See
TracBrowser
for help on using the repository browser.