Explore Workflows

View already parsed workflows here or click here to add your own

Graph Name Retrieved From View
workflow graph cond-wf-013.cwl

https://github.com/common-workflow-language/cwl-v1.2.git

Path: tests/conditionals/cond-wf-013.cwl

Branch/Commit ID: e62f99dd79d6cb9c157cceb458f74200da84f6e9

workflow graph checker-workflow-wrapping-tool.cwl

This demonstrates how to wrap a \"real\" tool with a checker workflow that runs both the tool and a tool that performs verification of results

https://github.com/dockstore-testing/md5sum-checker.git

Path: checker-workflow-wrapping-tool.cwl

Branch/Commit ID: 761499a8329b367d37eb83d180fb762e04ada97f

workflow graph GSEApy - Gene Set Enrichment Analysis in Python

GSEAPY: Gene Set Enrichment Analysis in Python ============================================== Gene Set Enrichment Analysis is a computational method that determines whether an a priori defined set of genes shows statistically significant, concordant differences between two biological states (e.g. phenotypes). GSEA requires as input an expression dataset, which contains expression profiles for multiple samples. While the software supports multiple input file formats for these datasets, the tab-delimited GCT format is the most common. The first column of the GCT file contains feature identifiers (gene ids or symbols in the case of data derived from RNA-Seq experiments). The second column contains a description of the feature; this column is ignored by GSEA and may be filled with “NA”s. Subsequent columns contain the expression values for each feature, with one sample's expression value per column. It is important to note that there are no hard and fast rules regarding how a GCT file's expression values are derived. The important point is that they are comparable to one another across features within a sample and comparable to one another across samples. Tools such as DESeq2 can be made to produce properly normalized data (normalized counts) which are compatible with GSEA.

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

Path: workflows/gseapy.cwl

Branch/Commit ID: b5e16e359007150647b14dc6e038f4eb8dccda79

workflow graph WGS and MT analysis for fastq files

rna / protein - qc, preprocess, filter, annotation, index, abundance

https://github.com/MG-RAST/pipeline.git

Path: CWL/Workflows/wgs-fasta.workflow.cwl

Branch/Commit ID: 1844de830f6935901849ccd9966685fbf13e8042

workflow graph extract_gencoll_ids

https://github.com/ncbi/pgap.git

Path: task_types/tt_extract_gencoll_ids.cwl

Branch/Commit ID: 49732e54e2fe2eafd2f82df3c482c73e642f6d64

workflow graph sum-wf.cwl

https://github.com/common-workflow-language/cwl-v1.2.git

Path: tests/sum-wf.cwl

Branch/Commit ID: ea9f8634e41824ac3f81c3dde698d5f0eef54f1b

workflow graph Trim Galore RNA-Seq pipeline paired-end strand specific

Modified original [BioWardrobe's](https://biowardrobe.com) [PubMed ID:26248465](https://www.ncbi.nlm.nih.gov/pubmed/26248465) **RNA-Seq** basic analysis for a **pair-end** experiment. A corresponded input [FASTQ](http://maq.sourceforge.net/fastq.shtml) file has to be provided. Current workflow should be used only with the single-end RNA-Seq data. It performs the following steps: 1. Trim adapters from input FASTQ files 2. Use STAR to align reads from input FASTQ files according to the predefined reference indices; generate unsorted BAM file and alignment statistics file 3. Use fastx_quality_stats to analyze input FASTQ files and generate quality statistics files 4. Use 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 files 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/trim-rnaseq-pe-dutp.cwl

Branch/Commit ID: ce058d892d330125cd03d0a0d5fb3b321cda0be3

workflow graph env-wf3.cwl

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

Path: cwltool/schemas/v1.0/v1.0/env-wf3.cwl

Branch/Commit ID: 4a31f2a1c1163492ae37bbc748a299e8318c462c

workflow graph scatter-wf3_v1_1.cwl#main

https://github.com/common-workflow-language/cwl-utils.git

Path: testdata/scatter-wf3_v1_1.cwl

Branch/Commit ID: 124a08ce3389eb49066c34a4163cbbed210a0355

Packed ID: main

workflow graph Generate genome indices for STAR & bowtie

Creates indices for: * [STAR](https://github.com/alexdobin/STAR) v2.5.3a (03/17/2017) PMID: [23104886](https://www.ncbi.nlm.nih.gov/pubmed/23104886) * [bowtie](http://bowtie-bio.sourceforge.net/tutorial.shtml) v1.2.0 (12/30/2016) It performs the following steps: 1. `STAR --runMode genomeGenerate` to generate indices, based on [FASTA](http://zhanglab.ccmb.med.umich.edu/FASTA/) and [GTF](http://mblab.wustl.edu/GTF2.html) input files, returns results as an array of files 2. Outputs indices as [Direcotry](http://www.commonwl.org/v1.0/CommandLineTool.html#Directory) data type 3. Separates *chrNameLength.txt* file from Directory output 4. `bowtie-build` to generate indices requires genome [FASTA](http://zhanglab.ccmb.med.umich.edu/FASTA/) file as input, returns results as a group of main and secondary files

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

Path: workflows/genome-indices.cwl

Branch/Commit ID: 3fc68366adb179927af5528c27b153abaf94494d