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

Automatic drop of genome leads to error in downstream modules of classify_wf #312

Closed
almutwerner opened this issue Mar 23, 2021 · 1 comment · Fixed by #318
Closed

Automatic drop of genome leads to error in downstream modules of classify_wf #312

almutwerner opened this issue Mar 23, 2021 · 1 comment · Fixed by #318
Labels
enhancement Proposed feature or change to GTDB-Tk. next version Upcoming feature/fix in staging branch.

Comments

@almutwerner
Copy link

Hello!

I am running gtdbtk classify_wf on some of my genomes. During the identify step, one genome was automatically dropped by Prodigal:

Skipping 1 of 202 genomes as no genes were called by Prodigal. Check the genome quality (see gtdb.warnings.log).
Skipping: 3300001969

This resulted in an error, when the script reached the align step:

[2021-03-22 14:09:01] ESC[1;31mERROR:ESC[0m [] are not present in the input list of genome to process.

[2021-03-22 14:09:01] ESC[1;31mERROR:ESC[0m Controlled exit resulting from an unrecoverable error or warning.

================================================================================
EXCEPTION: InconsistentGenomeBatch
MESSAGE: You are attempting to run GTDB-Tk on a non-empty directory that contains extra genomes not present in your initial identify directory. Remove them, or run GTDB-Tk on a new directory.

I tried to rerun in a fresh directory, but that did not work. So I removed the genome from the input fasta folder and the intermediate identify folder, and only then the script continued and finished successfully.

I don't know, if this is really the issue that caused the exception, but if it is, I would suggest making gtdbtk classify_wf aware of genomes dropped by itself, so it does not get confused anymore.

@pchaumeil
Copy link
Collaborator

Hello,
Thanks for the feedback,
We will add this feature in the new release of GTDB-Tk

Regards,
Pierre

@pchaumeil pchaumeil added the enhancement Proposed feature or change to GTDB-Tk. label Mar 25, 2021
@aaronmussig aaronmussig linked a pull request Apr 22, 2021 that will close this issue
@aaronmussig aaronmussig added the next version Upcoming feature/fix in staging branch. label Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Proposed feature or change to GTDB-Tk. next version Upcoming feature/fix in staging branch.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants