Welcome, Guest. Please Login
YaBB - Yet another Bulletin Board
 
  HomeHelpSearchLogin  
 
Dated Tips Molecular Clock Interpretation (Read 3058 times)
aculasso
YaBB Newbies
*
Offline


monkey business

Posts: 13
Buenos Aires - Argentina
Gender: male
Dated Tips Molecular Clock Interpretation
Apr 24th, 2011 at 5:09pm
 
Hi all!
I've my sequences, viral ones, serially taken from a patient. I make the best posible tree (model test, then paup exhaustive search). I ran the DateTipsMolecularClock script, and get some results... a LRT between noclock and clock hypotheses, and a rate with confidence intervals
The question is:
If I get a p value for the test of, say, 0,025... Is the "molecular clock hypothesis" barely rejected? how is constructed the LRT? and last but not least... What does the rates mean if I rejected the clock hypotesis?

Thank you very much!

Regards!

Andrés
Back to top
 
 
IP Logged
 
Sergei
YaBB Administrator
*****
Offline


Datamonkeys are forever...

Posts: 1658
UCSD
Gender: male
Re: Dated Tips Molecular Clock Interpretation
Reply #1 - Apr 27th, 2011 at 10:08am
 
Hi Andrés,

If the p-value is 0.025, then the hypothesis of a strict (single rate) molecular clock is rejected, and you should not be using the estimates from this model, as they are likely to be incorrect. BEAST is the standard package for dealing with relaxed molecular clock estimation -- have you tried using it to obitain rate and date estimates?

Sergei
Back to top
 

Associate Professor
Division of Infectious Diseases
Division of Biomedical Informatics
School of Medicine
University of California San Diego
WWW WWW  
IP Logged
 
aculasso
YaBB Newbies
*
Offline


monkey business

Posts: 13
Buenos Aires - Argentina
Gender: male
Re: Dated Tips Molecular Clock Interpretation
Reply #2 - Apr 29th, 2011 at 10:15am
 
Yes...
The estimations of beast are 10 times higher. However I´m working with very small datasets (6-10 sequences of 700 bp) and I´ve read somewhere that Felsestein said that coalescent analysis are OK for as les as 8 sequences if they are long enough (not my case)

The first approach of my analysis was the evaluation of direct sequences of the viruses (coinfected host). The sequences seem to contain temporal data (topology of tree is compatible with the sampling, and the branch lengths are strongly correlated with the time) but since correlation assumptions are violated by definition by the phylogenies, I was looking for some "quick and dirt, yet better" way for estimating rates... Dated tips sounded fine for me, but then... there is no evidence of clock.

I´ve also tried beast, and in fact the "real" rate analyses were carried out with cloned sequences (about 18 for sample) with beast. The rates I get with beast are x10 or x100 the results of dated tips.

As I understand now, neither the Date Tips nor the beast estimations are reliable since for the former there is not a strict clock and for the last the sample have a small number.

That is the reason of why I became interested in GADatedClock... but I can't find more information about if it is applicable to this situation, or how it works except for your posts, and the succinct description of the script.

¿Should I abandon the analysis of direct sequences?

Thank you for your patience

Andrés
Back to top
 
 
IP Logged