source: trunk/GDE/PHYLIP/doc/proml.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: 33.1 KB
Line 
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2<HTML>
3<HEAD>
4<TITLE>dnaml</TITLE>
5<META NAME="description" CONTENT="proml">
6<META NAME="keywords" CONTENT="proml">
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>ProML -- Protein Maximum Likelihood program</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>
25This program implements the maximum likelihood method for protein
26amino acid sequences.
27It uses the either the Jones-Taylor-Thornton or the Dayhoff
28probability model of change between amino acids.
29The assumptions of these present models are:
30<OL>
31<LI>Each position in the sequence evolves independently.
32<LI>Different lineages evolve independently.
33<LI>Each position undergoes substitution at an expected rate which is
34chosen from a series of rates (each with a probability of occurrence)
35which we specify.
36<LI>All relevant positions are included in the sequence, not just those that
37have changed or those that are "phylogenetically informative".
38<LI>The probabilities of change between amino acids are given by the
39model of Jones, Taylor, and Thornton (1992) or by the PAM model of
40Dayhoff (Dayhoff and Eck, 1968; Dayhoff et. al., 1979).
41</OL>
42<P>
43Note the assumption that we are looking at all positions, including those
44that have not changed at all.  It is important not to restrict attention
45to some positions based on whether or not they have changed; doing that
46would bias branch lengths by making them too long, and that in turn
47would cause the method to misinterpret the meaning of those positions that
48had changed.
49<P>
50This program uses a Hidden Markov Model (HMM)
51method of inferring different rates of evolution at different amino acid
52positions.  This
53was described in a paper by me and Gary Churchill (1996).  It allows us to
54specify to the program that there will be
55a number of different possible evolutionary rates, what the prior
56probabilities of occurrence of each is, and what the average length of a
57patch of positions all having the same rate.  The rates can also be chosen
58by the program to approximate a Gamma distribution of rates, or a
59Gamma distribution plus a class of invariant positions.  The program computes the
60the likelihood by summing it over all possible assignments of rates to positions,
61weighting each by its prior probability of occurrence.
62<P>
63For example, if we have used the C and A options (described below) to specify
64that there are three possible rates of evolution,  1.0, 2.4, and 0.0,
65that the prior probabilities of a position having these rates are 0.4, 0.3, and
660.3, and that the average patch length (number of consecutive positions
67with the same rate) is 2.0, the program will sum the likelihood over
68all possibilities, but giving less weight to those that (say) assign all
69positions to rate 2.4, or that fail to have consecutive positions that have the
70same rate.
71<P>
72The Hidden Markov Model framework for rate variation among positions
73was independently developed by Yang (1993, 1994, 1995).  We have
74implemented a general scheme for a Hidden Markov Model of
75rates; we allow the rates and their prior probabilities to be specified
76arbitrarily  by the user, or by a discrete approximation to a Gamma
77distribution of rates (Yang, 1995), or by a mixture of a Gamma
78distribution and a class of invariant positions.
79<P>
80This feature effectively removes the artificial assumption that all positions
81have the same rate, and also means that we need not know in advance the
82identities of the positions that have a particular rate of evolution.
83<P>
84Another layer of rate variation also is available.  The user can assign
85categories of rates to each positions (for example, we might want
86amino acid positions in the active site of a protein to change more slowly
87than other positions.  This is done with the categories input file and the
88C option.  We then specify (using the menu) the relative rates of evolution of
89amino acid positions
90in the different categories.  For example, we might specify that positions
91in  the active site
92evolve at relative rates of 0.2 compared to 1.0 at other positions.  If we
93are assuming that a particular position maintains a cysteine bridge to another,
94we may want to put it in a category of positions (including perhaps the
95initial position of the protein sequence which maintains methionine) which
96changes at a rate of 0.0.
97<P>
98If both user-assigned rate categories and Hidden Markov Model rates
99are allowed, the program assumes that the
100actual rate at a position is the product of the user-assigned category rate
101and the Hidden Markov Model regional rate.  (This may not always make
102perfect biological sense: it would be more natural to assume some upper
103bound to the rate, as we have discussed in the Felsenstein and Churchill
104paper).  Nevertheless you may want to use both types of rate variation.
105<P>
106<H2>INPUT FORMAT AND OPTIONS</H2>
107<P>
108Subject to these assumptions, the program is a
109correct maximum likelihood method.  The
110input is fairly standard, with one addition.  As usual the first line of the
111file gives the number of species and the number of amino acid positions.
112<P>
113Next come the species data.  Each
114sequence starts on a new line, has a ten-character species name
115that must be blank-filled to be of that length, followed immediately
116by the species data in the one-letter amino acid code.  The sequences must
117either be in the "interleaved" or "sequential" formats
118described in the Molecular Sequence Programs document.  The I option
119selects between them.  The sequences can have internal
120blanks in the sequence but there must be no extra blanks at the end of the
121terminated line.  Note that a blank is not a valid symbol for a deletion.
122<P>
123The options are selected using an interactive menu.  The menu looks like this:
124<P>
125<TABLE><TR><TD BGCOLOR=white>
126<PRE>
127Amino acid sequence Maximum Likelihood method, version 3.6a3
128
129Settings for this run:
130  U                 Search for best tree?  Yes
131  P   JTT or PAM amino acid change model?  Jones-Taylor-Thornton model
132  C                One category of sites?  Yes
133  R           Rate variation among sites?  constant rate of change
134  W                       Sites weighted?  No
135  S        Speedier but rougher analysis?  Yes
136  G                Global rearrangements?  No
137  J   Randomize input order of sequences?  No. Use input order
138  O                        Outgroup root?  No, use as outgroup species  1
139  M           Analyze multiple data sets?  No
140  I          Input sequences interleaved?  Yes
141  0   Terminal type (IBM PC, ANSI, none)?  (none)
142  1    Print out the data at start of run  No
143  2  Print indications of progress of run  Yes
144  3                        Print out tree  Yes
145  4       Write out trees onto tree file?  Yes
146  5   Reconstruct hypothetical sequences?  No
147
148  Y to accept these or type the letter for one to change
149
150</PRE>
151</TD></TR></TABLE>
152<P>
153The user either types "Y" (followed, of course, by a carriage-return)
154if the settings shown are to be accepted, or the letter or digit corresponding
155to an option that is to be changed.
156<P>
157The options U, W, J, O, M, and 0 are the usual ones.  They are described in the
158main documentation file of this package.  Option I is the same as in
159other molecular sequence programs and is described in the documentation file
160for the sequence programs.
161<P>
162The P option toggles between two models of amino acid change.  One
163is the Jones-Taylor-Thornton model, the other the Dayhoff PAM matrix
164model.   These are both based on Margaret Dayhoff's (Dayhoff and Eck, 1968;
165Dayhoff et. al., 1979) method of empirical tabulation of changes of
166amino acid sequences, and conversion of these to a probability
167model of amino acid change which is used to make a transition probability
168matrix which allows prediction of the probability of changing from any
169one amino acid to any other, and also predicts equilibrium amino acid
170composition.
171<P>
172The default method is that of Jones,
173Taylor, and Thornton (1992).  This is similar to the Dayhoff
174PAM model, except that it is based on a recounting of the number of
175observed changes in amino acids, using a much larger sample of protein
176sequences than did Dayhoff.  Because its sample is so much larger this
177model is to be preferred over the original Dayhoff PAM model.
178The Dayhoff model uses Dayhoff's PAM 001 matrix from
179Dayhoff et. al. (1979), page 348.
180<P>
181The R (Hidden Markov Model rates) option allows the user to
182approximate a Gamma distribution of rates among positions, or a
183Gamma distribution plus a class of invariant positions, or to specify how
184many categories of
185substitution rates there will be in a Hidden Markov Model of rate
186variation, and what are the rates and probabilities
187for each.   By repeatedly selecting the R option one toggles among
188no rate variation, the Gamma, Gamma+I, and general HMM possibilities.
189<P>
190If you choose Gamma or Gamma+I the program will ask how many rate
191categories you want.  If you have chosen Gamma+I, keep in mind that
192one rate category will be set aside for the invariant class and only
193the remaining ones used to approximate the Gamma distribution.
194For the approximation we do not use the quantile method of Yang (1995)
195but instead use a quadrature method using generalized Laguerre
196polynomials.  This should give a good approximation to the Gamma
197distribution with as few as 5 or 6 categories.
198<P>
199In the Gamma and Gamma+I cases, the user will be
200asked to supply the coefficient of variation of the rate of substitution
201among positions.  This is different from the parameters used by Nei and Jin
202(1990) but
203related to them:  their parameter <EM>a</EM> is also known as "alpha",
204the shape parameter of the Gamma distribution.  It is
205related to the coefficient of variation by
206<P>
207&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CV = 1 / a<SUP>1/2</SUP>
208<P>
209or
210<P>
211&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a = 1 / (CV)<SUP>2</SUP>
212<P>
213(their parameter <EM>b</EM> is absorbed here by the requirement that time is scaled so
214that the mean rate of evolution is 1 per unit time, which means that <EM>a = b</EM>).
215As we consider cases in which the rates are less variable we should set <EM>a</EM>
216larger and larger, as <EM>CV</EM> gets smaller and smaller.
217<P>
218If the user instead chooses the general Hidden Markov Model option,
219they are first asked how many HMM rate categories there
220will be (for the moment there is an upper limit of 9,
221which should not be restrictive).  Then
222the program asks for the rates for each category.  These rates are
223only meaningful relative to each other, so that rates 1.0, 2.0, and 2.4
224have the exact same effect as rates 2.0, 4.0, and 4.8.  Note that an
225HMM rate category
226can have rate of change 0, so that this allows us to take into account that
227there may be a category of amino acid positions that are invariant.  Note that
228the run time
229of the program will be proportional to the number of HMM rate categories:
230twice as
231many categories means twice as long a run.  Finally the program will ask for
232the probabilities of a random amino acid position falling into each of these
233regional rate categories.  These probabilities must be nonnegative and sum to
2341.  Default
235for the program is one category, with rate 1.0 and probability 1.0 (actually
236the rate does not matter in that case).
237<P>
238If more than one HMM rate category is specified, then another
239option, A, becomes
240visible in the menu.  This allows us to specify that we want to assume that
241positions that have the same HMM rate category are expected to be clustered
242so that there is autocorrelation of rates.  The
243program asks for the value of the average patch length.  This is an expected
244length of patches that have the same rate.  If it is 1, the rates of
245successive positions will be independent.  If it is, say, 10.25, then the
246chance of change to a new rate will be 1/10.25 after every position.  However
247the "new rate" is randomly drawn from the mix of rates, and hence could
248even be the same.  So the actual observed length of patches with the same
249rate will be a bit larger than 10.25.  Note below that if you choose
250multiple patches, there will be an estimate in the output file as to
251which combination of rate categories contributed most to the likelihood.
252<P>
253Note that the autocorrelation scheme we use is somewhat different
254from Yang's (1995) autocorrelated Gamma distribution.  I am unsure
255whether this difference is of any importance -- our scheme is chosen
256for the ease with which it can be implemented.
257<P>
258The C option allows user-defined rate categories.  The user is prompted
259for the number of user-defined rates, and for the rates themselves,
260which cannot be negative but can be zero.  These numbers, which must be
261nonnegative (some could be 0),
262are defined relative to each other, so that if rates for three categories
263are set to 1 : 3 : 2.5 this would have the same meaning as setting them
264to 2 : 6 : 5.
265The assignment of rates to amino acid positions
266is then made by reading a file whose default name is "categories".
267It should contain a string of digits 1 through 9.  A new line or a blank
268can occur after any character in this string.  Thus the categories file
269might look like this:
270<P>
271<PRE>
272122231111122411155
2731155333333444
274</PRE>
275<P>
276With the current options R, A, and C the program has a good
277ability to infer different rates at different positions and estimate
278phylogenies under a more realistic model.  Note that Likelihood Ratio
279Tests can be used to test whether one combination of rates is
280significantly better than another, provided one rate scheme represents
281a restriction of another with fewer parameters.  The number of parameters
282needed for rate variation is the number of regional rate categories, plus
283the number of user-defined rate categories less 2, plus one if the
284regional rate categories have a nonzero autocorrelation.
285<P>
286The G (global search) option causes, after the last species is added to
287the tree, each possible group to be removed and re-added.  This improves the
288result, since the position of every species is reconsidered.  It
289approximately triples the run-time of the program.
290<P>
291The User tree (option U) is read from a file whose default name is
292<TT>intree</TT>.  The trees can be multifurcating. They must be
293preceded in the file by a line giving the number of trees in the file.
294<P>
295If the U (user tree) option is chosen another option appears in
296the menu, the L option.  If it is selected,
297it signals the program that it
298should take any branch lengths that are in the user tree and
299simply evaluate the likelihood of that tree, without further altering
300those branch lengths.   This means that if some branches have lengths
301and others do not, the program will estimate the lengths of those that
302do not have lengths given in the user tree.  Note that the program RETREE
303can be used to add and remove lengths from a tree.
304<P>
305The U option can read a multifurcating tree.  This allows us to
306test the hypothesis that a certain branch has zero length (we can also
307do this by using RETREE to set the length of that branch to 0.0 when
308it is present in the tree).  By
309doing a series of runs with different specified lengths for a branch we
310can plot a likelihood curve for its branch length while allowing all
311other branches to adjust their lengths to it.  If all branches have
312lengths specified, none of them will be iterated.  This is useful to allow
313a tree produced by another method to have its likelihood
314evaluated.  The L option has no effect and does not appear in the
315menu if the U option is not used.
316<P>
317The W (Weights) option is invoked in the usual way, with only weights 0
318and 1 allowed.  It selects a set of positions to be analyzed, ignoring the
319others.  The positions selected are those with weight 1.  If the W option is
320not invoked, all positions are analyzed.
321The Weights (W) option
322takes the weights from a file whose default name is "weights".  The weights
323follow the format described in the main documentation file.
324<P>
325The M (multiple data sets) option will ask you whether you want to
326use multiple sets of weights (from the weights file) or multiple data sets
327from the input file.
328The ability to use a single data set with multiple weights means that
329much less disk space will be used for this input data.  The bootstrapping
330and jackknifing tool Seqboot has the ability to create a weights file with
331multiple weights.  Note also that when we use multiple weights for
332bootstrapping we can also then maintain different rate categories for
333different positions in a meaningful way.  You should not use the multiple
334data sets option without using multiple weights, you should not at the
335same time use the user-defined rate categories option (option C).
336<P>
337The algorithm used for searching among trees uses
338a technique invented by David Swofford
339and J. S. Rogers.  This involves not iterating most branch lengths on most
340trees when searching among tree topologies,  This is of necessity a
341"quick-and-dirty" search but it saves much time.  There is a menu option
342(option S) which can turn off this search and revert to the earlier
343search method which iterated branch lengths in all topologies.  This will
344be substantially slower but will also be a bit more likely to find the
345tree topology of highest likelihood.  If the Swofford/Rogers search
346finds the best tree topology, the branch lengths inferred will
347be almost precisely the same as they would be with the more thorough
348search, as the maximization of likelihood with respect to branch
349lengths for the final tree is not different in the two kinds of search.
350<P>
351<H2>OUTPUT FORMAT</H2>
352<P>
353The output starts by giving the number of species and the number of amino acid
354positions.
355<P>
356If the R (HMM rates) option is used a table of the relative rates of
357expected substitution at each category of positions is printed, as well
358as the probabilities of each of those rates.
359<P>
360There then follow the data sequences, if the user has selected the menu
361option to print them, with the sequences printed in
362groups of ten amino acids.  The
363trees found are printed as an unrooted
364tree topology (possibly rooted by outgroup if so requested).  The
365internal nodes are numbered arbitrarily for the sake of
366identification.  The number of trees evaluated so far and the log
367likelihood of the tree are also given.  Note that the trees printed out
368have a trifurcation at the base.  The branch lengths in the diagram are
369roughly proportional to the estimated branch lengths, except that very short
370branches are printed out at least three characters in length so that the
371connections can be seen.  The unit of branch length is the expected
372fraction of amino acids changed (so that 1.0 is 100 PAMs).
373<P>
374A table is printed
375showing the length of each tree segment (in units of expected amino acid
376substitutions per position), as well as (very) rough confidence
377limits on their lengths.  If a confidence limit is
378negative, this indicates that rearrangement of the tree in that region
379is not excluded, while if both limits are positive, rearrangement is
380still not necessarily excluded because the variance calculation on which
381the confidence limits are based results in an underestimate, which makes
382the confidence limits too narrow.
383<P>
384In addition to the confidence limits,
385the program performs a crude Likelihood Ratio Test (LRT) for each
386branch of the tree.  The program computes the ratio of likelihoods with and
387without this branch length forced to zero length.  This done by comparing the
388likelihoods changing only that branch length.  A truly correct LRT would
389force that branch length to zero and also allow the other branch lengths to
390adjust to that.  The result would be a likelihood ratio closer to 1.  Therefore
391the present LRT will err on the side of being too significant.  YOU ARE
392WARNED AGAINST TAKING IT TOO SERIOUSLY.  If you want to get a better
393likelihood curve for a branch length you can do multiple runs with
394different prespecified lengths for that branch, as discussed above in the
395discussion of the L option.
396<P>
397One should also
398realize that if you are looking not at a previously-chosen branch but at all
399branches, that you are seeing the results of multiple tests.  With 20 tests,
400one is expected to reach significance at the P = .05 level purely by
401chance.  You should therefore use a much more conservative significance level,
402such as .05 divided by the number of tests.  The significance of these tests
403is shown by printing asterisks next to
404the confidence interval on each branch length.  It is important to keep
405in mind that both the confidence limits and the tests
406are very rough and approximate, and probably indicate more significance than
407they should.  Nevertheless, maximum likelihood is one of the few methods that
408can give you any indication of its own error; most other methods simply fail to
409warn the user that there is any error!  (In fact, whole philosophical schools
410of taxonomists exist whose main point seems to be that there isn't any
411error, that the "most parsimonious" tree is the best tree by definition and
412that's that).
413<P>
414The log likelihood printed out with the final tree can be used to perform
415various likelihood ratio tests.  One can, for example, compare runs with
416different values of the relative rate of change in the active site and in
417the rest of the protein to determine
418which value is the maximum likelihood estimate, and what is the allowable range
419of values (using a likelihood ratio test, which you will find described in
420mathematical statistics books).  One could also estimate the base frequencies
421in the same way.  Both of these, particularly the latter, require multiple runs
422of the program to evaluate different possible values, and this might get
423expensive.
424<P>
425If the U (User Tree) option is used and more than one tree is supplied,
426and the program is not told to assume autocorrelation between the
427rates at different amino acid positions, the
428program also performs a statistical test of each of these trees against the
429one with highest likelihood.   If there are two user trees, the test
430done is one which is due to Kishino and Hasegawa (1989), a version
431of a test originally introduced by Templeton (1983).  In this
432implementation it uses the mean and variance of
433log-likelihood differences between trees, taken across amino acid
434positions.  If the two
435trees' means are more than 1.96 standard deviations different
436then the trees are
437declared significantly different.  This use of the empirical variance of
438log-likelihood differences is more robust and nonparametric than the
439classical likelihood ratio test, and may to some extent compensate for the
440any lack of realism in the model underlying this program.
441<P>
442If there are more than two trees, the test done is an extension of
443the KHT test, due to Shimodaira and Hasegawa (1999).  They pointed out
444that a correction for the number of trees was necessary, and they
445introduced a resampling method to make this correction.  In the version
446used here the variances and covariances of the sum of log likelihoods across
447amino acid positions are computed for all pairs of trees.  To test whether the
448difference between each tree and the best one is larger than could have
449been expected if they all had the same expected log-likelihood,
450log-likelihoods for all trees are sampled with these covariances and equal
451means (Shimodaira and Hasegawa's "least favorable hypothesis"),
452and a P value is computed from the fraction of times the difference between
453the tree's value and the highest log-likelihood exceeds that actually
454observed.  Note that this sampling needs random numbers, and so the
455program will prompt the user for a random number seed if one has not
456already been supplied.  With the two-tree KHT test no random numbers
457are used.
458<P>
459In either the KHT or the SH test the program
460prints out a table of the log-likelihoods of each tree, the differences of
461each from the highest one, the variance of that quantity as determined by
462the log-likelihood differences at individual sites, and a conclusion as to
463whether that tree is or is not significantly worse than the best one.  However
464the test is not available if we assume that there
465is autocorrelation of rates at neighboring positions (option A) and is not
466done in those cases.
467<P>
468The branch lengths printed out are scaled in terms of expected numbers of
469amino acid substitutions, scaled so that the average rate of
470change, averaged over all the positions analyzed, is set to 1.0.
471if there are multiple categories of positions.  This means that whether or not
472there are multiple categories of positions, the expected fraction of change
473for very small branches is equal to the branch length.  Of course,
474when a branch is twice as
475long this does not mean that there will be twice as much net change expected
476along it, since some of the changes occur in the same position and overlie or
477even reverse each
478other.  The branch length estimates here are in terms of the expected
479underlying numbers of changes.  That means that a branch of length 0.26
480is 26 times as long as one which would show a 1% difference between
481the amino acid sequences at the beginning and end of the branch.  But we
482would not expect the sequences at the beginning and end of the branch to be
48326% different, as there would be some overlaying of changes.
484<P>
485Confidence limits on the branch lengths are
486also given.  Of course a
487negative value of the branch length is meaningless, and a confidence
488limit overlapping zero simply means that the branch length is not necessarily
489significantly different from zero.  Because of limitations of the numerical
490algorithm, branch length estimates of zero will often print out as small
491numbers such as 0.00001.  If you see a branch length that small, it is really
492estimated to be of zero length.
493<P>
494Another possible source of confusion is the existence of negative values for
495the log likelihood.  This is not really a problem; the log likelihood is not a
496probability but the logarithm of a probability.  When it is
497negative it simply means that the corresponding probability is less
498than one (since we are seeing its logarithm).  The log likelihood is
499maximized by being made more positive: -30.23 is worse than -29.14.
500<P>
501At the end of the output, if the R option is in effect with multiple
502HMM rates, the program will print a list of what amino acid position
503categories contributed the most to the final likelihood.  This combination of
504HMM rate categories need not have contributed a majority of the likelihood,
505just a plurality.  Still, it will be helpful as a view of where the
506program infers that the higher and lower rates are.  Note that the
507use in this calculations of the prior probabilities of different rates,
508and the average patch length, gives this inference a "smoothed"
509appearance: some other combination of rates might make a greater
510contribution to the likelihood, but be discounted because it conflicts
511with this prior information.  See the example output below to see
512what this printout of rate categories looks like.
513A second list will also be printed out, showing for each position which
514rate accounted for the highest fraction of the likelihood.  If the fraction
515of the likelihood accounted for is less than 95%, a dot is printed instead.
516<P>
517Option 3 in the menu controls whether the tree is printed out into
518the output file.  This is on by default, and usually you will want to
519leave it this way.  However for runs with multiple data sets such as
520bootstrapping runs, you will primarily be interested in the trees
521which are written onto the output tree file, rather than the trees
522printed on the output file.  To keep the output file from becoming too
523large, it may be wisest to use option 3 to prevent trees being
524printed onto the output file.
525<P>
526Option 4 in the menu controls whether the tree estimated by the program
527is written onto a tree file.  The default name of this output tree file
528is "outtree".  If the U option is in effect, all the user-defined
529trees are written to the output tree file.
530<P>
531Option 5 in the menu controls whether ancestral states are estimated
532at each node in the tree.  If it is in effect, a table of ancestral
533sequences is printed out (including the sequences in the tip species which
534are the input sequences).
535The symbol printed out is for the amino acid which accounts for the
536largest fraction of the likelihood at that position.
537In that table, if a position has an amino acid which
538accounts for more than 95% of the likelihood, its symbol printed in capital
539letters (W rather than w).  One limitation of the current
540version of the program is that when there are multiple HMM rates
541(option R) the reconstructed amino acids are based on only the single
542assignment of rates to positions which accounts for the largest amount of the
543likelihood.  Thus the assessment of 95% of the likelihood, in tabulating
544the ancestral states, refers to 95% of the likelihood that is accounted
545for by that particular combination of rates.
546<P>
547<H2>PROGRAM CONSTANTS</H2>
548<P>
549The constants defined at the beginning of the program include "maxtrees",
550the maximum number of user trees that can be processed.  It is small (100)
551at present to save some further memory but the cost of increasing it
552is not very great.  Other constants
553include "maxcategories", the maximum number of position
554categories, "namelength", the length of species names in
555characters, and three others, "smoothings", "iterations", and "epsilon", that
556help "tune" the algorithm and define the compromise between execution speed and
557the quality of the branch lengths found by iteratively maximizing the
558likelihood.  Reducing iterations and smoothings, and increasing epsilon, will
559result in faster execution but a worse result.  These values
560will not usually have to be changed.
561<P>
562The program spends most of its time doing real arithmetic.
563The algorithm, with separate and independent computations
564occurring for each pattern, lends itself readily to parallel processing.
565<P>
566<H2>PAST AND FUTURE OF THE PROGRAM</H2>
567<P>
568This program is derived in version 3.6 by Lucas Mix from DNAML,
569with which it shares
570many of its data structures and much of its strategy.
571<P>
572<HR>
573<P>
574<H3>TEST DATA SET</H3>
575<P>
576(Note that although these may look like DNA sequences, they are being
577treated as protein sequences consisting entirely of alanine, cystine,
578glycine, and threonine).
579<P>
580<TABLE><TR><TD BGCOLOR=white>
581<PRE>
582   5   13
583Alpha     AACGTGGCCAAAT
584Beta      AAGGTCGCCAAAC
585Gamma     CATTTCGTCACAA
586Delta     GGTATTTCGGCCT
587Epsilon   GGGATCTCGGCCC
588</PRE>
589</TD></TR></TABLE>
590<P>
591<HR>
592<H3>CONTENTS OF OUTPUT FILE (with all numerical options on)</H3>
593<P>
594(It was run with HMM rates having gamma-distributed rates
595approximated by 5 rate categories,
596with coefficient of variation of rates 1.0, and with patch length
597parameter = 1.5.  Two user-defined rate categories were used, one for
598the first 6 positions, the other for the last 7, with rates 1.0 : 2.0.
599Weights were used, with sites 1 and 13 given weight 0, and all others
600weight 1.)
601<P>
602<TABLE><TR><TD BGCOLOR=white>
603<PRE>
604
605Amino acid sequence Maximum Likelihood method, version 3.6a3
606
607 5 species,  13  sites
608
609    Site categories are:
610
611             1111112222 222
612
613
614    Sites are weighted as follows:
615
616             0111111111 111
617
618Jones-Taylor-Thornton model of amino acid change
619
620
621Name            Sequences
622----            ---------
623
624Alpha        AACGTGGCCA AAT
625Beta         ..G..C.... ..C
626Gamma        C.TT.C.T.. C.A
627Delta        GGTA.TT.GG CC.
628Epsilon      GGGA.CT.GG CCC
629
630
631
632Discrete approximation to gamma distributed rates
633 Coefficient of variation of rates = 1.000000  (alpha = 1.000000)
634
635States in HMM   Rate of change    Probability
636
637        1           0.264            0.522
638        2           1.413            0.399
639        3           3.596            0.076
640        4           7.086            0.0036
641        5          12.641            0.000023
642
643
644
645Site category   Rate of change
646
647        1           1.000
648        2           2.000
649
650
651
652  +Beta     
653  | 
654  |                                       +Epsilon   
655  |         +-----------------------------3 
656  1---------2                             +-------------------Delta     
657  |         | 
658  |         +--------------------------Gamma     
659  | 
660  +-----------------Alpha     
661
662
663remember: this is an unrooted tree!
664
665Ln Likelihood =  -121.49044
666
667 Between        And            Length      Approx. Confidence Limits
668 -------        ---            ------      ------- ---------- ------
669
670     1          Alpha            60.18362     (     zero,   135.65380) **
671     1          Beta              0.00010     (     zero,    infinity)
672     1             2             32.56292     (     zero,    96.08019) *
673     2             3            141.85557     (     zero,   304.10906) **
674     3          Epsilon           0.00010     (     zero,    infinity)
675     3          Delta            68.68682     (     zero,   151.95402) **
676     2          Gamma            89.79037     (     zero,   198.93830) **
677
678     *  = significantly positive, P < 0.05
679     ** = significantly positive, P < 0.01
680
681Combination of categories that contributes the most to the likelihood:
682
683             1122121111 112
684
685Most probable category at each site if > 0.95 probability ("." otherwise)
686
687             ....1..... ...
688
689Probable sequences at interior nodes:
690
691  node       Reconstructed sequence (caps if > 0.95)
692
693    1        .AGGTCGCCA AAC
694 Beta        AAGGTCGCCA AAC
695    2        .AggTCGCCA CAC
696    3        .GGATCTCGG CCC
697 Epsilon     GGGATCTCGG CCC
698 Delta       GGTATTTCGG CCT
699 Gamma       CATTTCGTCA CAA
700 Alpha       AACGTGGCCA AAT
701
702</PRE>
703</TD></TR></TABLE>
704</BODY>
705</HTML>
Note: See TracBrowser for help on using the repository browser.