scvelo
RNA velocity analysis with scVelo. Estimate cell state transitions from unspliced/spliced mRNA dynamics, infer trajectory directions, compute latent time, and identify driver genes in single-cell RNA-seq data. Complements Scanpy/scVI-tools for trajectory inference.
Author
Category
Development ToolsInstall
Hot:23
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=k-dense-ai-skills-scvelo&locale=en&source=copy
scvelo — RNA Velocity Analysis
Overview of Skills
scvelo is a Python tool for analyzing single-cell RNA-seq data. By modeling mRNA splicing kinetics, it infers cell-state transition trajectories, predicts differentiation directions, and identifies driver genes. It can reconstruct developmental trajectories without requiring time-series data.
Use Cases
Core Functions
FAQs
What data format does scvelo require?
scvelo requires an AnnData object containing two layers: unspliced and spliced. These data can be generated using STARsolo, the kallisto|bustools lamanno mode, the velocyto CLI, or alevin-fry. Ensure that adata.layers['spliced'] and adata.layers['unspliced'] are present, and that obsm includes UMAP coordinates for visualization.
What is the difference between the stochastic and dynamical models?
The stochastic model is fast and suitable for exploratory analysis of large datasets. The dynamical model fits complete splicing kinetics with higher accuracy; it can identify driver genes and compute latent time, but it is computationally intensive (about 10–30 minutes for ~10,000 cells). It is recommended to start with stochastic for exploration, and use dynamical for publication.
How do I interpret the RNA velocity arrow plot?
Arrow direction indicates the cell’s expected future state, and arrow length indicates the rate of change. Healthy data should show coherent flow patterns, with arrows following known biological routes (e.g., from stem cells to differentiated cells). Random or chaotic arrows may indicate data quality issues or inappropriate parameters; check the unspliced read coverage and the n_neighbors setting.