8000 Update RTN/TNI module by mribeirodantas · Pull Request #8500 · nf-core/modules · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update RTN/TNI module #8500

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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Update RTN/TNI module #8500

wants to merge 15 commits into from

Conversation

mribeirodantas
Copy link
Member
  • Start working on the RTN TNA module
  • Fix indentation for ECLint check
  • Update RTN package version & use Seqera Containers
  • Updates environment.yml and meta.yml
  • Add stub basic test to rtn/tna
  • Minor fixes
  • Update RTN TNI module to use new test-datasets

PR checklist

Closes #XXX

  • 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 module conventions in the contribution docs
  • If necessary, include test data in your PR.
  • Remove all TODO statements.
  • Emit the versions.yml file.
  • Follow the naming conventions.
  • Follow the parameters requirements.
  • Follow the input/output options guidelines.
  • Add a resource label
  • Use BioConda and BioContainers if possible to fulfil software requirements.
  • Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
    • For modules:
      • nf-core modules test <MODULE> --profile docker
      • nf-core modules test <MODULE> --profile singularity
      • nf-core modules test <MODULE> --profile conda
    • For subworkflows:
      • nf-core subworkflows test <SUBWORKFLOW> --profile docker
      • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
      • nf-core subworkflows test <SUBWORKFLOW> --profile conda

@mribeirodantas mribeirodantas changed the title update rtn tni Update RTN/TNI module May 18, 2025
@mribeirodantas mribeirodantas marked this pull request as draft May 18, 2025 04:30
@mribeirodantas mribeirodantas marked this pull request as ready for review May 19, 2025 20:40
Copy link
Contributor
@charles-plessy charles-plessy left a comment

Choose a reason for hiding this comment

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

Hi! I had a look at the PR and left a couple of comments…

@@ -0,0 +1,50 @@
process RTN_TNA {
debug true
Copy link
Contributor

Choose a reason for hiding this comment

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

You probably need to remove this?


input:
tuple val(meta), path(tni_object)
tuple val(meta), path(degs)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that the best practice is to give a different name such as meta2, meta3, etc. because you can't guarantee that all metadata channels will be identical.

writeLines(
c(
'"${task.process}":',
paste(' bioconductor-rtn:', rtn.version)
Copy link
Contributor

Choose a reason for hiding this comment

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

How about also outputting R's version?

def DEGs = file("${workDir}/degs.tsv")
DEGs.text = content

run("RTN_TNI") {
Copy link
Contributor

Choose a reason for hiding this comment

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

10000

You can also save the output of the rtn/tni package on https://github.com/nf-core/test-datasets/, to avoid running it twice (since it is already ran in its own test suite).

Copy link
Member

Choose a reason for hiding this comment

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

Just add config './nextflow.config next to e.g. the tags or just inside the when block next to the e.g. options

{ assert file(process.out.gsea1_plot[0][1]).exists() },
{ assert file(process.out.gsea2_object[0][1]).exists() },
{ assert file(process.out.gsea2_plot[0][1]).exists() },
{ assert file(process.out.versions[0]).exists() }
Copy link
Contributor

Choose a reason for hiding this comment

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

For this one and the other outputs that have no randomness inside, can you make stronger tests such as assert snapshot(process.out.versions).match() ?

################################################
################################################

tni_object <- readRDS('tni.rds')
Copy link
Contributor

Choose a reason for hiding this comment

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

What if tni_object has a different name?

@@ -0,0 +1,5 @@
process {
Copy link
Contributor

Choose a reason for hiding this comment

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

I do not see this file (nor nextflow.config3 being used).

Copy link
Member

Choose a reason for hiding this comment

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

Instead of using the nonstandard config{2,3,4} notation, you could instead use Mahesh's clever system of params: https://nf-co.re/docs/guidelines/components/modules#configuration-of-extargs-in-tests

Copy link
Member
@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

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

Basically what Charles said, but I gave a couple of extra suggestions to solve those points

@@ -1,5 +1,5 @@
process {
withName: RTN_TNI {
ext.args = '--tfs ENSG00000125798,ENSG00000125816'
ext.args = '--n_permutations 12'
Copy link
Member

Choose a reason for hiding this comment

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

See comment above

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.

3 participants
0