-
Notifications
You must be signed in to change notification settings - Fork 26
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
Make the gene essentiality usage more user friendly #194
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.
Some minor comments on the formatting/typos. I am not familiar with the functionality itself, so if you want an opinion there, you should get an additional review from someone else.
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Co-authored-by: Jasmin Frangenberg <[email protected]>
Hi @jasmezz I think regarding functionality it was more or less demanded to be like this by the users of the pipeline :) |
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.
Ok then I'll approve from what I understand ;) Hint (if you want to accept my last docs suggestion), you can add [skip ci]
to your commit message which prevents GHA from triggering the CI tests. Because it is only a tiny usage docs update, it is legitimate to bypass re-running all functional checks if you want.
[skip ci] Co-authored-by: Jasmin Frangenberg <[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.
Hi! sorry for reviewing a merged PR, but I am leaving 2 comments which should be fixed in another PR 🙂
|
||
if(params.mle && params.bagel2) { | ||
ch_venndiagram = BAGEL2_PR.out.pr.join(MAGECK_MLE.out.gene_summary) | ||
VENNDIAGRAM(ch_venndiagram) |
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.
The versions of VENNDIAGRAM
are missing
path 'query.txt', emit: query | ||
|
||
script: | ||
template 'collect_gene_ids.py' |
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.
Where is this script?
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 think this module is not used
Hi!
I here modified the documentation and the way 4 modules (RRA, MLE, Drugz and Bagel2) are called in the workflow. The user now needs to only specify a contrast file and any of the modules (ie
--rra
,--mle,
--drugz
,--bagel2
) to get the module running.One of the modules was also not working properly (only running once) because I hadn't set the channels properly (with .first() at the end did the trick)