Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cmccabe
    Senior Member
    • Jul 2012
    • 355

    bedtools error

    I am getting the below error using bedtoold 2.20. The files are too large to attach. Thank you.

    Code:
     dnascopev@ubuntu:~$ cd "/media/9C168A3F168A1A82"
    
    dnascopev@ubuntu:/media/9C168A3F168A1A82$ coverageBed -hist -abam IonXpress_001.bam -b LCH_IDT.bed | grep ^all > output.txt
    Unexpected file format.  Please use tab-delimited BED, GFF, or VCF. Perhaps you have non-integer starts or ends at line 1?
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    What're the first couple lines of LCH_IDT.bed?

    Comment

    • cmccabe
      Senior Member
      • Jul 2012
      • 355

      #3
      There are 15 lines in that file sorted: The first 3 lines are below. Thanks.

      chr12 112884064 112884217
      chr12 112888106 112888331
      chr12 112890983 112891206

      Comment

      • dpryan
        Devon Ryan
        • Jul 2011
        • 3478

        #4
        The most common cause of this is either not using unix line endings (i.e., using \r) or having an extraneous space after a tab. The simplest thing is to just look at the bed file in a hex editor. You could also just "od -c LCH_IDT.bed" if you don't have a hex editor handy. A tab will show up as "\t" and a proper like ending will be "\n". Aside from those you should only see regular characters.

        Comment

        • cmccabe
          Senior Member
          • Jul 2012
          • 355

          #5
          Thank you, that was it... I seem to do that a lot, I guess I need to use Linux more and Windows less .

          Comment

          • dariober
            Senior Member
            • May 2010
            • 311

            #6
            For the record... To quickly visualize non-printable characters you could use
            Code:
            cat -vet
            . What you want to see is that tab characters are marked by ^I and line endings by $. If lines end in ^M$ you have windows line endings "carriage return + line feed". E.g.:

            Code:
            cat -vet ds069_293T_GFP_2.merge_peaks.bed | head
            chr1^I713939^I714220^Ids069_293T_GFP_2.merge_peak_1^I8.91011$
            chr1^I762786^I762945^Ids069_293T_GFP_2.merge_peak_2^I6.57885$
            chr1^I805256^I805387^Ids069_293T_GFP_2.merge_peak_3^I3.11743$
            chr1^I840046^I840238^Ids069_293T_GFP_2.merge_peak_4^I3.39438$
            chr1^I856585^I856713^Ids069_293T_GFP_2.merge_peak_5^I7.55995$
            chr1^I859179^I859369^Ids069_293T_GFP_2.merge_peak_6^I13.05689$

            Comment

            • cmccabe
              Senior Member
              • Jul 2012
              • 355

              #7
              Thank you .

              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.
                Yesterday, 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, Today, 11:08 AM
              0 responses
              6 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-30-2026, 05:37 AM
              0 responses
              11 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-26-2026, 11:10 AM
              0 responses
              18 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-17-2026, 06:09 AM
              0 responses
              53 views
              0 reactions
              Last Post SEQadmin2  
              Working...