Kana comes from the Telugu word kaṇaṁ (కణం), which means ... drumroll... cell
kana is a web application for single-cell data analysis that works directly in the browser. That's right - the calculations are performed client-side, by your browser, on your computer! This differs from the usual paradigm of, e.g., Shiny applications where data needs to be sent to a backend server that does the actual analysis. Our client-side approach has a number of advantages:
If you have a Matrix Market (.mtx
) file or HDF5 (tenx V3 or AnnData
representation stored as h5ad), or SummarizedExperiment
(or derivatives like SingleCellExperiment
) stored as an RDS file, or an ExperimentHub id, you're ready to go.
genes.tsv
or features.tsv
file to identify marker genes properly.The standard analysis follows the flow described in the Orchestrating Single-Cell Analysis with Bioconductor. Briefly, this involves:
batch
column in the cell annotations, or load multiple datasets where each dataset is considered a batchThe interface provides a depiction of the dimensionality reduction of choice, a ranking of marker genes for the cluster of interest, and diagnostic plots from the individual analysis steps.
Checkout the wiki for tutorials on the functionality Kana provides.
Tips and tricks:
If you use Kana for analysis or exploration, consider citing our JOSS publication -
@article{Kana2023,
doi = {10.21105/joss.05603},
url = {https://doi.org/10.21105/joss.05603},
year = {2023},
publisher = {The Open Journal},
volume = {8},
number = {89},
pages = {5603},
author = {Aaron Tin Long Lun and Jayaram Kancherla},
title = {Powering single-cell analyses in the browser with WebAssembly},
journal = {Journal of Open Source Software}
}
Check out Contributing for guidelines on opening issues and pull requests.
Deployment is as easy as serving the static files in this repository via HTTPS. Indeed, our deployment is just being served via GitHub Pages. other providers include static hosting on AWS S3, Google buckets, netlify or name-your-own-provider. As promised, there's no need to set up a backend server.
Thanks to llewelld for creating a docker image that can generate static HTML files without the hassle of setting up npm
and node
.
Build the docker images and tag them as kana.
docker build . -t kana
# if you are on a macos with m1 or m2, you MIGHT have to use the platform tag
docker build . -t kana --platform linux/arm64
Run the container to generate the production builds,
docker run -v .:/kana -t kana
# or depending on your operating system (noticed this on windows with WSL)
docker run -v $(pwd):/kana -t kana
and voila, you should now see a builds directory. you can also run the npm commands to generate the builds. checkout either the Dockerfile or the contributing section in this README.
There are numerous options to serve the html files locally using tools that are probably already available on your machine.
Python's http.server
python -m http.server 3000 -d builds
npm's serve
npm install -g serve
serve builds
or caddy, apache, nginx or static hosting solutions, or anything else you are familiar with.
We have significantly revamped the entire application and the underlying infrastructure to support hybrid compute - either purely client-side with webassembly, or on backend systems through node, or both.
kana uses the scran.js library for efficient client-side execution of single-cell analysis steps. This uses a variety of C/C++ libraries compiled to WebAssembly to enable heavy-duty calculations in the browser at near-native speed.
All computations performed by kana run in a Web Worker. This avoids blocking on the main thread and allows the application to be more responsive. Data is sent to the main thread on an as-needed basis, e.g., for visualizations. We also create separate Web Workers for the t-SNE and UMAP steps so that they can be run concurrently for maximum efficiency.
The WASM code itself is compiled with PThreads support to enable parallelization of some analysis steps.
This involves the use of a SharedArrayBuffer
to efficiently share memory across Web Workers,
which in turn requires cross origin isolation of the site.
We achieve this by using a service worker to cache the resources and load the blobs with the relevant headers - hence the need for HTTPS.
bakana
). One can extend Kana to interact to this API (#good-first-issue).kana
files). This package specifies the formats and provides readers for parsing various versions.For the curious: this project was bootstrapped with the Create React App.