source: trunk/GDE/PHYLIP/doc/dnamove.html

Last change on this file was 2176, checked in by westram, 21 years ago

* empty log message *

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 14.4 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2<HTML>
3<HEAD>
4<TITLE>dnamove</TITLE>
5<META NAME="description" CONTENT="dnamove">
6<META NAME="keywords" CONTENT="dnamove">
7<META NAME="resource-type" CONTENT="document">
8<META NAME="distribution" CONTENT="global">
9<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
10</HEAD>
11<BODY BGCOLOR="#ccffff">
12<DIV ALIGN=RIGHT>
13version 3.6
14</DIV>
15<P>
16<DIV ALIGN=CENTER>
17<H1>DNAMOVE - Interactive DNA parsimony</H1>
18</DIV>
19<P>
20&#169; Copyright 1986-2002 by the University of
21Washington.  Written by Joseph Felsenstein.  Permission is granted to copy
22this document provided that no fee is charged for it and that this copyright
23notice is not removed.
24<P>
25DNAMOVE is an interactive DNA parsimony program, inspired by Wayne Maddison and
26David and Wayne Maddison's marvellous program MacClade, which is written for
27Macintosh computers.  DNAMOVE reads in a data set which is prepared in almost
28the same format as one for the DNA parsimony program DNAPARS.  It allows
29the user to choose an initial tree, and displays this tree on the screen.  The
30user can look at different sites and the way the nucleotide states are
31distributed on that tree, given the most parsimonious reconstruction of state
32changes for that particular tree.  The user then can specify how the tree is to
33be rearraranged, rerooted or written out to a file.  By looking at different
34rearrangements of the tree the user can manually search for the most
35parsimonious tree, and can get a feel for how different sites are affected
36by changes in the tree topology.
37<P>
38This program uses graphic characters that show the tree to best
39advantage on some computer systems.
40Its graphic characters will work best on MSDOS systems or MSDOS windows in
41Windows, and to
42any system whose screen or terminals emulate ANSI standard terminals
43such as old Digital VT100 terminals,
44Telnet programs,
45or VT100-compatible windows in the X windowing system.
46For any other screen types, (such as Macintosh windows) there is a generic
47option which does
48not make use of screen graphics characters.  The program will work well
49in those cases, but the tree it displays will look a bit uglier.
50<P>
51The input data file is set up almost identically to the data files for
52DNAPARS.  The code for nucleotide sequences is the standard one, as
53described in the molecular sequence programs document.
54The user trees are contained in the input tree file
55which is used for input of the starting tree (if desired).  The
56output tree file is used for the final tree.
57<P>
58The user interaction starts with the program presenting a menu.  The
59menu looks like this:
60<P>
61<TABLE><TR><TD BGCOLOR=white>
62<PRE>
63
64Interactive DNA parsimony, version 3.6a3
65
66Settings for this run:
67  O                             Outgroup root?  No, use as outgroup species  1
68  W                            Sites weighted?  No
69  T                   Use Threshold parsimony?  No, use ordinary parsimony
70  I               Input sequences interleaved?  Yes
71  U   Initial tree (arbitrary, user, specify)?  Arbitrary
72  0        Graphics type (IBM PC, ANSI, none)?  (none)
73  S                  Width of terminal screen?  80
74  L                 Number of lines on screen?  24
75
76Are these settings correct? (type Y or the letter for one to change)
77
78</PRE>
79</TD></TR></TABLE>
80<P>
81The O (Outgroup), W (Weights), T (Threshold), and 0 (Graphics type) options
82are the usual
83ones and are described in the main documentation file.  The I
84(Interleaved) option is the usual one and is described in the main
85documentation file and the molecular sequences programs documentation file.
86The U (initial tree) option allows the user to choose whether
87the initial tree is to be arbitrary, interactively specified by the user, or
88read from a tree file.  Typing U causes the program to change among the
89three possibilities in turn.  I
90would recommend that for a first run, you allow the tree to be set up
91arbitrarily (the default), as the "specify" choice is difficult
92to use and the "user tree" choice requires that you have available a tree file
93with the tree topology of the initial tree, which must be a rooted tree.
94Its default name is <TT>intree</TT>.  The program will ask you for its name if
95it looks for the input tree file and does not find one of this name.
96If you wish to set up some
97particular tree you can also do that by the rearrangement commands specified
98below. 
99<P>
100The W (Weights) option allows only weights of 0 or 1.
101<P>
102The T (threshold) option allows a continuum of methods between parsimony and
103compatibility.  Thresholds less than or equal to 1.0 do not have any
104meaning and should not be used: they will result in a tree dependent only on
105the input order of species and not at all on the data!
106<P>
107The L (screen Lines) option allows the user to change the height of the
108screen (in lines of characters) that is assumed to be available on the
109display.  This may be particularly helpful when displaying large trees
110on terminals that have more than 24 lines per screen, or on workstation
111or X-terminal screens that can emulate the ANSI terminals with more than
11224 lines.
113<P>
114After the initial menu is displayed and the choices are made,
115the program then sets up an initial tree and displays it.  Below it will be a
116one-line menu of possible commands, which looks like this:
117<P>
118<PRE>
119NEXT? (Options: R # + - S . T U W O F C H ? X Q) (H or ? for Help)
120</PRE>
121<P>
122If you type H or ? you will get a single screen showing a description of each
123of these commands in a few words.  Here are slightly more detailed
124descriptions:
125<P>
126<DL>
127<DT>R    ("Rearrange")</DT> <DD>  This command asks for the number of a node which is to be
128removed from the tree.  It and everything to the right of it on the tree is to
129be removed (by breaking the branch immediately below it).  The command also
130asks for the number of a node below which that group is to be inserted.  If an
131impossible number is given, the program refuses to carry out the rearrangement
132and asks for a new command.  The rearranged tree is displayed: it will often
133have a different number of steps than the original.  If you wish to undo a
134rearrangement, use the Undo command, for which see below.</DD>
135<DT>#</DT> <DD>This command, and the +, - and S commands described below, determine
136which site has its states displayed on the branches of
137the trees.  The initial tree displayed by the program does not show
138states of sites.  When # is typed, the program does not ask the user which
139site is to be shown but automatically shows the states of the next
140site that is not compatible with the tree (the next site that does not
141perfectly fit the current tree).  The search for this site "wraps around"
142so that if it reaches the last site without finding one that is not
143compatible with the tree, the search continues at the first site; if no
144incompatible site is found the current site is shown again, and if no current
145site is being shown then the first site is shown.  The display takes the form of
146different symbols or textures on the branches of the tree.  The state of each
147branch is actually the state of the node above it.  A key of the symbols or
148shadings used for states A, C, G, T (U) and ? are shown next to the
149tree.  State ? means that more than one possible nucleotide could exist at
150that point
151on the tree, and that the user may want to consider the different
152possibilities, which are usually apparent by inspection.</DD>
153<DT>+</DT> <DD>This command is the same as \# except that it goes forward one site,
154showing the states of the next site.  If no site has been shown, using + will
155cause the first site to be shown.  Once the last site has been
156reached, using + again will show the first site.</DT>
157<P>
158<DT>-</DT>  <DD>This command is the same as + except that it goes backwards, showing the
159states of the previous site.  If no site has been shown, using - will
160cause the last site to be shown.  Once site number 1 has been
161reached, using - again will show the last site.</DD>
162<DT>S    ("Show").</DT> <DD> This command is the same as + and - except that it causes
163the program to ask you for the number of a site.  That site is
164the one whose states will be displayed.  If you give the site number as 0,
165the program will go back to not showing the states of the sites.</DD>
166<DT>. (dot)</DT>  <DD>This command simply causes the current tree to be redisplayed.  It is of
167use when the tree has partly disappeared off of the top of the screen owing to
168too many responses to commands being printed out at the bottom of the screen. 
169</DD>
170<P>
171<DT>T    ("Try rearrangements").</DT> <DD>This command asks for the name of a node.  The
172part of the tree at and above that node is removed from the tree.  The program
173tries to re-insert it in each possible location on the tree (this may take some
174time, and the program reminds you to wait).  Then it prints out a summary.  For
175each possible location the program prints out the number of the node to the
176right of the
177place of insertion and the number of steps required in each case.  These are
178divided into those that are better then or tied with the current tree.  Once
179this summary is printed out, the group that was removed is reinserted into its
180original position.  It is up to you to use the R command to actually carry out
181any of the arrangements that have been tried. </DD>
182<DT>U    ("Undo").</DT> <DD>This command reverses the effect of the most recent
183rearrangement, outgroup re-rooting, or flipping of branches.  It returns to the
184previous tree topology.  It will be of great use when rearranging the tree and
185when a rearrangement proves worse than the preceding one -- it permits you to
186abandon the new one and return to the previous one without remembering its
187topology in detail.</DD>
188<DT>W    ("Write").</DT> <DD>This command writes out the current tree onto a tree output
189file.  If the file already has been written to by this run of DNAMOVE, it will
190ask you whether you want to replace the contents of the file, add the tree to
191the end of the file, or  not write out the tree to the file.  The tree
192is written in the standard format used by PHYLIP (a subset of the
193Newick standard).  It is in the proper format to serve as the
194User-Defined Tree for setting up the initial tree in a subsequent run of the
195program.  Note that if you provided the initial tree topology in a tree file
196and replace its contents, that initial tree will be lost.</DD>
197<DT>O    ("Outgroup").</DT> <DD>This asks for the number of a node which is to be the
198outgroup.  The tree will be redisplayed with that node
199as the left descendant of the bottom fork.  Note that it is possible to
200use this to make a multi-species group the outgroup (i.e., you can give the
201number of an interior node of the tree as the outgroup, and the program will
202re-root the tree properly with that on the left of the bottom fork.</DD>
203<DT>F    ("Flip").</DT> <DD>This asks for a node number and then flips the two branches at
204that node, so that the left-right order of branches at that node is
205changed.  This does not actually change the tree topology (or the number of
206steps on that tree) but it does change the appearance of the tree.</DD>
207<DT>C    ("Clade").</DT> <DD>When the data consist of more than 12 species (or more than
208half the number of lines on the screen if this is not 24), it may be
209difficult to display the tree on one screen.  In that case the tree
210will be squeezed down to
211one line per species.  This is too small to see all the interior states of the
212tree.  The C command instructs the program to print out only that part of the
213tree (the "clade") from a certain node on up.  The program will prompt you for
214the number of this node.  Remember that thereafter you are not looking at the
215whole tree.  To go back to looking at the whole tree give the C command again
216and enter "0" for the node number when asked.  Most users will not want to use
217this option unless forced to.</DD>
218<DT>H    ("Help").</DT> <DD>Prints a one-screen summary of what the commands do, a few
219words for each command.</DD>
220<DT>?    ("huh?").</DT> <DD>A synonym for H.  Same as Help command.</DD>
221<DT>X    ("Exit").</DT> <DD>Exit from program.  If the current tree has not yet been saved
222into a file, the program will first ask you whether it should be saved.</DD>
223<DT>Q    ("Quit").</DT> <DD>A synonym for X.  Same as the eXit command.</DD>
224</DL>
225<P>
226<H3>ADAPTING THE PROGRAM TO YOUR COMPUTER AND TO YOUR TERMINAL</H3>
227<P>
228As we have seen, the initial menu of the program allows you to choose
229among three screen types (PCDOS, Ansi, and none).  We have tried to
230have the default values be correct for PC, Macintosh, and Unix
231screens.  If the setting is "none" (which is necessary on
232Macintosh screens), the special graphics
233characters will not be used to indicate nucleotide states, but only letters
234will be used for the four nucleotides.  This is less easy to look at.
235<P>
236<H2>MORE ABOUT THE PARSIMONY CRITERION</H2>
237<P>
238This program carries out unrooted parsimony (analogous to Wagner
239trees) (Eck and Dayhoff, 1966; Kluge and Farris, 1969) on DNA
240sequences.  The method of Fitch (1971) is used to count the number of
241changes of base needed on a given tree.  The assumptions of this
242method are exactly analogous to those of MIX:
243<P>
244<OL>
245<LI>Each site evolves independently.
246<LI>Different lineages evolve independently.
247<LI>The probability of a base substitution at a given site is
248small over the lengths of time involved in
249a branch of the phylogeny.
250<LI>The expected amounts of change in different branches of the phylogeny
251do not vary by so much that two changes in a high-rate branch
252are more probable than one change in a low-rate branch.
253<LI>The expected amounts of change do not vary enough among sites that two
254changes in one site are more probable than one change in another.
255</OL>
256<P>
257That these are the assumptions of parsimony methods has been documented
258in a series of papers of mine: (1973a, 1978b, 1979, 1981b,
2591983b, 1988b).  For an opposing view arguing that the parsimony methods
260make no substantive
261assumptions such as these, see the papers by Farris (1983) and Sober (1983a,
2621983b), but also read the exchange between Felsenstein and Sober (1986). 
263<P>
264Change from an occupied site to a deletion is counted as one
265change.  Reversion from a deletion to an occupied site is allowed and is also
266counted as one change.
267<P>
268Below is a test data set, but we cannot show the
269output it generates because of the interactive nature of the program.
270<P>
271<HR>
272<P>
273<H3>DATA SET</H3>
274<P>
275<TABLE><TR><TD BGCOLOR=white>
276<PRE>
277   5   13
278Alpha     AACGUGGCCA AAU
279Beta      AAGGUCGCCA AAC
280Gamma     CAUUUCGUCA CAA
281Delta     GGUAUUUCGG CCU
282Epsilon   GGGAUCUCGG CCC
283</PRE>
284</TD></TR></TABLE>
285</BODY>
286</HTML>
Note: See TracBrowser for help on using the repository browser.