Explore Workflows

https://github.com/nal-i5k/organism_onboarding.git

Path: flow_apollo2_data_processing/processing/workflow.cwl

Branch/Commit ID: 0ecf492419ddaa015f14a163381948c53b3deea6

Gene expression merge - combines RPKM gene expression from several experiments =================================================================================== Workflows merges RPKM gene expression from several experiments based on the values from GeneId, Chrom, TxStart, TxEnd and Strand columns. Reported RPKM columns are renamed based on the experiments names.

https://github.com/datirium/workflows.git

Path: workflows/feature-merge.cwl

Branch/Commit ID: 8a92669a566589d80fde9d151054ffc220ed4ddd

https://github.com/common-workflow-language/cwltool.git

Path: tests/wf/1st-workflow.cwl

Branch/Commit ID: e6c2d955a448225f026a04130443d13661844440

Devel version of Single-Cell Cell Ranger Aggregate ================================================== Workflow calls \"cellranger aggr\" command to combine output files from \"cellranger count\" (the molecule_info.h5 file from each run) into a single feature-barcode matrix containing all the data. When combining multiple GEM wells, the barcode sequences for each channel are distinguished by a GEM well suffix appended to the barcode sequence. Each GEM well is a physically distinct set of GEM partitions, but draws barcode sequences randomly from the pool of valid barcodes, known as the barcode whitelist. To keep the barcodes unique when aggregating multiple libraries, we append a small integer identifying the GEM well to the barcode nucleotide sequence, and use that nucleotide sequence plus ID as the unique identifier in the feature-barcode matrix. For example, AGACCATTGAGACTTA-1 and AGACCATTGAGACTTA-2 are distinct cell barcodes from different GEM wells, despite having the same barcode nucleotide sequence. This number, which tells us which GEM well this barcode sequence came from, is called the GEM well suffix. The numbering of the GEM wells will reflect the order that the GEM wells were provided in the \"molecule_info_h5\" and \"gem_well_labels\" inputs. When combining data from multiple GEM wells, the \"cellranger aggr\" pipeline automatically equalizes the average read depth per cell between groups before merging. This approach avoids artifacts that may be introduced due to differences in sequencing depth. It is possible to turn off normalization or change the way normalization is done through the \"normalization_mode\" input. The \"none\" value may be appropriate if you want to maximize sensitivity and plan to deal with depth normalization in a downstream step.

https://github.com/datirium/workflows.git

Path: workflows/cellranger-aggr.cwl

Branch/Commit ID: 8a92669a566589d80fde9d151054ffc220ed4ddd

Slightly changed original [BioWardrobe's](https://biowardrobe.com) [PubMed ID:26248465](https://www.ncbi.nlm.nih.gov/pubmed/26248465) **RNA-Seq** basic analysis for **strand specific pair-end** experiment. An additional steps were added to map data to mitochondrial chromosome only and then merge the output. Experiment files in [FASTQ](http://maq.sourceforge.net/fastq.shtml) format either compressed or not can be used. Current workflow should be used only with the pair-end strand specific RNA-Seq data. It performs the following steps: 1. `STAR` to align reads from input FASTQ file according to the predefined reference indices; generate unsorted BAM file and alignment statistics file 2. `fastx_quality_stats` to analyze input FASTQ file and generate quality statistics file 3. `samtools sort` to generate coordinate sorted BAM(+BAI) file pair from the unsorted BAM file obtained on the step 1 (after running STAR) 5. Generate BigWig file on the base of sorted BAM file 6. Map input FASTQ file to predefined rRNA reference indices using Bowtie to define the level of rRNA contamination; export resulted statistics to file 7. Calculate isoform expression level for the sorted BAM file and GTF/TAB annotation file using `GEEP` reads-counting utility; export results to file

https://github.com/datirium/workflows.git

Path: workflows/rnaseq-pe-dutp-mitochondrial.cwl

Branch/Commit ID: 8a92669a566589d80fde9d151054ffc220ed4ddd

Principal Component Analysis --------------- Principal component analysis (PCA) is a statistical procedure that uses an orthogonal transformation to convert a set of observations of possibly correlated variables (entities each of which takes on various numerical values) into a set of values of linearly uncorrelated variables called principal components. The calculation is done by a singular value decomposition of the (centered and possibly scaled) data matrix, not by using eigen on the covariance matrix. This is generally the preferred method for numerical accuracy.

https://github.com/datirium/workflows.git

Path: workflows/pca.cwl

Branch/Commit ID: 8a92669a566589d80fde9d151054ffc220ed4ddd

https://github.com/ddbj/human-reseq.git

Path: Workflows/bams2gvcf.woBQSR_male_chrXY_wXTR.cwl

Branch/Commit ID: b06a9beafaa6009587d1f0fca0941bca5e0f0a27

https://github.com/common-workflow-language/cwltool.git

Path: cwltool/schemas/v1.0/v1.0/scatter-valuefrom-wf6.cwl

Branch/Commit ID: e835bc0487fe42fb330b6222c9be65d18dd81ec9

Workflow maps FASTQ files from `fastq_files` input into reference genome `reference_star_indices_folder` and insilico generated `insilico_star_indices_folder` genome (concatenated genome for both `strain1` and `strain2` strains). For both genomes STAR is run with `outFilterMultimapNmax` parameter set to 1 to discard all of the multimapped reads. For insilico genome SAM file is generated. Then it's splitted into two SAM files based on strain names and then sorted by coordinates into the BAM format. For reference genome output BAM file from STAR slignment is also coordinate sorted.

https://github.com/datirium/workflows.git

Path: subworkflows/allele-vcf-alignreads-se-pe.cwl

Branch/Commit ID: 7a4593d2fa5b2fcbedc9219dc5687a4bc5aea66a

https://github.com/datirium/workflows.git

Path: metadata/advanced-header.cwl

Branch/Commit ID: 1f03ff02ef829bdb9d582825bcd4ca239e84ca2e