kallisto | Near-optimal RNA-Seq quantification | Genomics library
kandi X-RAY | kallisto Summary
kandi X-RAY | kallisto Summary
kallisto is a program for quantifying abundances of transcripts from RNA-Seq data, or more generally of target sequences using high-throughput sequencing reads. It is based on the novel idea of pseudoalignment for rapidly determining the compatibility of reads with targets, without the need for alignment. On benchmarks with standard RNA-Seq data, kallisto can quantify 30 million human bulk RNA-seq reads in less than 3 minutes on a Mac desktop computer using only the read sequences and a transcriptome index that itself takes than 10 minutes to build. Pseudoalignment of reads preserves the key information needed for quantification, and kallisto is therefore not only fast, but also comparably accurate to other existing quantification tools. In fact, because the pseudoalignment procedure is robust to errors in the reads, in many benchmarks kallisto significantly outperforms existing tools. The kallisto algorithms are described in more detail in:. NL Bray, H Pimentel, P Melsted and L Pachter, Near optimal probabilistic RNA-seq quantification, Nature Biotechnology 34, p 525--527 (2016).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kallisto
kallisto Key Features
kallisto Examples and Code Snippets
Community Discussions
Trending Discussions on kallisto
QUESTION
How can I perform a try catch in nextflow?
I am currently writing a pipeline where it is possible that the bash command I am executing exits with an exitcode 1 under certain conditions. This brings my pipeline to a grinding halt. I would now like to use a try catch clause to define some alternative behavior in case this happens.
I have tried doing this in groovy fashion which does not seem to work:
...ANSWER
Answered 2021-Feb-11 at 23:29AFAIK there's no way to handle errors in your process definition using a try/catch block. Rather than trying to catch all of the scenarios that result in an exit status 1, could you better define those conditions and handle them before trying to execute your process? For example, if an empty FASTQ file (or a FASTQ file with an insufficient number of reads as required by your process) was supplied as input and this resulted in an exit status 1, a pre-processing command that filtered out those files could be useful here.
But if it's not possible to better define the condition(s) that your command produces exit status 1 or any non-zero exit status, you can ignore them like you have suggested by appending errorStrategy 'ignore'
to your process definition. Below is an example of how you could get the 'success' and 'failed' outputs, so they can be handled appropriately:
QUESTION
I'm super new to coding in general so apologies for any lack of clarity or conciseness. I'm attempting to make a build for Kallisto to use in RNA sequence alignment and I'm getting stuck at the "make" stage. The cmake was successful after a little fiddling and downloading a CXX compiler, but the make keep exiting with an error status:
...ANSWER
Answered 2020-Jun-23 at 01:15The error looks like the zlib
package was not installed in the env. Fortunately, I've recently built kallisto and can share the Conda environment I have been using, which I've tested on both osx-64 and linux-64 platforms:
kallisto-build.yaml
QUESTION
I'm using some quick R script to cbind files after performing quantification (kallisto/salmon).
The problem is, I get an R error, saying my input files aren't the same length so cbind() won't work.
This is obviously not the case, they all are 16887 lines (checked with bash wc), and it works perfectly fine in R without snakemake.
Also worth mentioning, I do get an output for a random number of sample (~ 1 to 4).
Here's the R code :
...ANSWER
Answered 2020-Apr-21 at 10:40The problem, I think, is that rule merge_quantif
is executed for each sample, i.e. 17 times, possibily in parallel. However, each run of merge_quantif
writes to the same output file (QUANTIF+"/all_sample_quantified.txt"
) since in your R script you have write.table(merge, snakemake@params[[1]], ...)
. I suspect this causes problems or at least is not an ideal setup. I suspect what you want is something like:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install kallisto
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page