Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • quokka
    Member
    • Apr 2010
    • 19

    megahit failing without an error message in (x)ubuntu virtual machine

    Hi.

    I can get megahit (v1.1) to work as expected (either by compiling it myself or using precompiled binaries) on our cluster with CentOS (6.8).

    The same version of megahit initially appears to run on Ubuntu (14.04) but no contigs are assembled and there are no errors displayed. The command I am using for testing purposes is:

    Code:
    megahit -t 1 -m 1000000000 --verbose -r /home/input/readsInterleaved3.fa -o /home/output/assembly
    On Ubuntu, the screen only displays:

    Code:
    MEGAHIT v1.1.1
    --- [Wed Jan 18 15:32:08 2017] Start assembly. Number of CPU threads 1 ---
    --- [Wed Jan 18 15:32:08 2017] Available memory: 2099187712, used: 1000000000
    ..and the resulting assembly folder is empty.

    If I execute the same command line instructions as above on Centos (on our cluster) the screen displays:

    Code:
    MEGAHIT v1.1.1
    --- [Wed Jan 18 15:45:15 2017] Start assembly. Number of CPU threads 1 ---
    --- [Wed Jan 18 15:45:15 2017] Available memory: 126861316096, used: 1000000000
    --- [Wed Jan 18 15:45:15 2017] Converting reads to binaries ---
    ...and lots more output as the program correctly executes and assembles the contigs.


    I'm guessing that perhaps megahit is coded to abort if there is not a minimum amount of memory available on the machine??

    Usually I like to construct pipelines etc on my small virtual machine before porting them over to the cluster, hence my attempts to get them to work on this low memory machine.

    Have I come to the correct conclusion or is there some other possibility (and associated fix) that exists?
    Last edited by quokka; 01-17-2017, 11:11 PM.

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