Skip to content
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

Issues with VFDB Integration and Gene Detection in Abricate #207

Open
mirulee opened this issue Mar 18, 2024 · 0 comments
Open

Issues with VFDB Integration and Gene Detection in Abricate #207

mirulee opened this issue Mar 18, 2024 · 0 comments

Comments

@mirulee
Copy link

mirulee commented Mar 18, 2024

Hello,

I've been primarily using Abricate with the VFDB database and have encountered a couple of issues that I hope can be addressed.

  1. I noticed that Abricate utilizes the VFDB's setA (core dataset) for its database. Attempting to create a custom database using setB (all dataset) from VFDB, I've run into a problem. While Abricate neatly extracts and organizes gene names in its output, the VFDB database format combines gene names with additional information, such as "VFG032131(gb|WP_009917653) (actA) actin-assembly inducing protein precursor [ActA (VF0066) - Motility (VFC0204)] [Listeria monocytogenes SLCC2540]", making it difficult to separately identify gene names. How does Abricate manage to extract gene names separately when using its default database?

  2. For certain samples, specific genes are not detected by Abricate, yet when I submit the same samples directly to the VFDB site, those genes are identified. What could be causing this discrepancy?

Thank you for your assistance in resolving these matters. I look forward to your guidance and suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant