Skip to content

Data types


This section of the documentation is currently under construction. If your question is not answered here, please contact us!

St. Jude Cloud hosts both raw genomic data files and processed results files:

File Type Short Description Details
BAM HG38 aligned BAM files produced by Microsoft Genomics Service (DNA-Seq) or STAR 2-pass mapping (RNA-Seq). Click here
gVCF Genomic VCF files produced by Microsoft Genomics Service. Click here
Somatic VCF Curated list of somatic variants produced by the St. Jude somatic variant analysis pipeline. Click here
CNV list of somatic copy number alterations produced by St. Jude CONSERTING pipeline. Click here

BAM files

In St. Jude Cloud, we stored aligned sequence reads in the ubiquitous BAM file format. For more information on SAM/BAM files, please refer to the SAM/BAM specification.

Whole Genome and Whole Exome

Whole Genome Sequence (WGS) and Whole Exome Sequence (WES) BAM files were produced by the Microsoft Genomics Service aligned to HG38 (GRCh38 no alt analysis set). For more information about how Microsoft Genomics produces BAM files or any other questions regarding data generation, please refer to the official Microsoft Genomics whitepaper.


RNA-Seq BAM files are mapped to HG38 + ERCC Spike In Sequences (commonly used for normalization of expression analyses). For alignment, STAR v2.5.3a 2-pass mapping followed by Picard MarkDuplicates. Below is the STAR command used during alignment. For more information about any of the parameters used, please refer to the STAR manual for v2.5.3a.

    STAR \
        --runThreadN $NUM_THREADS \                           # $NUM_THREADS is the number of threads to parallelize the alignment across (generally we use 4).
        --genomeDir $GENOME_DIR \                             # $GENOME_DIR is a STAR reference directory containing HG38 and ERCC Spike In sequences.
        --readFilesIn $READ_FILES \                           # $READ_FILES are the input FastQ files to align.
        --limitBAMsortRAM $MEMORY_LIMIT \                     # $MEMORY_LIMIT is a upper limit on the amount of RAM to use in the alignment.
        --outFileNamePrefix $OUT_FILE_PREFIX \
        --outSAMtype BAM SortedByCoordinate \
        --outSAMstrandField intronMotif \
        --outSAMattributes NH   HI   AS   nM   NM   MD   XS \
        --outSAMunmapped Within \
        --outSAMattrRGline $RGs \                             # $RGs is the read group information for each FastQ passed in $READ_FILES.
        --outFilterMultimapNmax 20 \
        --outFilterMultimapScoreRange 1 \
        --outFilterScoreMinOverLread 0.66 \
        --outFilterMatchNminOverLread 0.66 \
        --outFilterMismatchNmax 10 \
        --alignIntronMax 500000 \
        --alignMatesGapMax 1000000 \
        --alignSJDBoverhangMin 1 \
        --sjdbScore 2 \
        --twopassMode Basic

gVCF files

We provide gVCF files produced by the Microsoft Genomics Service. gVCF files are derived from the BAM files produced above as called by GATK's haplotype caller. Today, we defer to the official specification document from the Broad Institute, as well as this discussion on the difference between VCF and gVCF files. For more information about how Microsoft Genomics produces gVCF files or any other questions regarding data generation, please refer to the official Microsoft Genomics whitepaper.

Somatic VCF files

Somatic VCF files contain HG38 based SNV/Indel variant calls from the St. Jude somatic variant analysis pipeline as follows. Broadly speaking:

  1. Reads were aligned to HG19 using bwa backtrack (bwa aln + bwa sampe) using default parameters.
  2. Post processing of aligned reads was performed using Picard CleanSam and MarkDuplicates.
  3. Variants were called using the Bambino variant caller (you can download by navigating here and searching for "Bambino package").
  4. Variants were post-processed using an in-house post-processing pipeline that cleans and annotates variants. This pipeline is not currently publicly available.
  5. Variants were manually reviewed by analysts and published with the relevant Pediatric Cancer Genome Project (PCGP) paper.
  6. Post-publication, variants were lifted over to HG38 (the original HG19 coordinates are stored in the HG19 INFO field.).

For more information on variants for each of the individuals, please refer to the relevant PCGP paper. For more information on the variant calling format (VCF), please see the latest specification for VCF document listed here.

CNV files

CNV files contain copy number alteration (CNA) analysis results for paired tumor-normal WGS samples. Files are produced by running paired tumor-normal BAM files through the CONSERTING pipeline which identifies CNA through iterative analysis of (i) local segmentation by read depth within boundaries identified by structural variation (SV) breakpoints followed by (ii) segment merging and local SV analysis. CREST was used to identify local SV breakpoints. CNV files contain the following information:

Field Description
chrom chromosome
loc.start start of segment
loc.end end of segment
num.mark number of windows retained in the segment (gaps and windows with low mappability are excluded)
length.ratio The ratio between the length of the used windows to the genomic length
seg.mean The estimated GC corrected difference signal (2 copy gain will have a seg.mean of 1)
GMean The mean coverage in the germline sample (a value of 1 represents diploid)
DMean The mean coverage in the tumor sample
LogRatio Log2 ratio between tumor and normal coverage
Quality score A empirical score used in merging
SV_Matching whether the boundary of the segments were supported by SVs (3: both ends supported, 2: right end supported, 1: left end supported, 0: neither end supported)