-
Notifications
You must be signed in to change notification settings - Fork 5
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
Package version information or yml file for conda environment not availble #1
Comments
Hi @m-d-grunnill - I'm so sorry you're having trouble with this. I'm afraid the EV-D68 workflow has been somewhat 'on hold' since the pandemic due to being fully committed to SC2 work (I hope to change this by the end of the year). While I've been running the workflow recently on a recent analysis, it's been on older versions of Nextstrain/Treetime. I'm currently running Treetime 0.8.6 and augur 14.0.0 (pretty old) as I've not had time to update everything and ensure it still works (seems it wouldn't from your experience!). |
Dear @emmahodcroft |
Hi @m-d-grunnill - I'm very glad to hear this worked! Hopefully the bug fix will go through soon, but until then I am glad you can at least get things working! (And that it's not something much harder to solve!) |
@m-d-grunnill the fix has been released in Augur 22.0.3. You should now be able to use the latest versions of Augur and TreeTime for your analyses. Thank you for your patience! |
I couldn't find information on package version in the readme or a yml file in a prominent place.
I am a researcher at Public Health Ontario conducting phylogenetic/dynamic analyses of Enterovirus D68. Unfortunately with some of the latest versions of augur and TimeTree the augur refine function runs into an issue constructing an output json file (see nextstrain/augur#1209) . I found your work on Enterovrius D68 and was hoping from it I could find the correct combination of package versions so I could perform my work Enterovrius D68. Any information on package version combinations you used would be gratefully received.
The text was updated successfully, but these errors were encountered: