Skip to content
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

Spike ins normalization #321

Open
EmanuelSoda opened this issue Oct 28, 2022 · 12 comments
Open

Spike ins normalization #321

EmanuelSoda opened this issue Oct 28, 2022 · 12 comments
Milestone

Comments

@EmanuelSoda
Copy link

Description of feature

Hi nf-core team,
first of all thanks for the amazing work!
I was wondering if the pipeline already takes in consideration the spike ins and in that case how to use it.
If this function in not implemented yet, it is possible to implement it?

Thanks in advance

Emanuel

@EmanuelSoda EmanuelSoda changed the title Spike ins normalizzation Spike ins normalization Oct 28, 2022
@cjfields
Copy link

cjfields commented Jul 6, 2023

This would be great to add as I've seen spike-ins being used in a few ChIP-Seq projects. I believe the only place spike-in normalization is included is with the bigWig file however, @EmanuelSoda is that your experience as well?

@EmanuelSoda
Copy link
Author

Hi,
As far as I know it is also possible to normalize in some way the bam files in order to obtain a more reliable quantification afterwards. But I am not sure how.

@chlazaris
Copy link

Spike-in normalization would be a very useful addition. @nservant has written a Nextflow pipeline which provides this feature in addition to others (https://github.com/bioinfo-pf-curie/ChIP-seq). I am testing it at the moment but it would be really useful to have the official nf-core ChIP-seq pipeline support this option.

@cjfields
Copy link

cjfields commented Jul 11, 2023

@chlazaris would it make sense to combine efforts here? It seems like there is considerable overlap, but the workflow from @nservant seems to tick a few more requests like spike-in norm and IDR, and nf-core has other options the above workflow is missing.

@chlazaris
Copy link

Hello @cjfields, this is what I see too. We should probably have a Zoom call to see what the best options are. My time zone is EDT. What is the best way to reach you? Thanks

@cjfields
Copy link

@chlazaris it should be a call that involves the key nf-core devs who have been working on this, for example @JoseEspinosa or @drpatelh . Maybe this is a conversation that could happen on the nf-core Slack channel initially to organize something?

@chlazaris
Copy link

@cjfields this is a good idea. Please, feel free to start the discussion there but include @nservant in addition to @JoseEspinosa and @drpatelh, as he was the one who developed the version with spike-in normalization and IDR. Thank you!

@cjfields
Copy link

Just a small note, there are different methods for spike-in norm that should be considered, for example:

https://github.com/hbctraining/Intro-to-ChIPseq-flipped/blob/main/lessons/spikeIn_normalization.md

@ahepperla
Copy link

Hi all, just commenting in support of adding spike-in normalization similar to nf-core/cutandrun. It's an invaluable technique for ChIP-seq

@nservant
Copy link

Hi guys, sorry for the delay. Happy to further discuss if needed

@chlazaris
Copy link

Hello @nservant and everyone else interested in spike-in normalization. Since, you have already worked on a version of the ChIP-seq pipeline with spike-ins @nservant, I am wondering what could be done to incorporate the spike-in normalization feature to the official nf-core pipeline, as the broader community would benefit a lot from this. There is an active thread on the nf-core Slack workspace. @cjfields started it and can be easily found by searching for "spike" on the #chipseq channel. Thank you and I will be happy to discuss further.

@saralinker
Copy link

Hi, it's really exciting to see that you're thinking of implementing spike-in normalization to the ChIP-seq pipeline as you've done for cutandrun. I was wondering if this is still an active endeavor?

@JoseEspinosa JoseEspinosa added this to the 2.2 milestone Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants