AMRFinderPlus v3.10.36
Bug fix release
When multiple identical BLASTX hits occurred in the same query contig, only one hit was optimal and the other hits were less optimal. This bug was apparently introduced in some of the speed optimizations we made in the last year or so.
The problem case appears to be fairly rare in our data. In hundreds of thousands of assemblies in the Pathogen Detection system we see evidence of this issue in less than 0.04% of AMRFinderPlus runs, however it may be more frequent in other data.
A big thank you to fengyuchengdu who reported this bug in issue #94.