Improving pplacement

[danilodileo]

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 pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,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).

The pull request Implements phylogenetic placement in alternative reference phylogenies based on HMM profile scoring.

[nf-core-bot]

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

[erikrikarddaniel]

@danilodileo, there must be something wrong here. There are 280 changed files! Was your branch not up to date with dev here?

[d4straub]

On the first glance there seem two problems. (1) nf-test output files are included but shouldnt. (2) Something with pulling upstream seems to have gone wrong, because .nf-core.yml attempts to revert to 2.12.0dev.

[danilodileo]

On the first glance there seem two problems. (1) nf-test output files are included but shouldnt. (2) Something with pulling upstream seems to have gone wrong, because .nf-core.yml attempts to revert to 2.12.0dev.

Hi, yes, this was an old PR and even though I updated the branch something went wrong. I am working to fix it!