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

Make --outdir mandatory, tin.py opt-in and fix #750 #771

Merged
merged 8 commits into from
Feb 22, 2022

Conversation

drpatelh
Copy link
Member

@drpatelh drpatelh commented Feb 21, 2022

  • nf-core/tools#1415 - Make --outdir a mandatory parameter
  • [#750] - Optionally ignore R1 / R2 after UMI extraction process
  • [#769] - Do not run RSeQC tin.py by default

@github-actions
Copy link

github-actions bot commented Feb 21, 2022

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit 3016c0b

+| ✅ 131 tests passed       |+
#| ❔   9 tests were ignored |#
!| ❗   1 tests had warnings |!

❗ Test warnings:

❔ Tests ignored:

  • files_unchanged - File ignored due to lint config: .github/ISSUE_TEMPLATE/bug_report.yml
  • files_unchanged - File ignored due to lint config: .github/PULL_REQUEST_TEMPLATE.md
  • files_unchanged - File ignored due to lint config: .github/workflows/branch.yml
  • files_unchanged - File ignored due to lint config: .github/workflows/linting_comment.yml
  • files_unchanged - File ignored due to lint config: .github/workflows/linting.yml
  • files_unchanged - File ignored due to lint config: assets/email_template.html
  • files_unchanged - File ignored due to lint config: assets/email_template.txt
  • files_unchanged - File ignored due to lint config: lib/NfcoreSchema.groovy
  • files_unchanged - File ignored due to lint config: lib/NfcoreTemplate.groovy

✅ Tests passed:

Run details

  • nf-core/tools version 2.2
  • Run at 2022-02-22 09:28:30

Copy link
Member

@mahesh-panchal mahesh-panchal left a comment

Choose a reason for hiding this comment

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

I would un-nest the if's but the decision is yours.

],
[
path: { "${params.outdir}/${params.aligner}/rseqc/junction_annotation/rscript" },
if ('bam_stat' in rseqc_modules) {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
if ('bam_stat' in rseqc_modules) {
if (!params.skip_rseqc && 'bam_stat' in rseqc_modules) {

Perhaps combine this with above? I prefer anything we can do to get rid of these nested if's.
Also I'm realizing it's harder to review, because it's easy to mistake which level of nesting you're in.

Copy link
Member Author

Choose a reason for hiding this comment

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

Changed in 3016c0b

Can you double-check it looks good for me please?

We really need to find a way to avoid this logic duplication....I will try and speak to our very own Yoda.

Copy link
Member

Choose a reason for hiding this comment

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

The logic duplication can be avoided by a pipeline rewrite. The alternative is to use channel branching and ternary operators to select the correct input channels, along channel mixing and the when. It's not a simple change though.

But it would be nicer to still be able to put process invocations in if's. Maybe that's not what the data flow model was intended for though. 🤷🏽 Most people writing these workflows come from training using R or Python or what have you, and are not used to this data flow model.

subworkflows/nf-core/fastqc_umitools_trimgalore.nf Outdated Show resolved Hide resolved
Copy link
Member

@mahesh-panchal mahesh-panchal left a comment

Choose a reason for hiding this comment

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

LGTM.

@drpatelh drpatelh merged commit 386bda0 into nf-core:dev Feb 22, 2022
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