Closed Anaphory closed 6 years ago
The Beast XML file contains the tag
<distribution id="timor_tapMRCA" monophyletic="true" spec="beast.math.distributions.MRCAPrior" tree="@Tree.t:beastlingTree">
<taxonset id="timor_tap" spec="TaxonSet">
<plate range="buna1278-bobon,buna1278-suai,fata1247,maka1316,p-east2519" var="language">
<taxon idref="$(language)" />
</plate>
</taxonset>
<Normal id="CalibrationDistribution.timor_tap" mean="3250.0" name="distr" offset="0.0" sigma="127.55102040816327" />
</distribution>
which is also missing Maliana. The tag that should enforce monophyly of Bunaq is entirely missing.
Oops. I just forgot monophyly=True
.
But:
The file I now generated gives the following error from Beast, where BEASTling should already complain (and this is possibly my programming fault or at least something need to consider for the #181 and #152 and #151 stuff):
Error 110 parsing the xml input file
validate and intialize error: 333: Don't know how to generate a Random Tree for taxon sets that intersect, but are not inclusive. Taxonset null and timor_tapMRCA
Error detected about here:
<beast>
<run id='mcmc' spec='MCMC'>
<init id='startingTree' spec='beast.evolution.tree.ConstrainedRandomTree'>
Bah. The loss of Maliana was due to an uncaught typo. Added a raise to the Glottolog lookup.
There is something seriously wrong with specifying a monophyly newick tree. I have the following configuration (using the
language_group
calibration code in my recent pull request, but that's hardly the issue here).The
monophyly_newick
tree is the following, in particular it has a clade(buna1278-bobon,buna1278-suai,buna1278-malia),
.However, the trees I get out of the Beast run (see below) do not have this clade. The starting tree contains
((buna1278-bobon:77.8718,fata1247:77.8718):723.378,buna1278-suai:801.2497)
and the final Bunaq dialect has landed in the wrong family half of the tree.This does not change for subsequent samples.