Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Nexus format as input in PhyloNext #17

Open
vmikk opened this issue Apr 25, 2024 · 1 comment
Open

Support for Nexus format as input in PhyloNext #17

vmikk opened this issue Apr 25, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@vmikk
Copy link
Owner

vmikk commented Apr 25, 2024

Currently, PhyloNext accepts phylogenetic trees in Newick format (due to its simplicity and widespread use).
However, our pipeline internally converts these Newick trees into Nexus format at one of the intermediate steps.
Given that both Newick and Nexus formats are provided in the outputs, there is a clear benefit to supporting Nexus as an input format directly.

@vmikk vmikk added the enhancement New feature or request label Apr 25, 2024
@vmikk vmikk added this to the 1.5 milestone Apr 25, 2024
@vmikk vmikk self-assigned this Apr 25, 2024
@vmikk
Copy link
Owner Author

vmikk commented Apr 26, 2024

Feature implemented, will be available in PhyloNext 1.5.0

} else if (file_extension(PHYTREE) %in% c("nex", "nexus", "nxs", "Nexus")) {
## Load Nexus tree
cat("..Based on the file extension, the Nexus format detected\n")
TREE <- ape::read.nexus(PHYTREE, force.multi = FALSE)
if("multiPhylo" %in% class(TREE)){
cat("WARNING: The supplied file contains multiple phylogenetic trees, only the first one will be used!\n")
TREE <- TREE[[1]]
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant