Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • sonja
    Member
    • Aug 2010
    • 10

    ERANGE to call peaks from ChIP-Seq data

    Hello!
    I try to call peaks from a bigger data set (~6 million reads) with erange.
    Running it with the default parameters works but only results into ~7000 peaks. With my factor I expect around 20000 binding sites and I try to get 40000 to analyze in a less restrictive way.
    However I fail generating that many peaks with erange. Either I get not enough peaks or the server gets frozen! The latter happened with the following command:


    python ERANGE3.2/commoncode/findall.py er chip.rds ErangePeaks_min1_minPeak0.000001_spacing200_fold 1_shift -control mock.rds ‐minimum 1 -ratio 2 ‐minPeak 0.000001 ‐revbackground -shift 80 -spacing 200

    I set -minPeak very low to get a lot of peaks...

    Can anyone help???
  • GKM
    Member
    • May 2009
    • 45

    #2
    If letting it learn the shift value instead of specifying it to be 80 doesn't help, then 7000 is probably what you have in that library.

    Where does the number 20000 come from? Another peak caller or simply expectations?

    Comment

    • sonja
      Member
      • Aug 2010
      • 10

      #3
      Thanks for replying!
      I tried what you said and I still do not get more peaks.
      Also it doesnt matter if I put the parameter ‐minPeak to 0.00001 or to 0.01

      The 20,000 is what I get with the default options of other peak callers. And in total, this data set contains more than 100,000 clusters (this is what I can reach if I am very little restrictive).

      Does anyone have experience with this? Is there anything I could try?
      Thank you!

      Comment

      • GKM
        Member
        • May 2009
        • 45

        #4
        In general, the settings you are using are very liberal, I personally wouldn't feel comfortable working with such peak calls - in my view it's better to have a few false negatives than a lot of false positives when looking at ChIP-Seq data and "the more peaks the better" approach isn't exactly the best approach to understanding the biology of the protein.

        That said, if you don't have any high confidence prior expectation on the number of calls you should get (say you're working with something that has never been ChIP-ed before and not with NRSF or CTCF) a few things would be helpful to know:

        - How many of the peaks contain an explanatory motif (although this wouldn't help if you're not dealing with a sequence-specific transcription factor, of course). How many of the peaks you are getting with a not so conservative peak caller contain it?

        - what is the size of the genome you're working with?

        - what is your IP efficiency as calculated by ERANGE? (second to last line in the output file)

        - How many peaks do you get with more conservative settings? (-minimum 2, -ratio 3, -minimum 4 -ratio 4, etc.)

        Comment

        • sonja
          Member
          • Aug 2010
          • 10

          #5
          The reason why I need so many peaks is because I want to compare the top 500, 1000, ... , 40000 peaks of different methods in terms of %motif (fraction of peaks with motif).

          Basically I am interested in the scoring system of different methods. If there is no possibility to increase the number of peaks I have to use another method for my comparisons..

          I am working on hg18.

          The IP efficiency:
          #stats: 77936.5 RPM in 7313 regions

          I didnt try to use more conservative settings because I want to be as little restrictive as possible. As I said I want to explore the scoring system.

          BTW, may I ask who you are ? Did you help developing the program or are you a user?
          thanks!

          Comment

          Latest Articles

          Collapse

          • GATTACAT
            Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by GATTACAT
            Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
            07-01-2026, 11:43 AM
          • SEQadmin2
            Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by SEQadmin2


            I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

            Here are nine questions we think about, in roughly the order they matter, before...
            06-18-2026, 07:11 AM

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, 07-02-2026, 11:08 AM
          0 responses
          19 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-30-2026, 05:37 AM
          0 responses
          20 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          21 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-17-2026, 06:09 AM
          0 responses
          54 views
          0 reactions
          Last Post SEQadmin2  
          Working...