Why chip-seq is strand specific?
2
1
Entering edit mode
8.1 years ago
bxia ▴ 180

Why chip-seq is strand specific?

The antibody will bind to double strand DNA, right?

ChIP-Seq • 5.2k views
ADD COMMENT
4
Entering edit mode
8.1 years ago

ChIP-seq itself is not strand specific. The reads generated when performing ChIP-seq are strand specific, which is important. The reads do not indicate the location of the TF binding or histone modification, they are at the end of the fragment that includes the TF binding position. The fact that the reads on the two strands should be seperated by ~ the average fragment size of your library is an important quality check for the data.

ADD COMMENT
0
Entering edit mode

How do you reconcile this answer with Devon's?

ADD REPLY
1
Entering edit mode

RNA-seq can be "stranded" because one strand is transcribed into an mRNA. This is interesting because there are cases where a protein coding gene can be transcribe from one strand, and a non-coding RNA can be transcribed from the opposite strand. Chip-seq doesn't really work that way. You are just looking for the location of a TF binding event or Histone modification. The TF binds to a fragment of double stranded DNA. The first ~50 bases of both strands are sequenced, leading to reads that are separated by the size of the original double strand fragment. While you will not be able to deduce from these reads weather the TF binds primarily to one strand or both. You can use the distance between the reads as a quality measure. See the work of Anshul Kundaje - https://sites.google.com/site/anshulkundaje/projects/idr - "It is important to check the cross-correlation plot that is produced by SPP to make sure the estimated fragment length is appropriate."

ADD REPLY
1
Entering edit mode
8.1 years ago
  1. It's generally not strand specific.
  2. The antibody doesn't bind DNA, it binds a protein that binds DNA. Of course, the protein is typically binding to both strands of DNA (often one of the grooves), which goes back to point 1.
ADD COMMENT

Login before adding your answer.

Traffic: 3065 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6