-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issue with reporting VIM resistance genes #180
Comments
Based on some testing with a separate workflow that tries to mimic the steps of microSALT for assembly and resistance blasting, it turns out the reason VIM is not reported is because of too small alignment lenghts in the blasting against the beta-lactamase file from ResFinder db. Because of the thresholds for the report (97% identity and 90% alignment length), the matches therefore don't end up in the report, although some matches are found in the blast results. I did test a lot of combinations of assemblers (Spades vs Skesa) and options such as (Trimming vs No trimming) and the various assembly mode flags to Spades. I will exclude other flags than
Thus, the results suggest that switching the assembler from Spades to Skesa and keeping the trimming active might potentially resolve this issue. |
I actually tried replacing Spades with SKESA now (in the branch |/180-fix-missing-vim-genes and now the results look pretty promising. These are the blast results (801 bp should be the full VIM gene, for most variants):
The report does not include them though, since the scraping depends on the contig naming scheme used in Spades, so that logic needs to be updated. But based on all I can see, they are now properly detected. |
I have added a command to convert the naming scheme back to the one used by Spades, so that no changes are needed in the Blast scraping logic. This is merged into PR #178 |
Although the implemented changes in #182 should have improved the situation, the customer has reported a case where a Vim gene is still missing, although it is being reported by ResFinder run on the raw reads. Investigating the issue, it turns out we have a hit, but the longest length (591 bp) is apparently too much shorter than the full gene length of 801 (~74%) bp to be reported (it should be at least 90% of the length):
|
Describe the bug
For some datasets where ResFinder ran on the raw reads report blaVIM beta lactamase resistance genes, there is no report of VIM genes at all in microSALT.
KS reports:
To Reproduce
Steps to reproduce the behavior:
24ET500149
with microSALT 3.3.5Expected behavior
The report for "24ET500149" should include
blaVIM-4
.Software version (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: