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

nf-validation on samplesheet #88

Merged
merged 4 commits into from
Sep 23, 2023
Merged

nf-validation on samplesheet #88

merged 4 commits into from
Sep 23, 2023

Conversation

Daniel-VM
Copy link
Contributor

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

PR description

Added nf-validation on sample sheet (#87). It enables the parsing of input sample sheets in various formats, including TSV, CSV, and YAML files.

Now, INPUT_CHECK() subworfklow is no longer requiered.

@github-actions
Copy link

github-actions bot commented Sep 22, 2023

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 8ba1df5

+| ✅ 156 tests passed       |+
#| ❔   1 tests were ignored |#
!| ❗   4 tests had warnings |!

❗ Test warnings:

  • pipeline_todos - TODO string in README.md: Describe the minimum required steps to execute the pipeline, e.g. how to prepare samplesheets.
  • pipeline_todos - TODO string in README.md: update the following command to include all required parameters for a minimal example
  • 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
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.9
  • Run at 2023-09-22 14:20:23

@Daniel-VM Daniel-VM requested a review from d4straub September 22, 2023 10:36
nextflow_schema.json Outdated Show resolved Hide resolved
workflows/bacass.nf Outdated Show resolved Hide resolved
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!
I give my ok here before all tests succeeded, please wait until those are all fine.

@d4straub
Copy link
Collaborator

I spotted two warnings in the tests:

WARN: A process with name 'MINIMAP2_CONSENSUS' is defined more than once in module script: /home/runner/work/bacass/bacass/./workflows/bacass.nf -- Make sure to not define the same function as process
WARN: A process with name 'MINIMAP2_POLISH' is defined more than once in module script: /home/runner/work/bacass/bacass/./workflows/bacass.nf -- Make sure to not define the same function as process

that can be easily removed by importing those processes under different names. Maybe for another PR.

@Daniel-VM
Copy link
Contributor Author

Great!!. Thanks for the review.

Concerning the warnings, I've been unable to replicate them when running nextflow run main.nf --profile docker,test_long --ourdir ./results locally (nextflow v23.04.1 ). I could be wrong, but I have not found MINIMAP2_CONSENSUS() or MINIMAP2_POLISH() being invoked twice or more within the 'workflows/bacass.nf' file.

I will test it further and do another PR.

@Daniel-VM Daniel-VM merged commit 463d4b0 into nf-core:dev Sep 23, 2023
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