Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Magnus
    Junior Member
    • Nov 2009
    • 5

    Memory problems with MosaikAligner 1.0.1307 (removed -km and -pm)

    Hi

    There was an option in "old" MosaikAligner to load the keys-file, and/or positions-file into the memory by using "-km" and "-pm" from a reference jump database. I was never able to load both into memory due to lack of sufficient RAM, (loaded just the keys-file). This features are now removed in "new" MosaikAligner, and I am not able to aligne with my new jump-database.

    Are there any tricks besides upgrading the hardware to get around this problem?

    Error message:
    Code:
    ------------------------------------------------------------------------------
    MosaikAligner 1.0.1307                                              2009-10-14
    Michael Stromberg & Wan-Ping Lee  Marth Lab, Boston College Biology Department
    ------------------------------------------------------------------------------
    
    - Using the following alignment algorithm: all positions
    - Using the following alignment mode: aligning reads to all possible locations
    - Using a maximum mismatch threshold of 6
    - Using a hash size of 15
    - Aligning in colorspace (SOLiD)
    - Using 4 processors
    - Using an alignment candidate threshold of 25bp.
    - Setting hash position threshold to 100
    - Using a jump database for hashing. Storing keys & positions in memory.
    - loading basespace reference sequences... finished.
    terminate called after throwing an instance of 'std::bad_alloc'
      what():  std::bad_alloc
    Aborted
    Server:
    Linux 2.6.25-gentoo-r7 #1 SMP x86_64 Intel(R) Xeon(R) CPU E5440 @ 2.83GHz GenuineIntel GNU/Linux
    cat /proc/meminfo gives "MemTotal: 16430836 kB"
    cat /proc/cpuinfo gives "8 times Intel(R) Xeon(R) CPU E5440 @ 2.83GHz"

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
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
19 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...