v1.3.6 Revised Tue Sep 25 11:21:46 EDT 2018 (Release)
No problem. You can either:
If possible, attach the logs from QoRTs and run QoRTs with the "--verbose" option to maximize the debugging information.
Different aligners often use different conventions, in particular with regards to the MAPQ field which is often used to differentiate multi-mapped and uniquely-mapped reads.
QoRTs has been successfully tested on NOVOALIGN whole-exome sequencing (WES). This requires the "--DNA", "--minMAPQ 0", and "--checkForAlignmentBlocks" parameters.
The easiest way to install the QoRTs R companion package is using the R command:
> install.packages("http://hartleys.github.io/QoRTs/QoRTs_LATEST.tar.gz", repos=NULL, type="source");
You can then download the jar file utility from the latest release. The jar file utility does not need to be installed and is run directly.
Alternatively you can download QoRTs directly from the release page. Download the zip file titled "QoRTs_versionNum.zip". Unzip it and install the R package using the command:
> install.packages("QoRTs_0.3.17.tar.gz",repos=NULL, type="source");
Note: If you run into an error that looks like this:
ERROR: cannot extract package from '0.3.17.tar.gz'
Then you may be attempting to install the entire github repository archive, rather than the actual R package archive. Download the QoRTs_versionNum.zip file from the most recent release, unzip it, and use the file "QoRTs_0.3.9.tar.gz" to install the R package. Do NOT attempt to install the full repository source in R!
The java jar file does not need to be installed. It can be downloaded from the release page. Just execute it using the java command:
java -jar /path/to/jarfile/QoRTs.jar QC input.bam anno.gtf.gz /output/dir/
If, during package installation, you encounter an error like:
> Warning in install.packages("QoRTs", lib = "~/.R/library") : > 'lib = "~/.R/library"' is not writable
Then you may not have write permissions for your package directory. You can install QoRTs to a different directory using the R command:
> install.packages("http://hartleys.github.io/QoRTs/QoRTs_LATEST.tar.gz", repos=NULL, type="source", lib="path/to/package/dir");
Make sure the "path/to/package/dir" directory exists and is writable. Then you can load this local copy of QoRTs using the R command:
Many printers have trouble with very large vector drawings and may hang when you attempt to print (Adobe acrobat, for example, will usually sit forever while saying "flattening"). While QoRTs does not require any external packages to run, if the png package is installed, it will automatically rasterize the larger vector drawings when outputting to a vector format (svg or pdf) in order to make them more printable. You can install the png package using the command:
Or, if binaries for png are not be available from CRAN for your version of R (they aren't for my "testbed" R installation, for example), then you can try to install from source using the command:
> install.packages("https://cran.r-project.org/src/contrib/png_0.1-7.tar.gz", repos=NULL, type="source");
You can install these packages using the R commands:
> source("https://bioconductor.org/biocLite.R") > biocLite("edgeR") > biocLite("DESeq2")
If you see an warning that looks like this:
WARNING WARNING WARNING: SAM format check: Phred Qual > 41! You will need to set either --adjustPhredScores or --maxPhredScores in order to compute Phred quality metrics! QoRTs WILL throw an error if quality metrics are attempted!
Followed by an error that looks like this:
ERROR! ArrayIndexOutOfBoundsException caught while attempting to store quality score metrics. Most likely cause: quality score found above 41!
Then you may have a problem with your Phred score encoding. This can be caused by one of two possibilities:
(1) Certain newer Illumina platforms (reportedly) produce Phred scores in excess of 41. While not explicitly forbidden by the Phred encoding specification (such as it is), this is very uncommon at the current time. However, if a Phred score in excess of 41 is encountered then QoRTs will throw a descriptive error like the one above.
In this case, you will need to use the "--maxPhredScore" parameter, set to the maximum expected Phred score. According to one (secondhand) report, Illumina stated that the absolute maximum (as of August 2015) was 45.
(2) Certain older Illumina platforms (~1.3-1.7) used Phred+64 encoding for their phred scores. While technically SAM files should always be converted to Phred+33, QoRTs does offer optional support for reading such malformed input files. Use the "--adjustPhredScore 31" option to automatically subtract 31 from all phred scores, thus converting Phred+64 to Phred+33. Note that negative Phred scores are NOT supported by QoRTs, and they WILL throw an error. See the related wikipedia article for more information.
(As of v0.3.26) QoRTs now includes a read-count gene biotype plot. However, this plot is not included in the main battery of plots (as of v0.3.26), as it may require special preparation.
This plot can be generated using the following command:
However, for this plot to work correctly you must have included biotype information in your input GTF file fed to QoRTs. For ensembl data this should already be included, but if your annotation comes from elsewhere then you will need to add this information yourself.
The "biotype" is pulled from the GTF annotation file using the optional "gene_biotype" attribute tag. This is the tag identifier used by Ensembl in their annotations. This separates RNA transcripts into categories such as protein coding mRNAs, lncRNAs, rRNAs, and so on. Unfortunately there are dozens if not hundreds of different ways to encode this sort information for various species and institutions, and unlike many other features no common standard has yet appeared. If you need to include this sort of information, you will need to edit the annotation GTF file yourself. You only need to mark the rRNA fields yourself. Any genes that do not have a gene_biotype field will simply be assigned the "UNK" biotype, so you only need to add the biotypes that you are interested in testing.
You can even just attach the biotypes for your desired genes to the end of the GTF file simply by adding lines that include the gene ID's and the desired "biotype". These can be any genes of interest, gene types, or even ERCC spike-ins. For example, at the end of your GTF file you could append:
chr22 blah this_text 1 2 0 + . gene_id "MyGene1"; gene_biotype "GeneGroup1"; chr22 blah is_irrelevant 1 2 0 + . gene_id "MyGene2"; gene_biotype "GeneGroup1"; chr22 blah and_can_be 1 2 0 + . gene_id "MyGene3"; gene_biotype "GeneGroup1"; chr22 blah anything_but 1 2 0 + . gene_id "MyGene4"; gene_biotype "GeneGroup2"; chr22 blah exon_or_CDS 1 2 0 + . gene_id "MyGene5"; gene_biotype "GeneGroup2";
As long as the "feature" column is not equal to "exon" or "CDS", the line will be ignored by QoRTs except to assign featuretype. All the other fields will be ignored.
You do still need those gene ID's and their position info to be listed elsewhere in the GTF.
Notes on usage: This function is more flexible than most of the QoRTs plotting functions, and depending on how it is run you can compile information from numerous genes for many purposes. For example by default it should list read counts for rRNA's.
WARNING: Like all QoRTs functions, this only counts for UNIQUELY MAPPED READS. Many of the odd biotypes have MANY copies across the genome and thus few reads will uniquely map to these sections. In addition, many mappers will refuse to map reads to too many different loci, and thus even with multi mapping the rates might still be low. Ideally, in order to accurately assess rRNA quantities you might need to examine the pre-mapped reads using some other method. Hopefully this tool will be of some service in assessing the approximate relative rRNA quantities. You might also be able to infer outliers in the rRNA quantities by checking for unusually low mapping rates or unusually high multi-mapping rates.
Basic help and documentation can be found using the command:
And by checking the section in the vignette.
If you use QoRTs and find it helpful, you can cite it in your publications as:
Hartley SW, Mullikin JC. QoRTs: a comprehensive toolset for quality control and data processing of RNA-Seq experiments. BMC Bioinformatics. doi: 10.1186/s12859-015-0670-5
Truncated input: the error listed below occurs when the bam file is truncated. ============================FATALERROR============================ QoRTs encountered a FATAL ERROR. For general help, use command: java -jar path/to/jar/QoRTs.jar --man ============================FATALERROR============================ Error info: Exception in thread "main" net.sf.samtools.FileTruncatedException: Premature end of file at net.sf.samtools.util.BlockCompressedInputStream.readBlock(BlockCompressedInputStream.java:382) at net.sf.samtools.util.BlockCompressedInputStream.available(BlockCompressedInputStream.java:127) at net.sf.samtools.util.BlockCompressedInputStream.read(BlockCompressedInputStream.java:252) at java.io.DataInputStream.read(DataInputStream.java:149)
This software is "United States Government Work" under the terms of the United States Copyright Act. It was written as part of the authors' official duties for the United States Government and thus QoRT Package User Manual cannot be copyrighted. This software is freely available to the public for use without a copyright notice. Restrictions cannot be placed on its present or future use.
Although all reasonable efforts have been taken to ensure the accuracy and reliability of the software and data, the National Human Genome Research Institute (NHGRI) and the U.S. Government does not and cannot warrant the performance or results that may be obtained by using this software or data. NHGRI and the U.S. Government disclaims all warranties as to performance, merchantability or fitness for any particular purpose.
In any work or product derived from this material, proper attribution of the authors as the source of the software or data should be made, using "NHGRI Genome Technology Branch" as the citation.
NOTE: The scala package includes (internally) the sam-JDK library (sam-1.113.jar), from picard tools, which is covered under the MIT license. The MIT license and copyright information can be accessed using the command: java -jar /path/to/jarfile/QoRTs.jar --man samjdkinfo