Explore Workflows

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

Graph Name Retrieved From View
workflow graph checker_workflow_wrapping_workflow.cwl

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

https://github.com/dockstore-testing/dockstore-workflow-md5sum-unified.git

Path: checker_workflow_wrapping_workflow.cwl

Branch/Commit ID: 3a604c0e70b2dc62973917cc186dc6db5a6ce519

workflow graph scatter-valuefrom-wf5.cwl

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

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

Branch/Commit ID: bbe20f54deea92d9c9cd38cb1f23c4423133d3de

workflow graph Subworkflow to allow calling cnvkit with cram instead of bam files

https://github.com/genome/analysis-workflows.git

Path: definitions/subworkflows/cram_to_cnvkit.cwl

Branch/Commit ID: a23f42ef49c10a588fd35a3afaad5de03e253533

workflow graph format_rrnas_from_seq_entry

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

Path: task_types/tt_format_rrnas_from_seq_entry.cwl

Branch/Commit ID: e71779665f42fcf34601b0f65e030bb0dd47fa79

workflow graph kmer_top_n_extract

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

Path: task_types/tt_kmer_top_n_extract.cwl

Branch/Commit ID: 1b8d71c75156a1a62bf0477d59db26010e2dcc29

workflow graph bam-bedgraph-bigwig.cwl

Workflow converts input BAM file into bigWig and bedGraph files. Input BAM file should be sorted by coordinates (required by `bam_to_bedgraph` step). If `split` input is not provided use true by default. Default logic is implemented in `valueFrom` field of `split` input inside `bam_to_bedgraph` step to avoid possible bug in cwltool with setting default values for workflow inputs. `scale` has higher priority over the `mapped_reads_number`. The last one is used to calculate `-scale` parameter for `bedtools genomecov` (step `bam_to_bedgraph`) only in a case when input `scale` is not provided. All logic is implemented inside `bedtools-genomecov.cwl`. `bigwig_filename` defines the output name only for generated bigWig file. `bedgraph_filename` defines the output name for generated bedGraph file and can influence on generated bigWig filename in case when `bigwig_filename` is not provided. All workflow inputs and outputs don't have `format` field to avoid format incompatibility errors when workflow is used as subworkflow.

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

Path: tools/bam-bedgraph-bigwig.cwl

Branch/Commit ID: b5e16e359007150647b14dc6e038f4eb8dccda79

workflow graph mut2.cwl

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

Path: tests/wf/mut2.cwl

Branch/Commit ID: 2a8af96d334e6979cb00af4569581d192d43ce41

workflow graph umi duplex alignment workflow

https://github.com/genome/analysis-workflows.git

Path: definitions/subworkflows/duplex_alignment.cwl

Branch/Commit ID: f401b02285f30de1c12ac2859134099fe04be33f

workflow graph Trim Galore ChIP-Seq pipeline single-read

The original [BioWardrobe's](https://biowardrobe.com) [PubMed ID:26248465](https://www.ncbi.nlm.nih.gov/pubmed/26248465) **ChIP-Seq** basic analysis workflow for a **single-read** experiment with Trim Galore. _Trim Galore_ is a wrapper around [Cutadapt](https://github.com/marcelm/cutadapt) and [FastQC](http://www.bioinformatics.babraham.ac.uk/projects/fastqc/) to consistently apply adapter and quality trimming to FastQ files, with extra functionality for RRBS data. In outputs it returns coordinate sorted BAM file alongside with index BAI file, quality statistics of the input FASTQ file, reads coverage in a form of BigWig file, peaks calling data in a form of narrowPeak or broadPeak files, islands with the assigned nearest genes and region type, data for average tag density plot (on the base of BAM file). Workflow starts with step *fastx\_quality\_stats* from FASTX-Toolkit to calculate quality statistics for input FASTQ file. At the same time `bowtie` is used to align reads from input FASTQ file to reference genome *bowtie\_aligner*. The output of this step is unsorted SAM file which is being sorted and indexed by `samtools sort` and `samtools index` *samtools\_sort\_index*. Based on workflow’s input parameters indexed and sorted BAM file can be processed by `samtools rmdup` *samtools\_rmdup* to get rid of duplicated reads. If removing duplicates is not required the original input BAM and BAI files return. Otherwise step *samtools\_sort\_index\_after\_rmdup* repeat `samtools sort` and `samtools index` with BAM and BAI files. Right after that `macs2 callpeak` performs peak calling *macs2\_callpeak*. On the base of returned outputs the next step *macs2\_island\_count* calculates the number of islands and estimated fragment size. If the last one is less that 80bp (hardcoded in the workflow) `macs2 callpeak` is rerun again with forced fixed fragment size value (*macs2\_callpeak\_forced*). If at the very beginning it was set in workflow input parameters to force run peak calling with fixed fragment size, this step is skipped and the original peak calling results are saved. In the next step workflow again calculates the number of islands and estimates fragment size (*macs2\_island\_count\_forced*) for the data obtained from *macs2\_callpeak\_forced* step. If the last one was skipped the results from *macs2\_island\_count\_forced* step are equal to the ones obtained from *macs2\_island\_count* step. Next step (*macs2\_stat*) is used to define which of the islands and estimated fragment size should be used in workflow output: either from *macs2\_island\_count* step or from *macs2\_island\_count\_forced* step. If input trigger of this step is set to True it means that *macs2\_callpeak\_forced* step was run and it returned different from *macs2\_callpeak* step results, so *macs2\_stat* step should return [fragments\_new, fragments\_old, islands\_new], if trigger is False the step returns [fragments\_old, fragments\_old, islands\_old], where sufix \"old\" defines results obtained from *macs2\_island\_count* step and sufix \"new\" - from *macs2\_island\_count\_forced* step. The following two steps (*bamtools\_stats* and *bam\_to\_bigwig*) are used to calculate coverage on the base of input BAM file and save it in BigWig format. For that purpose bamtools stats returns the number of mapped reads number which is then used as scaling factor by bedtools genomecov when it performs coverage calculation and saves it in BED format. The last one is then being sorted and converted to BigWig format by bedGraphToBigWig tool from UCSC utilities. Step *get\_stat* is used to return a text file with statistics in a form of [TOTAL, ALIGNED, SUPRESSED, USED] reads count. Step *island\_intersect* assigns genes and regions to the islands obtained from *macs2\_callpeak\_forced*. Step *average\_tag\_density* is used to calculate data for average tag density plot on the base of BAM file.

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

Path: workflows/trim-chipseq-se.cwl

Branch/Commit ID: 9ee330737f4603e4e959ffe786fbb2046db70a00

workflow graph count-lines14-wf.cwl

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

Path: v1.0/v1.0/count-lines14-wf.cwl

Branch/Commit ID: 9a23706ec061c5d2c02ff60238d218aadf0b5db9