-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add limma for rnaseq #286
Add limma for rnaseq #286
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think this should be done via the nf-core module you started work on at nf-core/modules#6753, see my comments there.
To re-iterate, I think a separate Limma Voom module is probably the way to go, and in the first instance it should implement the 'standard' Limma Voom pathway without additional custom code.
Also, you have Git problems to resolve. Actually this is probably because we need to do the template update. I'll try to get to that soon
@pinin4fjords could you give more details about your comment: |
test_affy will be fine :-) |
If you have a look at the PNG of the revised subway map, there are a number of problems:
|
Well regarding the pipeline map @pinin4fjords and @maxulysse. This is what is currently on dev and master: If I understand correctly you expect that diagram to be improved. Can we create issue to adres the problem which is present in current version of the pipeline? I will take care of that during upcoming hackathon. EDIT: Well please ignore this one - I've used different tool to edit SVG than Inkscape and it all fall apart. It should be fixed now. (Still not sure why but in gtihub svg viewer the issues which you mentioned persist. |
dev_report.zip Limma results files are exactly the same and I didn't noticed any difference in html report. |
Well please ignore this one - I've used different tool to edit SVG than Inkscape and it all fall apart. It should be fixed now. (Still not sure why but in gtihub svg viewer the issues which you mentioned persist. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good- much simpler now, thank you. Last piece is to add something to the usage documentation.
@pinin4fjords I've added small additions to point that limma is available now with rnaseq data. I didn't elaborated heavily as we don't do that in case of deseq2. I wanted to be consistent. |
@nf-core-bot fix linting |
…labundance into add_limma_for_rnaseq
@nf-core-bot fix linting |
Co-authored-by: Jonathan Manning <[email protected]>
Co-authored-by: Jonathan Manning <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks- looking good now!
This pR aims to add limma suport for rnaseq data with two modes pairwise and mixed model. Currently pairwise mode is integrated and mixed model is still in progress.
PR checklist
nf-core lint
).nf-test test main.nf.test -profile test,docker
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).