Tweet
Originally posted by Victory
View Post
-
Please be more verbose. What commands are you executing to install samtools after copying the SAM folder. You may have to get your cluster administrator to install samtools cluster-wide. I typically have a local install directory that is included in my PATH environmental variable. -
I use the import command to make BAM file.
samtools import <in.ref_list> <in.sam> <out.bam>
Do I have to use specific command to install the SAM program or just put the program folder on the directory?Comment
-
You have to copy the binary to an directory where *other* binaries are installed (like /usr/local/bin). You have to make sure that your PATH environment variable includes the above path. Then you can just "samtools" instead of the "/home/<ETC>/samtools"Originally posted by Victory View PostComment
-
Thank you. I will try that.Comment
-
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
-
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...
Comment