Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • mixter
    Member
    • May 2010
    • 22

    "R Killed" when working with large BAM files

    I'm trying to work with large BAM files produced by bowtie alignment of illumina sequencing runs. I'm able to work with them fine with tools outside of R, but R seems to have some limitations or issues with the size.

    Issue: After reading 4 bam files of 650 MB (maybe 1 million reads each) with the function readAligned("path","bamfile.bam,"BAM") from the ShortRead package, R simply terminates with the message:

    /usr/lib64/R/bin/BATCH: line 60: 10315 Killed ${R_HOME}/bin/R -f ${in} ${opts} ${R_BATCH_OPTIONS} > ${out} 2>&1

    I'm doing this on a linux-based grid engine, so it's not about the windows-specific memory limits. Also, this does not happen with small BAM files for testing. It night be about internal limits on table sizes, though?

    Any help would be greatly appreciated!
  • KevinLam
    Senior Member
    • Nov 2009
    • 204

    #2
    Hi. In lieu of other error msgs. Is it a possibility that the job timed out or was killed due to system admin set limits that are common for shared resources?
    Have u tried running just this command in a terminal?
    http://kevin-gattaca.blogspot.com/

    Comment

    • ffinkernagel
      Senior Member
      • Oct 2009
      • 110

      #3
      'Killed' is sometimes induced by running out of memory - the linux schedulder than kills processes until there is enough free memory again.

      How much swap space have you configured in addition to your RAM (and how much RAM is that)?

      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, Yesterday, 11:08 AM
      0 responses
      7 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
      20 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...