Seqanswers Leaderboard Ad

Collapse

Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [velvetg] segmentation fault?

    Hello,

    - I am running "velvet".
    - Velvet that I am using is the latest version.
    - After running velvetg, I've got error message "segmentation fault".
    - I think the memory is enough: I can use either 768 GB or 128 GB machine.

    The commands that I used are the below.

    make 'CATEGORIES=4'
    srun -p bigmem ./velveth OUTPUT_1 31 -fastq -shortPaired 02_L7.fastq 02_L8.fastq -fastq -shortPaired2 05_L7.fastq 05_L8.fastq -fastq -shortPaired3 08_L7.fastq 08_L8.fastq -fastq -shortPaired4 11_L7.fastq 11_L8.fastq > output1.out 2>&1 &
    556825727 sequences found
    ...
    [107491.832312] Inputting sequence 556000000 / 556825727
    [107637.486093] === Sequences loaded in 104746.688101 s
    [107637.491597] Done inputting sequences
    [107637.491604] Destroying splay table
    [107650.200950] Splay table destroyed

    srun -p bigmem -c 16 ./velvetg OUTPUT_1 -read_trkg yes -amos_file yes -unused_reads yes -exp_cov 10 -ins_length 3000 -ins_length_sd 1000 -ins_length2 6000 -ins_length_sd 1000 -ins_length3 9000 -ins_length_sd 1000 -ins_length4 11000 > output1_g.out 2>&1 &
    srun: error: node92: task 0: Segmentation fault



    I've got this error message. Would you please give me a piece of advice to resolve my problem? Thank you in advance.

  • #2
    Originally posted by syintel87 View Post
    Code:
    srun -p bigmem -c 16 ./velvetg OUTPUT_1 -read_trkg yes -amos_file yes -unused_reads yes -exp_cov 10 -ins_length 3000 -ins_length_sd 1000 -ins_length2 6000 -ins_length_sd 1000 -ins_length3 9000 -ins_length_sd 1000 -ins_length4 11000 > output1_g.out 2>&1 &
    srun: error: node92: task 0: Segmentation fault



    I've got this error message. Would you please give me a piece of advice to resolve my problem? Thank you in advance.
    Depending on the size of your files, might compiling with BIGASSEMBLY be required? Not sure if that'll solve your problem. Have you tried running the assembly with the shorter paired end libraries alone, and iteratively testing with the addition of your 6kb and then 9kb libraries.

    Not sure if your ins_length*_sd is formed correctly. It should be ins_length_sd, ins_length2_sd, ins_length3_sd, ins_length4_sd (which you omitted). I don't think this would cause your segfault though.

    Comment


    • #3
      Torsten Seemann, who contributes to the velvet project has answered this question which was addressed to the velvet mailing list:

      (Soyeon - I have replied this to the Velvet Users mailing list. That is the most appropriate place to ask these questions.)

      The most likely problem is 556825727 sequence found. That is half a billion reads. For k=31 that is a LOT OF NODES. You have probably ran out of memory.

      I see you are using srun (SLURM) on a cluster. How do you know that the velvet you compiled (on the head node?) is the one your job is using?

      You are using 4 categories. Do you have 4 separate DNA libraries that you sequenced? Or is your data just split into multiple files?

      Comment


      • #4
        Originally posted by AdrianP View Post
        Torsten Seemann, who contributes to the velvet project has answered this question which was addressed to the velvet mailing list:
        I would assume that having four different insert sizes would suggest four different libraries. I guess he didn't say how much memory his job is taking, "bigmem" is vague. Velvet's also pretty memory-hungry, other assemblers are more efficient in memory utilization. -create_binary on the later builds of velvet can bring down memory utilization somewhat, but choosing a larger K and loading less data will be helpful as well.

        One could imagine a situation where a job requests so much memory that it sits in queue forever, never quite getting enough freemem to kick off unless it's the weekend.
        Last edited by winsettz; 10-12-2013, 05:10 PM.

        Comment

        Latest Articles

        Collapse

        • seqadmin
          Exploring the Dynamics of the Tumor Microenvironment
          by seqadmin




          The complexity of cancer is clearly demonstrated in the diverse ecosystem of the tumor microenvironment (TME). The TME is made up of numerous cell types and its development begins with the changes that happen during oncogenesis. “Genomic mutations, copy number changes, epigenetic alterations, and alternative gene expression occur to varying degrees within the affected tumor cells,” explained Andrea O’Hara, Ph.D., Strategic Technical Specialist at Azenta. “As...
          07-08-2024, 03:19 PM
        • seqadmin
          Exploring Human Diversity Through Large-Scale Omics
          by seqadmin


          In 2003, researchers from the Human Genome Project (HGP) announced the most comprehensive genome to date1. Although the genome wasn’t fully completed until nearly 20 years later2, numerous large-scale projects, such as the International HapMap Project and 1000 Genomes Project, continued the HGP's work, capturing extensive variation and genomic diversity within humans. Recently, newer initiatives have significantly increased in scale and expanded beyond genomics, offering a more detailed...
          06-25-2024, 06:43 AM

        ad_right_rmr

        Collapse

        News

        Collapse

        Topics Statistics Last Post
        Started by seqadmin, 07-10-2024, 07:30 AM
        0 responses
        29 views
        0 likes
        Last Post seqadmin  
        Started by seqadmin, 07-03-2024, 09:45 AM
        0 responses
        201 views
        0 likes
        Last Post seqadmin  
        Started by seqadmin, 07-03-2024, 08:54 AM
        0 responses
        212 views
        0 likes
        Last Post seqadmin  
        Started by seqadmin, 07-02-2024, 03:00 PM
        0 responses
        193 views
        0 likes
        Last Post seqadmin  
        Working...
        X