8000 stringtie subworkflow and gffcompare by karlaarz · Pull Request #85 · nf-core/lncpipe · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

stringtie subworkflow and gffcompare #85

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

Merged
merged 24 commits into from
Mar 28, 2025
Merged

stringtie subworkflow and gffcompare #85

merged 24 commits into from
Mar 28, 2025

Conversation

karlaarz
Copy link

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/lncpipe branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core pipelines lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • 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).

@Emeerdink
Copy link

Looks good to me but can't be tested yet, Do we keep this open until it can be tested? I guess it won't pass anyway

@ctuni ctuni self-requested a review March 26, 2025 19:54
@ctuni
Copy link
ctuni commented Mar 27, 2025

Tests pass but the subworkflow is not being called... I'll check why

@ctuni
Copy link
ctuni commented Mar 27, 2025

How do feel @karlaarz @Emeerdink about adding featurecounts after the stringtie merge step? That way we can quantify the types of transcripts we capture

@karlaarz
Copy link
Author

yes, it is a good idea. I can add both htseq and featurecounts modules.

@Emeerdink
Copy link

Would you do this before the GFFcompare steps There are many filtering and merging steps that happen in the old pipeline before counting. What are your thoughts on that?

@karlaarz
Copy link
Author

yes, it can be added before or after gffcompare as in any case the input should be stringtie's output. I would suggest to add it after gffcompare now that all the checks of these modules have passed. What do you think?

@ctuni
Copy link
ctuni commented Mar 27, 2025

Beware! Checks are passing but the stringtie+gffcompare modules are not being run, and I'm still trying to troubleshoot why

@Emeerdink
Copy link

Ah sorry, my bad, I would add the counting after the gffcompare and all the filtering of the annotation files. This is what happens in the current pipeline (counting all the way at the end). in this paper, they do the counting directly after the merging of annotations and the filtering of the lncRNA annotations is done in a separate track. We can consider this as an update of the pipeline.

@ctuni
Copy link
ctuni commented Mar 27, 2025

Oooookey, the tests are passing and the stringtie and gffcompare modules are being correctly executed 🥳

The changes needed for the modules to run were purely structural: some channel factories needed to be changed.

I would now merge this PR, since the scope and changes are big and substantial.

I would also add htseqcount and featurecounts, but would do it on another separate PR.

@Emeerdink Emeerdink merged commit 6d9c06e into nf-core:dev Mar 28, 2025
7 checks passed
@karlaarz
Copy link
Author

@ctuni @Emeerdink I can work on the htseq and featurecounts modules later on today/tomorrow considering this paper

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