Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Hparker
    Member
    • Dec 2014
    • 42

    #31
    It was the type=bedgraph line that was causing the problems so I deleted it..

    Comment

    • Hparker
      Member
      • Dec 2014
      • 42

      #32
      It seems the type=bedGraph is important in the file! So I have it at the top of my sorted bedGraph. However, when I then do the bedGraphToBigWig conversion I still get an error: Expecting at least 3 words line 1 of sample_CO115_sorted.bedGraph got 1
      How do I overcome this?

      Comment

      • jwfoley
        Senior Member
        • Jun 2009
        • 183

        #33
        Could I just suggest that every time you change your bedGraph file, you post ten lines of it and the exact command you used along with your new question? This will reduce the required back-and-forth by about two thirds from the look of things.

        So guess what we need from you to answer your most recent question.

        Comment

        • Hparker
          Member
          • Dec 2014
          • 42

          #34
          This is the first 10 lines of the (sorted) bedGraph:

          type=bedGraph
          chr1 10469 10469 100
          chr1 10471 10471 100
          chr1 10484 10484 100
          chr1 10489 10489 100
          chr1 10493 10493 100
          chr1 10497 10497 100
          chr1 10525 10525 60
          chr1 10542 10542 60
          chr1 10563 10563 60


          I use this code to convert to a bigWig:

          bedGraphToBigWig sample_CO115_sorted.bedGraph hg19.chrom.sizes CO115.bw

          I get this error:

          Expecting at least 3 words line 1 of sample_CO115_sorted.bedGraph got 1

          If I remove the type=bedGraph from the bedGraph file I get an unreadable bigWig.

          Thanks for your help.
          Last edited by Hparker; 07-05-2015, 10:57 PM.

          Comment

          • GenoMax
            Senior Member
            • Feb 2008
            • 7142

            #35
            track type=bedGraph

            is the full declaration required (word track is needed, I have edited my previous posts to reflect this). Can you try again?

            Comment

            • Hparker
              Member
              • Dec 2014
              • 42

              #36
              I have made sure the first line of the bedGraph file now reads:

              track type=bedGraph

              I no longer get the error but the bigWig file does not seem right, first few lines shown below:

              &¸èà
              X¡jµÏ0ÄÄÚ≠Òp
              T–pD)æ(úùæ¡ÎŸ†- ⁄Nh‚Ä≤ǂƂ‰
              z˚‰äöÂ(Ê≤Âҋ†5ıÂ.ÊÄjÊ[Ê
              ó5Ê7ÊY@ëå*xchr1=C€chr10õchr114 chr12˜j˙chr13VZ›chr14$fchr15@Åchr16A¥bchr17*÷chr18 @]ßchr19
              ó<Üchr2 çÌ~chr20 p±¡chr21
              ggfichr22vÿchr3ïÕ chr4d»d chr5<å»
              chr6;3

              I used this code:

              bedGraphToBigWig sample_CO115_sorted.bedGraph hg19.chrom.sizes CO115.bw

              ...and the bedGraph first 10 lines:

              track type=bedGraph
              chr1 10469 10469 100
              chr1 10471 10471 100
              chr1 10484 10484 100
              chr1 10489 10489 100
              chr1 10493 10493 100
              chr1 10497 10497 100
              chr1 10525 10525 100
              chr1 10542 10542 100
              chr1 10563 10563 100

              Comment

              • GenoMax
                Senior Member
                • Feb 2008
                • 7142

                #37
                bigWig files are an indexed binary format. You will not be able to view them in a terminal. Try the file at UCSC.

                Comment

                • Hparker
                  Member
                  • Dec 2014
                  • 42

                  #38
                  It's working in IGV! Thanks for all your help!

                  Comment

                  • jwfoley
                    Senior Member
                    • Jun 2009
                    • 183

                    #39
                    Also, based on the lines you posted, "wiggle" might be a more appropriate format than "bedGraph" for the plaintext version of your data anyway.

                    Code:
                    track type=bedGraph
                    chr1	10469	10469	100
                    chr1	10471	10471	100
                    chr1	10484	10484	100
                    chr1	10489	10489	100
                    chr1	10493	10493	100
                    chr1	10497	10497	100
                    chr1	10525	10525	100
                    chr1	10542	10542	100
                    chr1	10563	10563	100
                    is more efficiently stored as

                    Code:
                    track type=wiggle_0
                    variableStep chrom=chr1
                    10469	100
                    10471	100
                    10484	100
                    10489	100
                    10493	100
                    10497	100
                    10525	100
                    10542	100
                    10563	100
                    (assuming you meant for your values to span 1 position each instead of 0 positions each, which is how they're interpreted in bedGraph format since it's zero-based, half-open)

                    Comment

                    Latest Articles

                    Collapse

                    • SEQadmin2
                      Cancer Drug Resistance: The Lingering Barrier to Rising Survival
                      by SEQadmin2



                      Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

                      There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
                      Yesterday, 05:17 AM
                    • 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, Yesterday, 10:08 AM
                    0 responses
                    6 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 07-07-2026, 11:05 AM
                    0 responses
                    8 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 07-02-2026, 11:08 AM
                    0 responses
                    31 views
                    0 reactions
                    Last Post SEQadmin2  
                    Started by SEQadmin2, 06-30-2026, 05:37 AM
                    0 responses
                    29 views
                    0 reactions
                    Last Post SEQadmin2  
                    Working...