Closed xiangpin closed 3 years ago
I obtained the tree file through IQTree and exported the file in nexus format by figtree
As mentioned by @wook2014 , the file was exported by FigTree. This is weird, as FigTree is expected to export BEAST compatible NEXUS file. Please confirm it.
PS: both software tools are all written by Andrew Rambaut.
I have reopened this file with FigTree, it can work, then I reexported it to a nexus
file. And It is weird, the statisicial information is after the labels, not after edge length. But the multiple value also does not have {}
. eg.t1[&mutation="test1","test2","test3"]:0.008
Then I rexport the example file of FigTree, but if multiple value is numeric type, which does have {}
.
@xiangpin It looks like the 'multiple' values of the metadata in the file are contained in a single set of quotation marks, not multiple sets as you show. i..e. t1[&mutation="test1,test2,test3"]:0.008
instead of t1[&mutation="test1","test2","test3"]:0.008
Yes, you are right. But they are not contained in a {}
. So the original read.beast
does not parse it well since it extract the annotation according the marks ={
,}
. In addition, they (t1[&mutation="test1,test2,test3"]:0.008
and t1[&mutation="test1","test2","test3"]:0.008
) are both parsed well since the quotations will be removed in the process.
Description
the problem of nexus format file.
Related Issue
47
Example
this file is different with the beast output file of example.
t1:0.02[&mutation="test1"]
{}
. eg:t2:0.04[&mutation="test1","test2"]