source: branches/lib/HELP_SOURCE/source/mg_alignment.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
  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 1.1 KB
Line 
1#       main topics:
2UP      arb.hlp
3UP      glossary.hlp
4UP      alignment.hlp
5UP      arb_merge_workflow.hlp
6
7#       sub topics:
8SUB     ad_align.hlp
9
10
11TITLE           Check/modify consistency of two alignments
12
13OCCURRENCE      ARB_MERGE/Check alignments
14
15DESCRIPTION     Checks the types of data stored within 'alignments' (see LINK{glossary.hlp})
16                for consistency to prevent merging of non homologous
17                data such as 16S and 23S rRNA or protein and DNA sequence data.
18
19                Press the 'Check Alignments' button to display the 'MERGE ALIGNMENTS'
20                window.
21
22                The 'Check' button checks all alignments.
23
24NOTES           If any alignment exists only in the source database (DB) then the alignment
25                will be created in the target DB (but no sequences will be copied).
26
27                If the alignment exists in both databases then the sequence_type
28                will be compared.
29
30                If any inconsistencies are detected the user has to resolve them
31                by pressing the 'MODIFY' button to display the 'ALIGNMENT
32                CONTROL' window. This tool allows to modify the alignments.
33
34EXAMPLES        None
35
36WARNINGS        None
37
38BUGS            No bugs known
39
Note: See TracBrowser for help on using the repository browser.