8000 Update to DSL2 and add in Transcript Identification by edmundmiller · Pull Request #24 · nf-core/nascent · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update to DSL2 and add in Transcript Identification #24

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 624 commits into from
Mar 16, 2022
Merged

Update to DSL2 and add in Transcript Identification #24

merged 624 commits into from
Mar 16, 2022

Conversation

edmundmiller
Copy link
Collaborator
@edmundmiller edmundmiller commented Sep 30, 2021

From Slack:

I've committed a bit of a party foul. Last March (2020) I started converting our labs pipeline that I had originally written in snakemake to follow the nf-core standard because I was coming up with similar stuff for our snakemake pipelines and would rather work with a larger community. We'd like to add it to nf-core. Anyways, I missed the part about reaching out on slack to see if there's an duplicate work. It's a groseq pipeline, which the #nascent pipeline covers but we're using a couple of different methods.
I started on DSL2 pre-template when @hpatel first converting rnaseq. I've got it updated to the latest template last week. I would like to wrap into nascent, I'm just not sure if they're doing the same thing. Ours uses either homer in a workflow our lab created in a previous paper using Homer, or following another one called TFSEE that @venkat Malladi's group came up with that uses grohmm. #nascent seems to be just creating the bedGraphs and bigwigs
I just see that as a 3 possible pathway after you've got the reads aligned and all. homer, grohmm, or just producing graphs from the reads.
I'm not sure whether the homer/grohmm can cover proseq or cageseq etc.
What I propose doing git repowise, I think ours has more relevant history and then I can reimplement the nascent stuff if it's worth it in DSL2 really easily. We can archive the #nascent pipeline since there's been no active development on it, and then we'll give acknowledgements to the archived repo. I'd love to get others thoughts.

This should be a rebase merge, since I already took care of the big merge locally.

If we decide to merge this, things that need to be done:

sruthips 10000 uresh and others added 30 commits February 10, 2021 11:34
Can't test offline, so no working on grohmm on a flight.
Since the docker image uses an old version of dREG it still has
"peakcalling" as the script.
Danko-Lab/dREG@b3038b8
IDK if this works because it's broken on my local cluster
Gotta keep 'em seperated.
Hey!
This prevents changing the tag_dir, which should fix caching of
findPeaks and makeucscfile.
@edmundmiller edmundmiller changed the title Merge in Groseq Update to DSL2 and add in Transcript Identification Feb 28, 2022
@edmundmiller
Copy link
Collaborator Author

To be clear, this is just merging into dev. Still need to write some tests and what not, but I'd like to break those into smaller PRs

@edmundmiller edmundmiller requested review from ignaciot and magruca March 1, 2022 16:56
@edmundmiller edmundmiller self-assigned this Mar 3, 2022
@edmundmiller edmundmiller added this to the V2 milestone Mar 3, 2022
@ignaciot
Copy link
Contributor
ignaciot commented Mar 8, 2022

Hi Edmund,

Life has become increasingly busier since I first put out the nascent pipeline, and I'm having a hard time finding the time to update it after every template change. So, your plan sounds fine to me if you decide to merge this with your GRO-seq pipeline.

@drpatelh
Copy link
Member

Will merge this in for now in favour of reviewing this properly before the release.

Copy link
Member
@drpatelh drpatelh left a comment

Choose a reason for hiding this comment

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

🚀

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.

7 participants
0