-
Notifications
You must be signed in to change notification settings - Fork 125
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
[Request An Update]: Pangolin (constellations) #367
Comments
I'll push a hotfix as soon as I'm able. thanks for raising the issue! |
I've made a dev branch with this change But this issue has me a little worried: cov-lineages/pangolin#449 Are you seeing anything similar? Lots of samples being that were previously given lineages to "Unassigned"? |
Fixes #367 * pangolin 4.0.6: update constellations to 0.1.10 * Update Dockerfile
@garfinjm the docker image is available on dockerhub and quay now: |
Here's a test on the 11 samples that I had posted in cov-lineages/pango-designation#584 that were all originally mis-called as BA.3. Everything seems like it's working to me, thanks for putting together the new image! staphb/pangolin:4.0.6-pdata-1.8
4.0.6-pdata-1.8-constellations-0.1.10
|
OK great, thanks for sharing. So these failed QC, but were still assigned BA.3 via scorpio in the older docker image? (staphb/pangolin:4.0.6-pdata-1.8) Are you running pangolin with lower-than-default |
Yeah, these are all terrible genomes, but they were all called BA.3 which hasnt shown up yet in MN. I got really suspicious when I had 11 on a single run of 92 samples back in April. We are using a pretty barebones pangolin command: |
Contact Details
No response
What container needs an update?
The constelations version in the Pangolin container is causing some issues in our lab and at least one other lab in our region, the v0.1.9 and v0.1.10 updates fix a bug that causes genomes with lots of missing data to be mis-assigned as probable BA.x by Scorpio (some details here: cov-lineages/pango-designation#584)
Thanks for all your work on this!
The text was updated successfully, but these errors were encountered: