The input should be a bam format file, with reads aligned using minimap2 against the transcriptome. That is, oarfish does not currently handle spliced alignment to the genome. Further, the output alignments should be name sorted (the default order produced by minimap2 should be fine). Specifically, oarfish relies on the existence of the AS tag in the bam records that encodes the alignment score in order to obtain the score for each alignment (which is used in probabilistic read assignment), and the score of the best alignment, overall, for each read.
The --output option passed to oarfish corresponds to a directory (that will be created if it doesn't exist), under which the relevant output files will be placed.
-The output of oarfish constist of 2 files:
The --output option passed to oarfish corresponds to a path prefix (this prefix can contain the path separator character and if it refers to a directory that does not yeat exist, that directory will be created). Based on this path prefix, say P, oarfish will create 2 files:
info.json - a JSON format file containing information about relevant parameters with which oarfish was run, and other relevant inforamtion from the processed sample apart from the actual transcript quantifications.quant.tsv - a tab separated file listing the quantified targets, as well as information about their length and other metadata. The num_reads column provides the estimate of the number of reads originating from each target.P.meta_info.json - a JSON format file containing information about relevant parameters with which oarfish was run, and other relevant inforamtion from the processed sample apart from the actual transcript quantifications.P.quant - a tab separated file listing the quantified targets, as well as information about their length and other metadata. The num_reads column provides the estimate of the number of reads originating from each target.oarfish is a program, written in rust, for quantifying transcript-level expression from long-read (i.e. Oxford nanopore cDNA and direct RNA and PacBio) sequencing technologies. oarfish requires a sample of sequencing reads aligned to the transcriptome (currntly not to the genome). It handles multi-mapping reads through the use of probabilistic allocation via an expectation-maximization (EM) algorithm.
It optionally employs many filters to help discard alignments that may reduce quantification accuracy. Currently, the set of filters applied in oarfish are directly derived from the NanoCount1 tool; both the filters that exist, and the way their values are set (with the exception of the --three-prime-clip filter, which is not set by default in oarfish but is in NanoCount).
Additionally, oarfish provides options to make use of coverage profiles derived from the aligned reads to improve quantification accuracy. The use of this coverage model is enabled with the --model-coverage flag.
The usage can be provided by passing -h at the command line.
accurate transcript quantification from long-read RNA-seq data\n\nUsage: oarfish [OPTIONS] --alignments <ALIGNMENTS> --output <OUTPUT>\n\nOptions:\n --quiet be quiet (i.e. don't output log messages that aren't at least warnings)\n --verbose be verbose (i.e. output all non-developer logging messages)\n -a, --alignments <ALIGNMENTS> path to the file containing the input alignments\n -o, --output <OUTPUT> location where output quantification file should be written\n -t, --threads <THREADS> maximum number of cores that the oarfish can use to obtain binomial probability [default: 1]\n -h, --help Print help\n -V, --version Print version\n\nfilters:\n --filter-group <FILTER_GROUP>\n [possible values: no-filters, nanocount-filters]\n -t, --three-prime-clip <THREE_PRIME_CLIP>\n maximum allowable distance of the right-most end of an alignment from the 3' transcript end [default: 4294967295]\n -f, --five-prime-clip <FIVE_PRIME_CLIP>\n maximum allowable distance of the left-most end of an alignment from the 5' transcript end [default: 4294967295]\n -s, --score-threshold <SCORE_THRESHOLD>\n fraction of the best possible alignment score that a secondary alignment must have for consideration [default: 0.95]\n -m, --min-aligned-fraction <MIN_ALIGNED_FRACTION>\n fraction of a query that must be mapped within an alignemnt to consider the alignemnt valid [default: 0.5]\n -l, --min-aligned-len <MIN_ALIGNED_LEN>\n minimum number of nucleotides in the aligned portion of a read [default: 50]\n -n, --allow-negative-strand\n allow both forward-strand and reverse-complement alignments\n\ncoverage model:\n --model-coverage apply the coverage model\n -b, --bins <BINS> number of bins to use in coverage model [default: 10]\n\nEM:\n --max-em-iter <MAX_EM_ITER>\n maximum number of iterations for which to run the EM algorithm [default: 1000]\n --convergence-thresh <CONVERGENCE_THRESH>\n maximum number of iterations for which to run the EM algorithm [default: 0.001]\n -q, --short-quant <SHORT_QUANT>\n location of short read quantification (if provided)\nThe input should be a bam format file, with reads aligned using minimap2 against the transcriptome. That is, oarfish does not currently handle spliced alignment to the genome. Further, the output alignments should be name sorted (the default order produced by minimap2 should be fine). Specifically, oarfish relies on the existence of the AS tag in the bam records that encodes the alignment score in order to obtain the score for each alignment (which is used in probabilistic read assignment), and the score of the best alignment, overall, for each read.
The --output option passed to oarfish corresponds to a directory (that will be created if it doesn't exist), under which the relevant output files will be placed. The output of oarfish constist of 2 files:
info.json - a JSON format file containing information about relevant parameters with which oarfish was run, and other relevant inforamtion from the processed sample apart from the actual transcript quantifications.quant.tsv - a tab separated file listing the quantified targets, as well as information about their length and other metadata. The num_reads column provides the estimate of the number of reads originating from each target.Josie Gleeson, Adrien Leger, Yair D J Prawer, Tracy A Lane, Paul J Harrison, Wilfried Haerty, Michael B Clark, Accurate expression quantification from nanopore direct RNA sequencing with NanoCount, Nucleic Acids Research, Volume 50, Issue 4, 28 February 2022, Page e19, https://doi.org/10.1093/nar/gkab1129 \u21a9
oarfish is a program, written in rust, for quantifying transcript-level expression from long-read (i.e. Oxford nanopore cDNA and direct RNA and PacBio) sequencing technologies. oarfish requires a sample of sequencing reads aligned to the transcriptome (currntly not to the genome). It handles multi-mapping reads through the use of probabilistic allocation via an expectation-maximization (EM) algorithm.
It optionally employs many filters to help discard alignments that may reduce quantification accuracy. Currently, the set of filters applied in oarfish are directly derived from the NanoCount1 tool; both the filters that exist, and the way their values are set (with the exception of the --three-prime-clip filter, which is not set by default in oarfish but is in NanoCount).
Additionally, oarfish provides options to make use of coverage profiles derived from the aligned reads to improve quantification accuracy. The use of this coverage model is enabled with the --model-coverage flag.
The usage can be provided by passing -h at the command line.
accurate transcript quantification from long-read RNA-seq data\n\nUsage: oarfish [OPTIONS] --alignments <ALIGNMENTS> --output <OUTPUT>\n\nOptions:\n --quiet be quiet (i.e. don't output log messages that aren't at least warnings)\n --verbose be verbose (i.e. output all non-developer logging messages)\n -a, --alignments <ALIGNMENTS> path to the file containing the input alignments\n -o, --output <OUTPUT> location where output quantification file should be written\n -t, --threads <THREADS> maximum number of cores that the oarfish can use to obtain binomial probability [default: 1]\n -h, --help Print help\n -V, --version Print version\n\nfilters:\n --filter-group <FILTER_GROUP>\n [possible values: no-filters, nanocount-filters]\n -t, --three-prime-clip <THREE_PRIME_CLIP>\n maximum allowable distance of the right-most end of an alignment from the 3' transcript end [default: 4294967295]\n -f, --five-prime-clip <FIVE_PRIME_CLIP>\n maximum allowable distance of the left-most end of an alignment from the 5' transcript end [default: 4294967295]\n -s, --score-threshold <SCORE_THRESHOLD>\n fraction of the best possible alignment score that a secondary alignment must have for consideration [default: 0.95]\n -m, --min-aligned-fraction <MIN_ALIGNED_FRACTION>\n fraction of a query that must be mapped within an alignemnt to consider the alignemnt valid [default: 0.5]\n -l, --min-aligned-len <MIN_ALIGNED_LEN>\n minimum number of nucleotides in the aligned portion of a read [default: 50]\n -n, --allow-negative-strand\n allow both forward-strand and reverse-complement alignments\n\ncoverage model:\n --model-coverage apply the coverage model\n -b, --bins <BINS> number of bins to use in coverage model [default: 10]\n\nEM:\n --max-em-iter <MAX_EM_ITER>\n maximum number of iterations for which to run the EM algorithm [default: 1000]\n --convergence-thresh <CONVERGENCE_THRESH>\n maximum number of iterations for which to run the EM algorithm [default: 0.001]\n -q, --short-quant <SHORT_QUANT>\n location of short read quantification (if provided)\nThe input should be a bam format file, with reads aligned using minimap2 against the transcriptome. That is, oarfish does not currently handle spliced alignment to the genome. Further, the output alignments should be name sorted (the default order produced by minimap2 should be fine). Specifically, oarfish relies on the existence of the AS tag in the bam records that encodes the alignment score in order to obtain the score for each alignment (which is used in probabilistic read assignment), and the score of the best alignment, overall, for each read.
The --output option passed to oarfish corresponds to a path prefix (this prefix can contain the path separator character and if it refers to a directory that does not yeat exist, that directory will be created). Based on this path prefix, say P, oarfish will create 2 files:
P.meta_info.json - a JSON format file containing information about relevant parameters with which oarfish was run, and other relevant inforamtion from the processed sample apart from the actual transcript quantifications.P.quant - a tab separated file listing the quantified targets, as well as information about their length and other metadata. The num_reads column provides the estimate of the number of reads originating from each target.Josie Gleeson, Adrien Leger, Yair D J Prawer, Tracy A Lane, Paul J Harrison, Wilfried Haerty, Michael B Clark, Accurate expression quantification from nanopore direct RNA sequencing with NanoCount, Nucleic Acids Research, Volume 50, Issue 4, 28 February 2022, Page e19, https://doi.org/10.1093/nar/gkab1129 \u21a9