Skip to content

segfault *after* kmer counts complete? #19

@ttriche

Description

@ttriche

So I'm under the impression that

  1. mantis needs squeakr-exact to create .ser files
  2. these .ser files can then be merged for querying and
  3. squeakr-count is now multithreaded.

But this doesn't seem to work out so good in practice:

[tim.triche@node069 single]$ THREADS=`cat /proc/cpuinfo | grep proc | wc -l` 
[tim.triche@node069 single]$ echo $THREADS 
80
[tim.triche@node069 single]$ free -h
              total        used        free      shared  buff/cache   available
Mem:           250G         10G        239G         46M        907M        238G
Swap:           11G          0B         11G

Ok looks good. Now let's take an therapy-related AML patient's ancient RNAseq data and index it:

[tim.triche@node069 single]$ squeakr-count -g -k 31 -s 31 -t $THREADS SRR621698.fastq.gz 
Reading from the fastq file and inserting in the QF
Total Time Elapsed: 184.994003seconds
Calc freq distribution: 
Total Time Elapsed: 8.228049seconds
Maximum freq: 329368
Num distinct elem: 312966013
Total num elems: 2172228383
Segmentation fault

Woops? Any ideas for debugging and unit testing are appreciated, since I'd like to scale this up for various search types. Thanks for a great tool and your support in getting it to run smoothly :-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions