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

Stop prokka from renaming contigs by default #306

Merged
merged 11 commits into from
Aug 31, 2023

Conversation

Darcy220606
Copy link
Contributor

PR checklist

This PR closes this issue #305

  • 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/funcscan 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).

@Darcy220606 Darcy220606 requested a review from a team August 22, 2023 09:34
@github-actions
Copy link

github-actions bot commented Aug 22, 2023

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit fea43ba

+| ✅ 157 tests passed       |+
!| ❗   1 tests had warnings |!

❗ Test warnings:

  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your preferred methods description, e.g. add publication citation for this pipeline

✅ Tests passed:

Run details

  • nf-core/tools version 2.9
  • Run at 2023-08-30 13:26:30

Copy link
Contributor

@louperelo louperelo 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.
Can this have implications on downstream output names, when tools use the PROKKA annotations? For the summary tools maybe?

@Darcy220606
Copy link
Contributor Author

Darcy220606 commented Aug 23, 2023

Looks good to me. Can this have implications on downstream output names, when tools use the PROKKA annotations? For the summary tools maybe?

Yes, it does @louperelo. Found it out when i was running the benchmarking with prokka. In the summary tables i got different contig names that were not comparable to those when i ran bakta or prodigal. To fix this issue, i added this parametre to retain the contig names. But theres a catch. Prokka gets confused when the contig name is overly long (i.e. it combines the coverage and lengths of contigs in the LOCUS in gbk) and then antismash raises an error, therefore, this parametre is by default turned off.

By default if annotaion tool is PROKKA, it changes the contig names to PROKKA_#. So if you have short contig names as input, prokka and antismash should not raise an error if the original contigs are retained.

Copy link
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

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

I swear we went through loops on this and not doing what we already do broke one of the tools..

But making it optional still works 👍

CHANGELOG.md Outdated Show resolved Hide resolved
@Darcy220606 Darcy220606 merged commit e0635da into nf-core:dev Aug 31, 2023
20 checks passed
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.

4 participants