Name Mode Size
.github 040000
R 040000
data-raw 040000
data 040000
inst 040000
man 040000
pkgdown 040000
src 040000
tests 040000
vignettes 040000
.BBSoptions 100644 0 kb
.Rbuildignore 100755 0 kb
.gitignore 100755 0 kb
CODE_OF_CONDUCT.md 100644 5 kb
CONTRIBUTING.md 100644 11 kb
DESCRIPTION 100644 2 kb
Dockerfile 100644 1 kb
LICENSE.md 100644 34 kb
NAMESPACE 100644 6 kb
NEWS 100755 0 kb
README.md 100755 2 kb
configure 100755 0 kb
configure.win 100755 0 kb
README.md
# FLAMES [![R build status](https://github.com/mritchielab/FLAMES/actions/workflows/check-bioc.yml/badge.svg)](https://github.com/mritchielab/FLAMES/actions) <img src="vignettes/FLAMES-01.png"> The FLAMES package provides a framework for performing single-cell and bulk read full-length analysis of mutations and splicing. FLAMES performs cell barcode and UMI assignment from nanopore reads as well as semi-supervised isoform detection and quantification. FLAMES is designed to be an easy and quick to use, powerful workflow for isoform detection and quantification, splicing analysis and mutation detection. The Bioconductor release of FLAMES can be installed with: ``` if (!require("BiocManager", quietly = TRUE)) install.packages("BiocManager") BiocManager::install("FLAMES") ``` The latest development version can be installed with: ``` if (!require("BiocManager", quietly = TRUE)) install.packages("BiocManager") BiocManager::install("OliverVoogd/FLAMES") ``` Input to FLAMES are fastq files generated from the long-read platform. Using the cell barcode annotation obtained from short-read data as the reference, the pipeline identifies and trims cell barcodes/UMI sequences from the long reads. After barcode assignment, all reads are aligned to the relevant genome to obtain a draft read alignment. The draft alignment is then polished and grouped to generate a consensus transcript assembly. All reads are aligned again using the transcript assembly as the reference and quantified. <img align='center' src="vignettes/FLAMESpipeline-01.png"> The above figure provides a high level overview of the main steps in the FLAMES pipeline. The optional arguments on the left are colour coded to associate with the specific step that they apply to. The FLAMES vignette can be found using: ``` # FLAMES must be installed browseVignettes("FLAMES") ```