https://github.com/alleninstitute/barware-pipeline

Hashed scRNA-seq data processing pipeline

https://github.com/alleninstitute/barware-pipeline

Science Score: 23.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
    1 of 1 committers (100.0%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (10.5%) to scientific vocabulary
Last synced: 11 months ago · JSON representation

Repository

Hashed scRNA-seq data processing pipeline

Basic Info
  • Host: GitHub
  • Owner: AllenInstitute
  • License: other
  • Language: Shell
  • Default Branch: main
  • Homepage:
  • Size: 68.4 KB
Statistics
  • Stars: 2
  • Watchers: 2
  • Forks: 1
  • Open Issues: 2
  • Releases: 2
Created about 5 years ago · Last pushed almost 5 years ago
Metadata Files
Readme Contributing License

README.md

BarWare-pipeline

Installing and running the pipeline

Repository retrieval and installation

git clone git@github.com:AllenInstitute/BarWare-pipeline cd BarWare-pipeline git submodule update --init R -e 'install.packages("BarMixer", type = "source", repos = NULL)' chmod +x BarCounter-release/barcounter

Running the pipeline

Stage 0: Run cellranger count

The BarWare pipeline is currently configured to demultiplex 10x Genomics 3' scRNA-seq data. Before analysis with BarCounter and BarMixer, we recommend that you run cellranger count to obtain the necessary scRNA-seq inputs for use with this pipeline.

If you are using a different analysis pipeline or method and would like to utilize BarWare, please let us know in the Issues page.

Before you run BarWare

You'll need 2 critical input files before running the BarWare pipeline:

1: A Well Sheet .csv file

You will need to generate a Well Sheet .csv file to specify which wells will be demultiplexed. This .csv should have the following columns: - wellid: An identifier for each well - fastqpath: The path to the directory containing the HTO FASTQ files for your well - fastqprefix: The prefix for your well that is appended to your HTO FASTQ files (multiple lanes will be automatically identified) - cellrangerouts: The full path to the cellranger count outs/ directory for each well

Example well_sheet.csv well_id,fastq_path,fastq_prefix,cellranger_outs X017-P1C1W1,/mnt/barware-manuscript/X017_fastq/,Pool-16-HTO,/mnt/barware-manuscript/code-testing/X017-P1C1W1/outs/ X017-P1C1W2,/mnt/barware-manuscript/X017_fastq/,Pool-24-HTO,/mnt/barware-manuscript/code-testing/X017-P1C1W2/outs/ X017-P1C1W3,/mnt/barware-manuscript/X017_fastq/,Pool-32-HTO,/mnt/barware-manuscript/code-testing/X017-P1C1W3/outs/

2: A Sample Sheet .csv file

The samplesheet.csv file specifies which samples are associated with which barcodes. This .csv should have the following columns:
- sampleid: The name of each multiplexed sample - poolid: An identifier for the pool of samples to demultiplex - hashname: The name of the HTOs used for hashing - hashtag: The sequence of the HTO barcodes used for hashing

example sample_sheet.csv sample_id,pool_id,hash_name,hash_tag 2735BW-MEM-1,X017-P1,HT1,GTCAACTCTTTAGCG 2735BW-MEM-2,X017-P1,HT2,TGATGGCCTATTGGG 2735BW-NIV-1,X017-P1,HT3,TTCCGCCTCTCTTTG 2735BW-NIV-2,X017-P1,HT4,AGTAAGTTCAGCGTA 2735BW-NON-1,X017-P1,HT5,AAGTATCGTTTCGCA 2735BW-NON-2,X017-P1,HT6,GGTTGCCAGATGTCA

With these in hand, you're ready for the BarWare pipeline.

Stage 1: Counting HTOs with BarCounter

A convenient wrapper script is provided in BarWare to run multiple wells in sequence using BarCounter: 01_run_BarCounter.sh. This script has 4 parameters: - -s: the full path to the samplesheet.csv file - -w: the full path to the wellsheet.csv file - -o: the full path of a directory to use for outputs

For example: bash BarWare-pipeline/01_run_BarCounter.sh \ -s $(pwd)/X017_sample_sheet.csv \ -w $(pwd)/X017_well_sheet.csv \ -o $(pwd)/X017_demultiplex_results

Stage 1 will generate outputs for each well: <output_dir>/ <well_id>/ hto_counts/ <fastq_prefix>_Tag_Counts.csv <fastq_prefix>_BarCounter.log <fastq_prefix>_valid_barcodes.txt

Stage 2: Demultiplexing and QC with BarMixer

BarMixer demultiplexing can be run using the 02_run_BarMixer.sh shell script. This script has 3 parameters: - -s: the full path to the samplesheet.csv file - -w: the full path to the wellsheet.csv file - -o: the full path of a directory to use for outputs

Note that the parameters -s, -w, and -o should be the same for both Stage 1 and Stage 2.

bash BarWare-pipeline/02_run_BarMixer.sh \ -s $(pwd)/X017_sample_sheet.csv \ -w $(pwd)/X017_well_sheet.csv \ -o $(pwd)/X017_demultiplex_results

Stage 2 will generate outputs for each well, and combined results for all wells. Final outputs separated by sample for downstream use are in the mergedh5/ subfolder. ``` <outputdir>/ / htoprocessed/ <wellid>htocategorytable.csv.gz <wellid>htocountmatrix.csv.gz <wellid>htoprocessingmetrics.json <wellid>htoreport.html rnametadata/ <wellid>.h5 wellmetadatareport.html <wellid>wellmetrics.json splith5/ <wellid><hashtag>.h5 multiplet.h5 <wellid>splith5metrics.json <wellid>splitreport.html mergedh5/ mergereport.html <sampleid>.h5 _multiplet.h5 ```

Using a docker image

Image retrieval
A pre-built docker image containing the BarWare pipeline can be downloaded from dockerhub using: docker pull hypercompetent/barware:latest

Image building
If you would like to re-build the Docker image, the Dockerfile is provided in the BarWare-pipeline repository: cd BarWare-pipeline docker build ./ -t barware:v1.0

Legal Information

License

The license for this package is available on Github in the file LICENSE in this repository

Level of Support

We are not currently supporting this code, but simply releasing it to the community AS IS but are not able to provide any guarantees of support. The community is welcome to submit issues, but you should not expect an active response.

Contribution Agreement

If you contribute code to this repository through pull requests or other mechanisms, you are subject to the Allen Institute Contribution Agreement, which is available in the file CONTRIBUTING in this repository

Owner

  • Name: Allen Institute
  • Login: AllenInstitute
  • Kind: organization
  • Location: Seattle, WA

Please visit http://alleninstitute.github.io/ for more information.

GitHub Events

Total
Last Year

Committers

Last synced: about 1 year ago

All Time
  • Total Commits: 56
  • Total Committers: 1
  • Avg Commits per committer: 56.0
  • Development Distribution Score (DDS): 0.0
Past Year
  • Commits: 0
  • Committers: 0
  • Avg Commits per committer: 0.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Lucas Graybuck l****g@a****g 56
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: about 1 year ago

All Time
  • Total issues: 3
  • Total pull requests: 0
  • Average time to close issues: about 24 hours
  • Average time to close pull requests: N/A
  • Total issue authors: 2
  • Total pull request authors: 0
  • Average comments per issue: 0.33
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • emjbishop (2)
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels

Dependencies

Dockerfile docker
  • us.gcr.io/dev-pipeline-internal/google-r-base v1.0 build