BacSC: A general workflow for bacterial single-cell RNA sequencing data analysis
This repository contains the BacSC pipeline for bacterial single-cell sequencing data analysis (Ostner et al., 2024). It also contains all code needed to reproduce the analyses in the publication (TODO).
For usage info, please refer to the tutorials in the respective directory.
Raw and intermediate data objects can be downloaded on zenodo.
Simply download the data directory from there and move it into the BacSC directory.
Installation
Usage
The tutorials directory contains two tutorial notebooks.
The easiest way to use BacSC on your data is to copy these notebooks and replace the respective paths at the top of the notebooks.
BacSC_tutorial_general_pipeline.ipynbshows how to perform Variance stabilization, dimension reduction and clustering.BacSC_cluster_analysis_tutorial.ipynbgives a template for differential expression testing with BacSC.
Repository structure
This repository is structured as follows:
- The
toolsdirectory contains all functions and code used throughout the BacSC pipeline. - The
tutorialsdirectory contains two tutorial notebooks. The easiest way to use BacSC on your data is to copy these notebooks and replace the respective paths at the top of the notebooks.BacSC_tutorial_general_pipeline.ipynbshows how to perform Variance stabilization, dimension reduction and clustering.BacSC_cluster_analysis_tutorial.ipynbgives a template for differential expression testing with BacSC.
- The
analysisdirectory provides notebooks for reproduction of the results in the publication (TODO). Grouped by dataset source, there are 3 notebooks for each dataset:<dataset>_final_pipeline(or<dataset>_final_pipeline_2) performs the general BacSC analsis up to cell type clustering.<dataset>_cluster_analysisperforms DA testing on the clusters determined before.<dataset>_summary_figuresgenerates the figures for each dataset in the manuscript.
Metadata
Release files for BacSC 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bacsc-0.1.1.tar.gz | 6.2 MB | Without provenance | Details for bacsc-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bacsc-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for bacsc-0.1.1-py3-none-any.whl |
Total release size: 6.2 MB
Release files / bacsc-0.1.1.tar.gz
| Download URL | bacsc-0.1.1.tar.gz |
|---|---|
| Size | 6.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97f1a7e115050cc51a180e136fd25612015b58afe84c29499ee44238e0d78860
|
|
BLAKE2b-256 checksum How to use checksums |
cdd8ef2c90fb194e32e9d9fa03fb8c7fe420f0fe9dd7dbc979a4aa745c764db0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.4
|
Release files / bacsc-0.1.1-py3-none-any.whl
| Download URL | bacsc-0.1.1-py3-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bd9991730d01301db7834dbeee502459e1e42ad883286ba0e2ce7fd72b44e00
|
|
BLAKE2b-256 checksum How to use checksums |
803cefbb7913665360f57ab95ede5d98000a887f26fcd34aaa23ccbc42097602
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.4
|
Security for BacSC 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.