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

Dev -> Master for 1.1.0 release #86

Merged
merged 80 commits into from
Jan 23, 2023
Merged

Dev -> Master for 1.1.0 release #86

merged 80 commits into from
Jan 23, 2023

Conversation

edmundmiller
Copy link
Collaborator

No description provided.

…-skip-tools

By default fastp and falco are always skipped even without providing skip_tools options. After this change, skip_tools worked as expected i.e: --skip_tools fastp.

However there is still a problem with --trim_fastq true

No such variable: Exception evaluating property 'fastq' for nextflow.script.ChannelOut, Reason: groovy.lang.MissingPropertyException: No such property: fastq for class: groovyx.gpars.dataflow.DataflowBroadcast
 -- Check script './workflows/demultiplex.nf' at line: 155

Problematic lines

 if (trim_fastq) {
                ch_fastq_to_qc = FASTP.out.fastq
            }

This closes #82
nf-core modules update
Important! Template update for nf-core/tools v2.7.2
@edmundmiller edmundmiller added this to the v1.1.0 milestone Jan 20, 2023
@edmundmiller edmundmiller self-assigned this Jan 20, 2023
@github-actions
Copy link

github-actions bot commented Jan 20, 2023

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit bb45880

+| ✅ 154 tests passed       |+
#| ❔   1 tests were ignored |#
!| ❗   5 tests had warnings |!

❗ Test warnings:

  • nextflow_config - Config manifest.version should end in dev: '1.1.0'
  • pipeline_todos - TODO string in README.md: Add full-sized test dataset and amend the paragraph below if applicable
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required
  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your prefered methods description, e.g. add publication citation for this pipeline
  • schema_description - No description provided in schema for parameter: skip_tools

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.7.2
  • Run at 2023-01-23 21:42:07

@apeltzer
Copy link
Member

@@ -31,7 +31,7 @@ DDMMYY_SERIAL_NUMBER_FC3,/path/to/SampleSheet3.csv,3,/path/to/sequencer/output3
| `lane` | Optional lane number. When a lane number is provided, only the given lane will be demultiplexed |
| `run_dir` | Full path to the Illumina sequencer output directory or a `tar.gz` file containing the contents of said directory |

An [example samplesheet](../assets/samplesheet.csv) has been provided with the pipeline.
An [example samplesheet](../assets/inputs/flowcell_input.csv) has been provided with the pipeline.
Copy link
Member

Choose a reason for hiding this comment

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

I'd recommend to version the flowcell_input.csv

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It should always point to the correct branch when someone is viewing the docs, right?

Copy link
Member

@maxulysse maxulysse left a comment

Choose a reason for hiding this comment

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

Minor modifications needed, but looks good to me.

Would love a full sized test data, but I know it's more complicated than just asking

Copy link
Collaborator

@adamrtalbot adamrtalbot left a comment

Choose a reason for hiding this comment

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

This mostly lgtm but I've left a few comments that could be improved. I'd say not necessary for release though.

tests/functions/demultiplex.nf.test Outdated Show resolved Hide resolved
Comment on lines +119 to +140
switch (demultiplexer) {
case ['bclconvert', 'bcl2fastq']:
// SUBWORKFLOW: illumina
// Runs when "demultiplexer" is set to "bclconvert" or "bcl2fastq"
BCL_DEMULTIPLEX( ch_flowcells, demultiplexer )
ch_raw_fastq = ch_raw_fastq.mix( BCL_DEMULTIPLEX.out.fastq )
ch_multiqc_files = ch_multiqc_files.mix( BCL_DEMULTIPLEX.out.reports.map { meta, report -> return report} )
ch_multiqc_files = ch_multiqc_files.mix( BCL_DEMULTIPLEX.out.stats.map { meta, stats -> return stats } )
ch_versions = ch_versions.mix(BCL_DEMULTIPLEX.out.versions)
break
case 'bases2fastq':
// MODULE: bases2fastq
// Runs when "demultiplexer" is set to "bases2fastq"
BASES_DEMULTIPLEX ( ch_flowcells )
ch_raw_fastq = ch_raw_fastq.mix(BASES_DEMULTIPLEX.out.fastq)
// TODO: verify that this is the correct output
ch_multiqc_files = ch_multiqc_files.mix(BASES_DEMULTIPLEX.out.metrics.map { meta, metrics -> return metrics} )
ch_versions = ch_versions.mix(BASES_DEMULTIPLEX.out.versions)
break
default:
exit 1, "Unknown demultiplexer: ${demultiplexer}"
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

👌

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

😊 Much more readable than messing with ext.when IMO

Copy link
Collaborator

Choose a reason for hiding this comment

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

Agreed!

FASTP(ch_raw_fastq, [], [])
ch_multiqc_files = ch_multiqc_files.mix( FASTP.out.json.map { meta, json -> return json} )
ch_versions = ch_versions.mix(FASTP.out.versions)
if (!("fastp" in skip_tools)){
Copy link
Collaborator

Choose a reason for hiding this comment

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

"If not tool in skip_tools" is pretty convoluted, but I can't quite work out an easier way of doing it. "Unless tool in skip_tools?"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's less code to wrap this way. I think if it had the python syntax, and you could say if "fastp" not in skip_tools it might be easier to read.

@matthdsm wrote that bit.

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.

9 participants