-
Notifications
You must be signed in to change notification settings - Fork 20
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
Error when updating PopPUNK database without reference data #325
Comments
Can you try with PopPUNK 2.7.0 and see if you get the same? I'm also working on a 'fast' update to meet a lot of your preferred criteria which will become available in 2.7.1, but it might be another couple of months before that is ready. |
Sadly, the result is even worse on 2.7.0. I created two fresh conda environments for fair comparsion. The error output of 2.6.3
The output directory of 2.6.3
The error output of 2.7.0
The output directory of 2.7.0
A different error appears in 2.7.0 and the output database is incomplete, while 2.6.3 at least seemingly generated a complete updated database. I understand a new version of PopPUNK could take a while to come out, especially for our niche use case. I am just wondering, do you think the output of 2.6.3 is safe to use despite the error? Thank you! |
The error above in 2.7.0 was also reported in #321 (seems to be related to newer versions of python, as it wasn't in changed code). I have PR #322 being prepared to fix it. You could:
|
I think the last suggestion is the safest and least finicky route before v2.7.1 is out, so I tested it out (used v2.6.3 as it works without further modifications). By adding a A small side effect is it will lead to the generation of "reference" data within the output directory which is actually identical in size to the full size data (can be simply solved by running I further cross-checked this newly generated database against the previously generated database (the one generated without All non- So I think the existing updated database is suitable for further assingment. Of course, I could just replace the existing database with the one generated without error just in case. |
Versions
poppunk 2.6.3
Command used and output returned
An updated database is generated at the output directory, accompanying with this error
Describe the bug
It is related to the usage of full-size (only) database for GPS Project GPSC assignment and its update.
The source database does not have any reference data
It is fine to use for normal assignment, due to the automatic fallback of typical
poppunk_assign
:However, when running
--update-db
, even though the updated full-size database is saved in the first half of the function, the later part of function does not check whether.ref
exists or not, and try to prune it, causing the error.PopPUNK/PopPUNK/assign.py
Lines 755 to 791 in 38b5d18
My question is, whether the updated database is safe to use despite the error? If so, could you please update the
poppunk_assign --update-db
process to handle this situation more elegantly?Thanks!
The text was updated successfully, but these errors were encountered: