Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • GenoMax
    Senior Member
    • Feb 2008
    • 7142

    Samtools problem on a "rocks" cluster

    I am having some problems getting samtools to run on a machine that is part of a rocks (v. 4.3) cluster (it happens to be the head-node which has 16GB RAM).

    Even if I use the pre-compiled binary available from the samtools site (or compile samtools locally from source) I am getting a segmentation fault running samtools ("import"). The job is *not* being submitted to cluster queue. I want to make sure samtools actually runs and completes a job on this OS.

    Has anyone else ran into this before?

    BTW: How may of you are using "rocks" based cluster(s) for processing/analyzing next gen sequence data?

    -- Hemant
  • jnfass
    Member
    • Aug 2008
    • 88

    #2
    I often use maq or bwa on a rocks cluster, but haven't used samtools yet. But if the job is not being submitted to the queue, then how do you know that samtools is segfaulting? Some examples of commands, output, your shell script you're submitting to the queue, etc, would be helpful ...

    Comment

    • GenoMax
      Senior Member
      • Feb 2008
      • 7142

      #3
      Originally posted by jnfass View Post
      I often use maq or bwa on a rocks cluster, but haven't used samtools yet. But if the job is not being submitted to the queue, then how do you know that samtools is segfaulting? Some examples of commands, output, your shell script you're submitting to the queue, etc, would be helpful ...
      Let us set aside the fact that this is a cluster for a moment. I am trying to make sure the program can run successfully on the head node.

      I am logged into the head node and then run a basic --> samtools "import" database *.sam *.bam command. samtools runs for sometime (e.g. I get this: [sam_header_read2] 28203826 sequences loaded) and then the program seg faults without producing any additional error messages.

      Any ideas?

      Comment

      • jnfass
        Member
        • Aug 2008
        • 88

        #4
        sorry - seems like a straight samtools problem, unrelated to cluster usage (if you've used the command successfully on other data, you could verify that) ...

        I can't help, but I'd suggest you post the exact command, and the exact output, so others might be able to help you. Good luck!

        Comment

        • nilshomer
          Nils Homer
          • Nov 2008
          • 1283

          #5
          Originally posted by GenoMax View Post
          I am having some problems getting samtools to run on a machine that is part of a rocks (v. 4.3) cluster (it happens to be the head-node which has 16GB RAM).

          Even if I use the pre-compiled binary available from the samtools site (or compile samtools locally from source) I am getting a segmentation fault running samtools ("import"). The job is *not* being submitted to cluster queue. I want to make sure samtools actually runs and completes a job on this OS.

          Has anyone else ran into this before?

          BTW: How may of you are using "rocks" based cluster(s) for processing/analyzing next gen sequence data?

          -- Hemant
          Can you give me the command you are using? What version of rocks and zlib are you using? We have rocks 4 and 5 running with samtools.

          Comment

          • GenoMax
            Senior Member
            • Feb 2008
            • 7142

            #6
            Originally posted by nilshomer View Post
            Can you give me the command you are using? What version of rocks and zlib are you using? We have rocks 4 and 5 running with samtools.
            This is the command line:

            samtools import ~/index/hg18.fa ~/single/single_end_mod.txt.part10.sam ~/single/single_end_mod.txt.part10.bam

            Rocks v.4.3 and the stock zlib that came with 4.3 (which is 1.2.1 I think).

            Comment

            • nilshomer
              Nils Homer
              • Nov 2008
              • 1283

              #7
              Originally posted by GenoMax View Post
              This is the command line:

              samtools import ~/index/hg18.fa ~/single/single_end_mod.txt.part10.sam ~/single/single_end_mod.txt.part10.bam

              Rocks v.4.3 and the stock zlib that came with 4.3 (which is 1.2.1 I think).
              Try running
              Code:
              samtools faidx ~/index/hg18.fa
              before the import. You need to index the reference.
              Then run
              Code:
              samtools import ~/index/hg18.fa.fai ~/single/single_end_mod.txt.part10.sam ~/single/single_end_mod.txt.part10.bam
              (notice the *fa.fai instead of *fa since the argument for import is a reference list, not the reference).

              Comment

              • jfshao1984
                Junior Member
                • Mar 2008
                • 5

                #8
                samtools import <in.ref_list> <in.sam> <out.bam>
                Since 0.1.4, this command is an alias of:
                samtools view -bt <in.ref_list> -o <out.bam> <in.sam>

                so you can use "samtools view -bt" instead. Before "view" ,you should run "samtools faidx" first. I am using rocks 4.3 cluster, and have not met some problem with samtools. Good luck to you

                Comment

                • GenoMax
                  Senior Member
                  • Feb 2008
                  • 7142

                  #9
                  Thanks "nilshomer" and "jfshao1984" for pointing out the solution.

                  Comment

                  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, 07-02-2026, 11:08 AM
                  0 responses
                  25 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-30-2026, 05:37 AM
                  0 responses
                  23 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-26-2026, 11:10 AM
                  0 responses
                  23 views
                  0 reactions
                  Last Post SEQadmin2  
                  Started by SEQadmin2, 06-17-2026, 06:09 AM
                  0 responses
                  55 views
                  0 reactions
                  Last Post SEQadmin2  
                  Working...