forked from dynverse/dynverse
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME.Rmd
60 lines (45 loc) · 3.75 KB
/
README.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
---
output: github_document
---
<!-- README.md is generated from README.Rmd. Please edit that file -->
# dynverse <img src="docs/logo.png" align="right" width="156" height="156" />
**dynverse** is a collection of R packages aimed at supporting the trajectory inference (TI) community on multiple levels: end-users who want to apply TI on their dataset of interest, and developers who seek to easily quantify the performance of their TI method and compare it to other TI methods.
All of these packages were developed as part of a benchmarking study available on [bioRxiv](https://doi.org/10.1101/276907). All source code has been made available [here](https://github.com/dynverse/dynalysis).
Wouter Saelens\*, Robrecht Cannoodt\*, Helena Todorov, Yvan Saeys. “A comparison of single-cell trajectory inference methods: towards more accurate and robust tools”. bioRxiv (Mar. 2018). DOI: [10.1101/276907](https://doi.org/10.1101/276907).
\*: Equal contribution
## End-users
The **[dyno](https://github.com/dynverse/dyno)** package offers **end-users** a complete TI pipeline. It features:
* a uniform interface to `r nrow(dynmethods::methods)` [TI methods](https://github.com/dynverse/dynmethods#list-of-included-methods),
* an [interactive guideline tool](https://github.com/dynverse/dyno#selecting-the-most-optimal-ti-methods) to help the user select the most appropriate method,
* the [interpretation and visualisation of trajectories](https://github.com/dynverse/dyno#plotting-the-trajectory), including colouring by gene expression or clusters, and
* downstream analyses such as the [identification of potential marker genes](https://github.com/dynverse/dyno#plotting-relevant-features).
## Developers
For developers of existing or new TI methods, **dyno** offers the same features as to end-users. In addition, developers might also want to check out the following packages:
* **[dynmethods](https://github.com/dynverse/dynmethods)**, which is a repository of wrappers for TI methods. If your method has already been included in dynmethods, an [issue](https://github.com/dynverse/dynmethods/issues) will have been created there.
* **[dynwrap](https://github.com/dynverse/dynwrap)**, the wrapping functions for transforming common trajectory data formats into the common trajectory model supported by dynverse.
* **[dyneval](https://github.com/dynverse/dyneval)**, the metrics for evaluating and comparing trajectories.
* **[dynalysis](https://github.com/dynverse/dynalysis)**, all source code in order to replicate the benchmarking study by Saelens and Cannoodt ([10.1101/276907](https://doi.org/10.1101/276907)).
## Overview
dynverse consists of several subpackages:
```{r, echo = FALSE, warning=FALSE, error=FALSE, message = FALSE}
library(tidyverse)
df <- tribble(
~Repo, ~Description,
"dynalysis", "Scripts to reproduce manuscript",
"dynwrap", "Common trajectory wrapping functionality",
"dynmethods", "Wrappers for trajectory inference methods",
"dyneval", "Metrics and evaluation pipeline",
"dyngen", "Generator of synthetic datasets",
"dynnormaliser", "Common normalisation functionality",
"dyntoy", "Quick generator of small toy datasets",
"dynplot", "Common visualisation functionality",
"dynutils", "Various common functions"
) %>%
mutate(
Package = glue::glue("[{Repo}](https://github.com/dynverse/{Repo})"),
Status = ifelse(!Repo %in% c("dynalysis"), glue::glue("[](https://travis-ci.org/dynverse/{Repo})"), "Coming soon"),
`Code coverage` = ifelse(!Repo %in% c("dynalysis"), glue::glue("[](https://codecov.io/gh/dynverse/{Repo})"), "")
) %>%
select(Package, Status, `Code coverage`, Description)
knitr::kable(df)
```