2
$\begingroup$

ETE3 * (Environment for Tree Exploration) is a major package and in particular Python package to navigate phylogenetic trees. It is the premier coding library/package for tree manipulation.

ETE4.0.0 beta has been released via GitHub. The download contains an old ETE manual (2009) and a README file for ETE4, thats about it. Does anyone know the location of the new ETE4 manual, or list of functionality beyond what is in the README (posted below). Reading the code is the last resort ;-)

README ETE4

  • Read and write support for trees in Newick format
  • Multiple functions for traversing, searching and manipulating tree topologies and node annotations
  • Integration with NCBI Taxonomic database
  • Integration with GTDB database
  • Programmatic visualization framework
  • Visualization of huge trees based on adaptive zooming
  • Comparing trees
  • Phylogenetic functions:
    • orthology detection
    • phylogenetic distance?

Reference * ETE 3: Reconstruction, analysis and visualization of phylogenomic data. Jaime Huerta-Cepas, Francois Serra and Peer Bork. Mol Biol Evol 2016; doi: 10.1093/molbev/msw046

Improve this question
$\endgroup$
4
  • 2
    $\begingroup$ The github page you link to says they have documentation on their official website (etetoolkit.org) and, indeed, clicking on the documentation link there took me to etetoolkit.org/docs/latest/index.html. Is that what you're looking for? $\endgroup$
    – terdon ♦
    Nov 17, 2022 at 15:36
  • 1
    $\begingroup$ Thanks @terdon, this is the documentation for ETE Toolkit 3.0.0b34 (last updated Mar 18, 2016). I recognise the ETE3 to ETE4 is small outside phylogenetics, but it is a big upgrade. The authors may respond here, if not I'll send them this link. $\endgroup$
    – M__ ♦
    Nov 17, 2022 at 16:00
  • 1
    $\begingroup$ I suspect you will get more traction if you just ask on their github. This isn't a question that is likely to be answerable by anyone other than the devs. $\endgroup$
    – terdon ♦
    Nov 17, 2022 at 16:04
  • $\begingroup$ Good point. github.com/etetoolkit/ete/issues/651 ... will pop their response as an answer here. ETE4 has potential. $\endgroup$
    – M__ ♦
    Nov 17, 2022 at 16:13

1 Answer 1

Reset to default
1
$\begingroup$

Just to feedback, the GitHub ticket was:

ETE4.0.0 beta contains an old ETE manual (2009) and a README file for ETE4. Is there an updated ETE4 manual beyond etetoolkit.org/docs/latest/index.html or the README of ETE4?

lm-jkominek wrote,

I know it's a bit of necro, but I wanted to second this request - while the current docs work fine enough for ETE3, they have diverged quite far from ETE4 and there's a bunch of errors that come through when using the latest version that have no explanation...

Thus I'm not alone ... (nothing to do with UAPs BTW)

jhcepas wrote,

absolutely. We are finishing some final changes to the core of ETE4 and will start with the documentation. In the mean time, @jordibc has a list of most important changes regarding compatibility. Could you share somewhere as a wiki page @jordibc ?

jordibc replied,

Yes, we are working on an updated version of the manual to be released with ete4. In the meantime, most of the old code can be run with some of the changes mentioned in the part of the wiki on migrating from ete3 to ete4. @lm-jkominek and @sarscov2 thanks and hope this helps for the moment!

The GitHub wiki was updated here. The Wiki page is kept up to date,

"Jordi Burguet-Castell edited this page 4 days ago · 2 revisions"

The actual additional features (why ETE4 is needed) and how to access them are not listed here. However the changes in syntax are listed. Examples of changes ...

# ETE3
t = Tree(filename) 
# ETE4
t = Tree(open(filename))
# ETE3
Tree(name='Hi', dist=1, support=1) 
# ETE4 
Tree({'name': 'Hi', 'dist': 1, 'support': 1})
# ETE3
Tree(nw, format=1) 
# ETE4 
Tree(nw, parser=1)

In summary there's different syntax. So we can start using ETE4

Improve this answer
$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.