Explore Workflows

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

Graph Name Retrieved From View
workflow graph record-in-secondaryFiles-missing-wf.cwl

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

Path: tests/record-in-secondaryFiles-missing-wf.cwl

Branch/Commit ID: c7c97715b400ff2194aa29fc211d3401cea3a9bf
workflow graph Detect Variants workflow for WGS pipeline

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

Path: definitions/pipelines/detect_variants_wgs.cwl

Branch/Commit ID: 449bc7e45bb02316d040f73838ef18359e770268
workflow graph hmmsearch_wnode and gpx_qdump combined workflow to apply scatter/gather

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

Path: task_types/tt_hmmsearch_wnode_plus_qdump.cwl

Branch/Commit ID: 72c3091012f5c2dce38ad9213cda617d2c7a61ac
workflow graph extract_gencoll_ids

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

Path: task_types/tt_extract_gencoll_ids.cwl

Branch/Commit ID: 72c3091012f5c2dce38ad9213cda617d2c7a61ac
workflow graph varscan somatic workflow

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

Path: definitions/subworkflows/varscan.cwl

Branch/Commit ID: e0b3c76e38630fb6234414b5adebfb6a4fb23117
workflow graph MAnorm SE - quantitative comparison of ChIP-Seq single-read data

What is MAnorm? -------------- MAnorm is a robust model for quantitative comparison of ChIP-Seq data sets of TFs (transcription factors) or epigenetic modifications and you can use it for: * Normalization of two ChIP-seq samples * Quantitative comparison (differential analysis) of two ChIP-seq samples * Evaluating the overlap enrichment of the protein binding sites(peaks) * Elucidating underlying mechanisms of cell-type specific gene regulation How MAnorm works? ---------------- MAnorm uses common peaks of two samples as a reference to build the rescaling model for normalization, which is based on the empirical assumption that if a chromatin-associated protein has a substantial number of peaks shared in two conditions, the binding at these common regions will tend to be determined by similar mechanisms, and thus should exhibit similar global binding intensities across samples. The observed differences on common peaks are presumed to reflect the scaling relationship of ChIP-Seq signals between two samples, which can be applied to all peaks. What do the inputs mean? ---------------- ### General **Experiment short name/Alias** * short name for you experiment to identify among the others **ChIP-Seq SE sample 1** * previously analyzed ChIP-Seq single-read experiment to be used as Sample 1 **ChIP-Seq SE sample 2** * previously analyzed ChIP-Seq single-read experiment to be used as Sample 2 **Genome** * Reference genome to be used for gene assigning ### Advanced **Reads shift size for sample 1** * This value is used to shift reads towards 3' direction to determine the precise binding site. Set as half of the fragment length. Default 100 **Reads shift size for sample 2** * This value is used to shift reads towards 5' direction to determine the precise binding site. Set as half of the fragment length. Default 100 **M-value (log2-ratio) cutoff** * Absolute M-value (log2-ratio) cutoff to define biased (differential binding) peaks. Default: 1.0 **P-value cutoff** * P-value cutoff to define biased peaks. Default: 0.01 **Window size** * Window size to count reads and calculate read densities. 2000 is recommended for sharp histone marks like H3K4me3 and H3K27ac, and 1000 for TFs or DNase-seq. Default: 2000

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

Path: workflows/manorm-se.cwl

Branch/Commit ID: 12e5256de1b680c551c87fd5db6f3bc65428af67
workflow graph kmer_build_tree

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

Path: task_types/tt_kmer_build_tree.cwl

Branch/Commit ID: 42df0c0f9a4e5697abadd9cb52440691fafc8f5d
workflow graph Nested workflow example

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

Path: tests/wf/double-nested.cwl

Branch/Commit ID: 8ef515037de411abd2f84b569ad4d4a4f7a2c7a0
workflow graph heatmap-prepare.cwl

Workflow runs homer-make-tag-directory.cwl tool using scatter for the following inputs - bam_file - fragment_size - total_reads `dotproduct` is used as a `scatterMethod`, so one element will be taken from each array to construct each job: 1) bam_file[0] fragment_size[0] total_reads[0] 2) bam_file[1] fragment_size[1] total_reads[1] ... N) bam_file[N] fragment_size[N] total_reads[N] `bam_file`, `fragment_size` and `total_reads` arrays should have the identical order.

https://github.com/Barski-lab/workflows.git

Path: subworkflows/heatmap-prepare.cwl

Branch/Commit ID: afbec98437a7796a509fffbad8c3370aa099f059
workflow graph kmer_cache_retrieve

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

Path: task_types/tt_kmer_cache_retrieve.cwl

Branch/Commit ID: 0d9e6bb52eac0c209af3977aa779e39aaa432458