Open
Conversation
Co-Authored-By: Claude Opus 4.6 <[email protected]>
|
suzannejin
changed the title
There was a problem hiding this comment.
Pull request overview
This PR implements the dual-mode configuration approach from #472 by making profiles the default (single-run) mechanism and only using paramsheets for explicit multi-run benchmarking. It updates pipeline configuration resolution, adds analysis profiles, and refactors tests/docs accordingly.
Changes:
- Switch paramset resolution to use paramsheet only when
--paramsheetis provided, otherwise run in profile (single-run) mode. - Add/restore analysis profiles (rnaseq/affy/maxquant/soft and variants) via new
conf/**.configfiles andnextflow.configprofile entries. - Update docs and tests to reflect the two-mode architecture; remove the shipped default paramsheet.
Reviewed changes
Copilot reviewed 39 out of 42 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| tests/test_soft.nf.test.snap | Snapshot updated for soft profile output paths and meta. |
| tests/test_soft.nf.test | Test now loads conf/soft/soft.config and sets explicit inputs instead of paramsheet. |
| tests/test_rnaseq_limma.nf.test | Tests now use rnaseq limma profile configs and explicit inputs (no paramsheet). |
| tests/test_rnaseq_dream.nf.test.snap | Snapshot updated for rnaseq dream output path naming and meta. |
| tests/test_rnaseq_dream.nf.test | Tests now use rnaseq dream profile configs and explicit inputs/overrides. |
| tests/test_rnaseq_deseq2.nf.test | Tests now use rnaseq DESeq2 profile configs and explicit inputs/overrides. |
| tests/test_nogtf.nf.test.snap | Snapshot updated for rnaseq “no gtf” output paths and meta. |
| tests/test_nogtf.nf.test | Test now loads conf/rnaseq/rnaseq.config and sets explicit inputs. |
| tests/test_maxquant.nf.test.snap | Snapshot updated for maxquant output paths and meta. |
| tests/test_maxquant.nf.test | Test now loads conf/maxquant/maxquant.config and sets explicit inputs. |
| tests/test_many.nf.test.snap | Snapshot updated for multi-run test paramset naming and meta. |
| tests/test_many.nf.test | Multi-run test still uses paramsheet mode but with renamed test paramsets. |
| tests/test_affy.nf.test | Tests now load affy profile configs and set explicit inputs/overrides. |
| tests/default.nf.test | “with formula” test now uses conf/test.config and explicit overrides. |
| subworkflows/local/utils_nfcore_differentialabundance_pipeline/main.nf | Paramset resolution now switches modes based on params.paramsheet; default config uses profile paramset_name. |
| nextflow_schema.json | Schema text updated to explain two-mode behavior; paramsheet default removed. |
| nextflow.config | params.paramsheet default set to null; adds analysis profiles under profiles {}. |
| docs/usage.md | Documents single-run vs multi-run modes and precedence; updates examples/profiles listing. |
| conf/testdata.yaml | Removed legacy testdata paramsets file. |
| conf/test_paramsheet.yaml | Refactored to be a self-contained test paramsheet (data/config/test blocks). |
| conf/test.config | Now includes rnaseq DESeq2+GSEA config instead of setting paramset_name directly. |
| conf/soft/soft.config | New soft analysis profile config. |
| conf/rnaseq/rnaseq_limma_gsea.config | New rnaseq limma+GSEA profile config. |
| conf/rnaseq/rnaseq_limma_gprofiler2.config | New rnaseq limma+gprofiler2 profile config. |
| conf/rnaseq/rnaseq_limma_decoupler.config | New rnaseq limma+decoupler profile config. |
| conf/rnaseq/rnaseq_limma.config | New rnaseq limma base profile config. |
| conf/rnaseq/rnaseq_dream_decoupler.config | New rnaseq dream+decoupler profile config. |
| conf/rnaseq/rnaseq_dream.config | New rnaseq dream base profile config. |
| conf/rnaseq/rnaseq_deseq2_gsea.config | New rnaseq DESeq2+GSEA profile config. |
| conf/rnaseq/rnaseq_deseq2_gprofiler2.config | New rnaseq DESeq2+gprofiler2 profile config. |
| conf/rnaseq/rnaseq.config | New rnaseq base (DESeq2 default) profile config. |
| conf/paramsheet.yaml | Removed shipped default paramsheet. |
| conf/maxquant/maxquant.config | New maxquant analysis profile config. |
| conf/affy/affy_limma_gsea.config | New affy limma+GSEA profile config. |
| conf/affy/affy_limma_gprofiler2.config | New affy limma+gprofiler2 profile config. |
| conf/affy/affy.config | New affy base profile config. |
| README.md | Updates usage guidance to analysis profiles + optional paramsheet mode. |
| CHANGELOG.md | Adds entry describing the profile-first reversion. |
Comments suppressed due to low confidence (1)
conf/test_paramsheet.yaml:184
affy_testdatapoints to a human GMT (h.all...Hs.symbols.gmt), but the derived test config setsgprofiler2_organism: "mmusculus", which overrides the GMT and queries mouse gene sets. Consider changing this tohsapiens(or omit it) so the test configuration matches the dataset species.
- paramset_name: test_affy_limma_gprofiler2
include: test_paramsheet/affy_limma_gprofiler2,test_paramsheet/affy_testdata
observations_id_col: name
observations_name_col: name
exploratory_main_variable: contrasts
differential_max_pval: 0.05
differential_max_qval: 0.05
differential_min_fold_change: 1.5
gprofiler2_organism: "mmusculus"
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| differential_min_fold_change = 1.5 | ||
|
|
||
| // gprofiler2 | ||
| gprofiler2_organism = 'mmusculus' |
There was a problem hiding this comment.
This test uses a human Hallmark GMT (h.all...Hs.symbols.gmt) but sets gprofiler2_organism = 'mmusculus', which will override the GMT and query mouse gene sets instead. Set this to hsapiens (or leave it unset to keep using the provided human GMT) to avoid silently testing the wrong species.
Suggested change
| gprofiler2_organism = 'mmusculus' | |
| gprofiler2_organism = 'hsapiens' |
Author
There was a problem hiding this comment.
@copilot create a issue to check this out (indeed the GSE50790 study uses human samples)
Co-authored-by: Copilot <[email protected]>
Member
|
@suzannejin are you happy with this? Have you reviewed the AI's work yet? |
grst
reviewed
Feb 26, 2026
Member
grst
left a comment
grst
left a comment
There was a problem hiding this comment.
The re-added profiles and docs-related changes LGTM.
I think currently the custom logic in getParamsetConfigurations() gets triggered no matter if a paramset is defined or not. I'm wondering if we could get a clearer separation of the "standard" and "custom" logic, by not even invoking that code if no paramsheet is set.
| // Use paramsheet if paramset_name is provided, otherwise use default params | ||
| def paramsets = (params.paramset_name) ? getParamsheetConfigurations() : getDefaultConfigurations() | ||
| // Use paramsheet if --paramsheet is explicitly provided, otherwise use default params (profile mode) | ||
| def paramsets = (params.paramsheet) ? getParamsheetConfigurations() : getDefaultConfigurations() |
Member
There was a problem hiding this comment.
What's the default configuration? Why do we even have to invoke getParamsetConfigurations() when no paramsheet is specified?
Author
Author
Hi @pinin4fjords , it is ready for me. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solves #472