FU Logo
  • Startseite
  • Kontakt
  • Impressum
  • Home
  • Listenauswahl
  • Anleitungen

[Seqan-dev] razers3 memory problem

<-- thread -->
<-- date -->
  • From: Matthias Lienhard <lienhard@molgen.mpg.de>
  • To: SeqAn Development <seqan-dev@lists.fu-berlin.de>
  • Date: Wed, 05 Jun 2013 11:44:07 +0200
  • Reply-to: SeqAn Development <seqan-dev@lists.fu-berlin.de>
  • Subject: [Seqan-dev] razers3 memory problem

Hi,
when runnig razers3 on my paired end HiSeq fastq files I get the following errors


razers3 -i 94 -rr 95 -tc 20 -o sample.sam reads1.fastq reads2.fastq
terminate called recursively
terminate called recursively
Aborted

or

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted

It seems as memory usage is very high (>50gb). Each of the fastq files is about 7 gb. When I take the first 100000 reads, the razers3 seems to work fine. However, I don't want to split the files in small chucks and merge them together afterwards (because of disk usage and convenience - I have about 50 samples to process)
Is there another way to handle this issue?

Also, it would be very convienient if gzipped fastq files could be used as input directly - and output in bam-format would be nice as well.

Best wishes, Matthias



<-- thread -->
<-- date -->
  • Follow-Ups:
    • Re: [Seqan-dev] razers3 memory problem
      • From: "Weese, David" <weese@campus.fu-berlin.de>
  • seqan-dev - June 2013 - Archives indexes sorted by:
    [ thread ] [ subject ] [ author ] [ date ]
  • Complete archive of the seqan-dev mailing list
  • More info on this list...

Hilfe

  • FAQ
  • Dienstbeschreibung
  • ZEDAT Beratung
  • postmaster@lists.fu-berlin.de

Service-Navigation

  • Startseite
  • Listenauswahl

Einrichtung Mailingliste

  • ZEDAT-Portal
  • Mailinglisten Portal