"Overlapping taxaSets??" error

54 views
Skip to first unread message

griffinia

unread,
Oct 30, 2018, 4:43:31 PM10/30/18
to beast-users

Hello all,


I am attempting to run, using BEAST 2.5.1, a partitioned (10 loci) divergence dating analysis with two calibration points derived from another publication   I created two taxa sets, one for the stem node of the entire tree (the MRCA of my ingroup and outgroup, thus all taxa in the analysis), and one for just the crown node of my ingroup. I am getting the error shown in the graphic below.


I am not quite sure how to alleviate this, and I will be, as ever, grateful for any guidance.  My XML data file is attached in a zip archive.  


Thanks,

Alan

BEAST2.5.1 error.jpg


ZamiaCaribDiv.zip

Remco Bouckaert

unread,
Oct 30, 2018, 5:10:15 PM10/30/18
to beast...@googlegroups.com
Hi Alan,

Taxon set ZamMicstem contains Abaco, but ZamMicstem1 contains Abraco with an extra r.
This means that these taxon sets are overlapping and cannot be both monophyletic at the same time. I suppose there is a typo in the taxon name, which should be easy to fix.

By the way, the calibrated Yule prior will be extremely slow when using many MRCA priors. It can deal with a few but more than 10 is most likely not going to work. You can use the Yule prior instead, but do have a look at a sample from the prior to be sure that the interaction between calibrations and Yule prior do not change your prior on calibrations too much.

Cheers,

Remco

<BEAST2.5.1 error.jpg>



--
You received this message because you are subscribed to the Google Groups "beast-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beast-users...@googlegroups.com.
To post to this group, send email to beast...@googlegroups.com.
Visit this group at https://groups.google.com/group/beast-users.
For more options, visit https://groups.google.com/d/optout.
<ZamiaCaribDiv.zip><BEAST2.5.1 error.jpg>

griffinia

unread,
Oct 30, 2018, 5:53:28 PM10/30/18
to beast-users
Remco, you are the best! How embarrassing! I had caught this in the Nexus file and thought that I had fixed it - apparently not.

I will give your suggestion on the prior a shot.

Thanks again,
Alan
Reply all
Reply to author
Forward
0 new messages