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.

Sign up for GitHub

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

Jump to bottom

no_est functionality #132

Open
mkandziora opened this issue Jul 18, 2020 · 2 comments
Open

no_est functionality #132

mkandziora opened this issue Jul 18, 2020 · 2 comments
Assignees
@LunaSare

Comments

@mkandziora
Copy link
Contributor

flag no_est does not only not estimate the updated tree, but it also does not look for new sequences. Not sure what the intention of this flag is or if I oversaw something.
@mkandziora mkandziora changed the title no_est does nothing no_est functionality Jul 18, 2020
@snacktavish
Copy link
Collaborator

I updated the message in the help to make clear that it just pulls the input files from OpenTree and or treebase, and aligns them, but does not blast search or estimate the tree.

@LunaSare LunaSare self-assigned this Oct 28, 2021
@LunaSare
Copy link
Collaborator

update in documentation too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LunaSare LunaSare

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@snacktavish @mkandziora @LunaSare