-
Notifications
You must be signed in to change notification settings - Fork 4
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
Simplify handling of motif files #6
Conversation
|
08b52b0
to
3409689
Compare
Requires #5 to be merged first |
I updated the Currently |
Yes, that's the way to go |
subworkflows/local/fimo.nf
Outdated
|
||
FILTER_MOTIFS(JASPAR_MAPPING.out.jaspar_ids, JASPAR_DOWNLOAD.out.motifs) | ||
JASPAR_MAPPING(tf_ranking, motifs_meme) | ||
FILTER_MOTIFS(JASPAR_MAPPING.out.jaspar_ids, motifs_meme) |
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.
JASPAR_MAPPING
and FILTER_MOTIFS
aim to keep only the motifs for transcription factors found significant by the pipeline. Splitting this into two processes made sense in the original implementation with a dedicated download from JASPAR, but now this should be done in a single process.
This PR adds a new subworkflow
MOTIFS
which handles the conversion of several input formats into the formats needed by the pipeline. If no motif file is provided to the pipeline, it can fetch motifs fromJASPAR
based on thetaxon_id
. It also performs the motif filtering that was part of thePEAKS
subworkflow earlier.The outputs of this subworkflow can also be used to simplify the
FIMO
subworkflow.