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

Fix empty barrnap output #553

Merged
merged 6 commits into from
Mar 14, 2023
Merged

Fix empty barrnap output #553

merged 6 commits into from
Mar 14, 2023

Conversation

jtangrot
Copy link
Contributor

Fix so empty output from barrnap can be handled by sbdi_export, added warnings and error messages id barrnap fails to find rRNA sequences. This adresses #552

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/ampliseq branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@github-actions
Copy link

github-actions bot commented Mar 13, 2023

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 36d1b55

+| ✅ 155 tests passed       |+
#| ❔   1 tests were ignored |#
!| ❗   2 tests had warnings |!

❗ Test warnings:

  • readme - README did not have a Nextflow minimum version badge.
  • schema_lint - Parameter input is not defined in the correct subschema (input_output_options)

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.7.2
  • Run at 2023-03-14 07:46:52

Copy link
Collaborator

@d4straub d4straub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. test_iontorrent now produces a warning that no rRNA were identified.

@jtangrot
Copy link
Contributor Author

Looks good to me. test_iontorrent now produces a warning that no rRNA were identified.

Yes, that's expected as those sequences are ITS2 only, so they are not recognized by barrnap. Do you think we should change the wording in the warning in some way?

@d4straub
Copy link
Collaborator

Do you think we should change the wording in the warning in some way?

Hm, in the warning "Barrnap could not identify any rRNA in the ASV sequences, which seem to be non-ribosomal. We recommended to use the --skip_barrnap option for these sequences." maybe , which seem to be non-ribosomal could be omitted? But thats not critical to me, just a thought. The error is fine I think.

@jtangrot
Copy link
Contributor Author

Changed the wording as suggested. Thanks for approving!

@jtangrot jtangrot merged commit 6bc08cf into nf-core:dev Mar 14, 2023
@jtangrot jtangrot deleted the issue552 branch March 14, 2023 09:05
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

Successfully merging this pull request may close these issues.

2 participants