Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • JMorlan
    Junior Member
    • Oct 2010
    • 4

    BEDTools coverageBed error

    Recently I have been getting the following persistent error when runnng BEDTools coverageBed (ver 2.16.2 or 2.12.0):

    /mnt/ngs/analysis/software/BEDTools-Version-2.16.2/bin/coverageBed: line 2: 32662 Killed ${0%/*}/bedtools coverage "$@"

    I suspected this is was a file format problem but one of my inputs is the product of intersectBed and the other works fine with intersectBed. I've tried dos2unix to make sure there are no extraneous characters mucking me up but that has not helped.

    I have used coverageBed successfully in the past so I tried to narrow down which input file was the culprit by swapping them out but BOTH files can be made to work as input depending on what file they are paired with!

    Any thoughts?

    JMorlan
    Last edited by JMorlan; 04-04-2014, 08:41 AM.
  • limits999
    Junior Member
    • Apr 2013
    • 2

    #2
    Hi JMorlan,

    Have you solved this problem?
    I met the similar problem, so if you have handled it, may you please provide some advice?

    Thanks!

    Ming

    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
    18 views
    0 reactions
    Last Post SEQadmin2  
    Started by SEQadmin2, 06-30-2026, 05:37 AM
    0 responses
    19 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...