Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • lj907
    Junior Member
    • Jul 2012
    • 9

    sh: samtools: command not found (Tophat)

    Dear all,

    I have been using tophat for my RNA-seq data. The command line I'm using is the standard: ./tophat -p 8 -G /path_to_genes.gtf/ -o <output_folder> /path_to_genome_index/ XXX.fastq

    Tophat runs happily, finds bowtie and samtools, checks for bowtie index, Fasta reference, generates SAM header... all goes well and I have 4 outputs: accepted_hits.bam deletions.bam insertions.bam and junctions.bam... However, when the sam version of accepted_hits.bam is going to be written, samtools fails and I get a message saying sh:samtools: command not found...
    Having gone through with the bam files till the very end (cufflinks then cuffdiff and R), I seem to get the analysis running but I don't understand why samtools fails during the mapping.... Tophat clearly recognises it at first.. and ./samtools <options> work nicely for other applications.
    Just to add I have used samtools-0.1.17.tar.bz2 (I'm on a iMac) untar ed it and cp ed it into my working path (I haven't got permission for /usr/bin), I have also cp ed libbam.a into my working directory...
    Can anyone help me
    Cheers
    lj907
  • krobison
    Senior Member
    • Nov 2007
    • 734

    #2
    If you try the command

    which samtools

    what do you get as output?

    Comment

    • lj907
      Junior Member
      • Jul 2012
      • 9

      #3
      I have tried which samtools...the command line renews... no answer... is it not installed properly? but how come tophat initially recognizes it? Thanks very much
      Last edited by lj907; 07-31-2012, 05:23 AM.

      Comment

      • krobison
        Senior Member
        • Nov 2007
        • 734

        #4
        I don't know how tophat originally found samtools -- indeed, my guess is that it didn't and what you saw relied on linked in libraries.

        Getting no output suggests that samtools is not in your PATH environment variable. Your notes above suggest you may not have compiled it. Check that there is a samtools executable in the directory you specified & that the directory appears in the output for

        echo $PATH

        Comment

        • lj907
          Junior Member
          • Jul 2012
          • 9

          #5
          Thanks Krobison... I had originally used make to compile... I'm going to try to export the executables to $HOME/bin... and check with which samtools and echo $PATH.. hopefully this will work
          cheers

          Comment

          Latest Articles

          Collapse

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, 06-05-2026, 10:09 AM
          0 responses
          10 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-04-2026, 08:59 AM
          0 responses
          21 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-02-2026, 12:03 PM
          0 responses
          28 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-02-2026, 11:40 AM
          0 responses
          22 views
          0 reactions
          Last Post SEQadmin2  
          Working...