Hi Benoit,
I am implementing a parse for GeneRax output, and specifically the reconciled tree in NHX format as that's how they come out of the program with the --reconciliation-samples option.
Doing so, I noticed that some transfer events were not reported in the NHX format, while they were in the recPhyloXML equivalent. See example below:
(BRADYR26_WSM3983__1:0.249317[&&NHX:S=BRADYR26:D=N:H=N:B=0.249317],(...))n338:0.028047[&&NHX:S=clade112:D=N:H=N:B=0.028047]
<clade>
<name>NULL</name>
<eventsRec>
<speciation speciesLocation="clade112"/>
</eventsRec>
<clade>
<name>BRADYR26_WSM3983__1</name>
<eventsRec>
<branchingOut speciesLocation="clade113"/>
</eventsRec>
<clade>
<name>loss</name>
<eventsRec>
<loss speciesLocation="clade113"/>
</eventsRec>
</clade>
<clade>
<name>BRADYR26_WSM3983__1</name>
<eventsRec>
<transferBack destinationSpecies="BRADYR26"/>
<leaf speciesLocation="BRADYR26"/>
</eventsRec>
</clade>
</clade>
<clade>
...
</clade>
</clade>
(I omitted the content of a big clade but I will send you the full files by email)
I don't know if this is an error or just something that is not covered by this tree format.
If it is the latter - or in any case - may I suggest to generate the reconciliation output in the recPhyloXML format instead or in addition of the NHX format only, so to avoid information loss?
I know that the recPhyloXML format is more verbose (~ 6x more) than the NHX format, but still that would not lead to too crazy file sizes, even with 1000 samples in a file; in addition such files would naturally lend themselves to efficient compression given their repetitive nature.
Thanks again for providing this great tool!
All the best,
Florent
Hi Benoit,
I am implementing a parse for GeneRax output, and specifically the reconciled tree in NHX format as that's how they come out of the program with the
--reconciliation-samplesoption.Doing so, I noticed that some transfer events were not reported in the NHX format, while they were in the recPhyloXML equivalent. See example below:
(I omitted the content of a big clade but I will send you the full files by email)
I don't know if this is an error or just something that is not covered by this tree format.
If it is the latter - or in any case - may I suggest to generate the reconciliation output in the recPhyloXML format instead or in addition of the NHX format only, so to avoid information loss?
I know that the recPhyloXML format is more verbose (~ 6x more) than the NHX format, but still that would not lead to too crazy file sizes, even with 1000 samples in a file; in addition such files would naturally lend themselves to efficient compression given their repetitive nature.
Thanks again for providing this great tool!
All the best,
Florent