Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • jwfoley
    replied
    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)

    Leave a comment:


  • Hparker
    replied
    It's working in IGV! Thanks for all your help!

    Leave a comment:


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

    Leave a comment:


  • Hparker
    replied
    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

    Leave a comment:


  • GenoMax
    replied
    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?

    Leave a comment:


  • Hparker
    replied
    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.

    Leave a comment:


  • jwfoley
    replied
    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.

    Leave a comment:


  • Hparker
    replied
    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?

    Leave a comment:


  • Hparker
    replied
    It was the type=bedgraph line that was causing the problems so I deleted it..

    Leave a comment:


  • GenoMax
    replied
    Is that the last line in your file (a blank line perhaps)?

    Code:
    $ wc -l sample_CO115.bedGraph

    Leave a comment:


  • Hparker
    replied
    Because I am now getting these errors:
    Expecting at least 3 words line 1321892 of sample_CO115.bedGraph got 1

    This is quite time consuming going through all the data to find where there are gaps.. is there a way of doing this in unix?

    Thanks a lot for your help!

    Leave a comment:


  • GenoMax
    replied
    You can edit manually (TextEdit or TextWrangler on Mac).

    Leave a comment:


  • Hparker
    replied
    Ah great! Can you edit it manually? Or is there code?

    Leave a comment:


  • GenoMax
    replied
    Originally posted by Hparker View Post
    type=bedGraphchr7 12784 12784 100
    chr7 12948 12948 100
    chr7 12962 12962 0
    chr7 13071 13071 100
    chr7 13107 13107 100
    chr7 13119 13119 100
    chr7 19750 19750 50
    chr7 19751 19751 100
    chr7 19771 19771 50
    chr7 19772 19772 0

    It appears to have type=bedGraph at the beginning of the file?
    Right but it has to be on a separate line by itself.

    Edit so the file has a return:

    Code:
    type=bedGraph
    chr7	12784	12784	100
    chr7	12948	12948	100

    Leave a comment:


  • Hparker
    replied
    type=bedGraphchr7 12784 12784 100
    chr7 12948 12948 100
    chr7 12962 12962 0
    chr7 13071 13071 100
    chr7 13107 13107 100
    chr7 13119 13119 100
    chr7 19750 19750 50
    chr7 19751 19751 100
    chr7 19771 19771 50
    chr7 19772 19772 0

    It appears to have type=bedGraph at the beginning of the file?

    Leave a comment:

Latest Articles

Collapse

  • SEQadmin2
    Multiomic Liquid Biopsy: What DNA/RNA Panels Reveal That DNA Alone Can’t
    by SEQadmin2



    Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?

    Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating
    ...
    10-14-2026, 09:55 AM
  • SEQadmin2
    New Genomics Technologies Take Aim at Long-Standing Limits
    by SEQadmin2


    Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.

    We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing
    ...
    09-28-2026, 10:25 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by SEQadmin2, 10-22-2026, 11:13 AM
0 responses
60 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-22-2026, 10:48 AM
0 responses
42 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-15-2026, 10:52 AM
0 responses
75 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 10-14-2026, 05:39 AM
0 responses
74 views
0 reactions
Last Post SEQadmin2  
Working...