Cell Ranger 1.0, printed on 01/29/2020
The Cell Ranger software strives to maintain compatibility with common analysis tools by using standard output file formats whenever possible. For example, the barcoded BAM files can be viewed in standard genome browsers such as IGV to verify alignment quality and other features. The Chromium-specific data, including cellular and molecular barcodes, can be accessed via any third-party tools or scripts that can parse the additional elements utilized by Cell Ranger.
All pipelines produce all of their output in a single pipeline output directory which, by default, is named according to the flowcell serial number for cellranger demux (e.g., HAWT7ADXX) and --id name for cellranger run. Output files will appear in the outs/ subdirectory within this pipeline output directory. For example, a typical cellranger run may look like:
$ cd /home/jdoe/runs $ cellranger run --id=sample345 \ --transcriptome=/opt/refdata-cellranger-1.0.0/hg19 \ --fastqs=/home/jdoe/runs/HAWT7ADXX/outs/fastq_path \ --indices=SI-3A-A1 \ --cells=1000 Martian Runtime - 1.3.0 Running preflight checks (please wait)... 2016-01-01 10:23:52 [runtime] (ready) ID.sample345.CELLRANGER_CS.CELLRANGER.SETUP_CHUNKS ... 2012-01-01 12:10:09 [runtime] (join_complete) ID.sample345.CELLRANGER_CS.CELLRANGER.SUMMARIZE_REPORTS Outputs: - Genome-aligned BAM: /opt/sample345/outs/possorted_genome_bam.bam - Genome-aligned BAM index: /opt/sample345/outs/possorted_genome_bam_index.bam.bai - Run summary HTML: /opt/sample345/outs/web_summary.html - Run summary CSV: /opt/sample345/outs/metrics_summary.csv - Unfiltered gene-barcode matrices: /opt/sample345/outs/raw_gene_bc_matrices - Filtered gene-barcode matrices: /opt/sample345/outs/filtered_gene_bc_matrices - Matrix analysis: /opt/sample345/outs/analysis - Per-molecule read information: /opt/sample345/outs/molecule_info.h5 Pipestance completed successfully!
In this case,
/home/jdoe/runs/ is where the pipeline was run
/home/jdoe/runs/sample345/ is the pipeline output directory
/home/jdoe/runs/sample345/outs/ contains the pipeline output files
More information about the contents of the pipeline output directory can be found in the Pipestance Structure page.