source: tags/arb_5.1/HELP_SOURCE/oldhelp/mark_long_branches.hlp

Last change on this file was 5784, checked in by westram, 15 years ago
  • mark long branches
    • allow to specify a minimum absolute diff
  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 2.0 KB
Line 
1#Please insert up references in the next lines (line starts with keyword UP)
2UP      arb.hlp
3UP      glossary.hlp
4
5#Please insert subtopic references  (line starts with keyword SUB)
6#SUB    subtopic.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 ********
11TITLE           Mark long branches
12
13OCCURRENCE      ARB_NT
14
15DESCRIPTION     Badly aligned sequences often result in long branches in the
16                tree. Being able to identify those branches quickly helps to
17                find those sequences.
18
19                The programs allows to mark all species having an extra
20                long branch compared with it's neighbour branch.
21
22                Enter two values separated by comma into the input field:
23                   * first the minimum relative difference between two neighbour
24                     branches you want to have marked.
25
26                     Examples:
27
28                        100 = mark branches that have more than the double length
29                              compared with their neighbour branch
30                        10  = mark branches that are more than 10% longer
31                        0   = mark branches that are longer than their neighbour branch
32
33                   * second the minimun absolute difference between two neighbour
34                     branches. The unit is the same as used in branchlength.
35
36NOTES           If a branch was marked - it's parent branches will not be marked,
37                i.e. the function does not mark ALL extra long branches, only those
38                nearest to the tips of the trees will get marked - otherwise the
39                output won't be useful.
40
41                Intended workflow is:
42                         * Search long branches
43                         * Check alignment and data and maybe fix it
44                         * Recalculate tree parts (see LINK{pa_add.hlp})
45                         * Search again. Now you most likely will find other branches.
46               
47EXAMPLES        None
48
49WARNINGS        None
50
51BUGS            No bugs known
Note: See TracBrowser for help on using the repository browser.