Explore Workflows

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

Graph Name Retrieved From View
workflow graph simple_two_step.cwl

https://github.com/ncbi/cwl-demos.git

Path: blast-pipelines/simple_two_step.cwl

Branch/Commit ID: master
workflow graph wf_simulate_data_collection.cwl

https://github.com/idaks/cwl_modeling.git

Path: yw_cwl_modeling/yw2cwl_parser/example_sql/simulate_data_collection/wf_simulate_data_collection.cwl

Branch/Commit ID: master
workflow graph Vcf concordance evaluation workflow

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

Path: definitions/subworkflows/vcf_eval_concordance.cwl

Branch/Commit ID: master
workflow graph create_snap_and_analyze.cwl

https://github.com/hubmapconsortium/sc-atac-seq-pipeline.git

Path: create_snap_and_analyze.cwl

Branch/Commit ID: 4b2af54
workflow graph wf_extract_prism_data.cwl

https://github.com/idaks/cwl_modeling.git

Path: yw_cwl_modeling/yw_cwl_parser_old/Examples/extract_prism_data/wf_extract_prism_data.cwl

Branch/Commit ID: master
workflow graph bsbolt_multilib.cwl

https://github.com/CompEpigen/PipelineOlympics.git

Path: CWL/workflows/BSBolt/bsbolt_multilib.cwl

Branch/Commit ID: main
workflow graph biowardrobe_chipseq_se.cwl

The workflow is used to run CHIP-Seq basic analysis with single-end input FASTQ file. 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.

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

Path: biowardrobe_chipseq_se.cwl

Branch/Commit ID: v0.0.5
workflow graph access_qc.cwl

https://github.com/msk-access/qc_generation.git

Path: access_qc.cwl

Branch/Commit ID: develop
workflow graph no-outputs-wf.cwl

Workflow without outputs.

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

Path: tests/no-outputs-wf.cwl

Branch/Commit ID: main
workflow graph timelimit2-wf.cwl

The entire test should take ~24 seconds. Test that the 20 second time limit applies to each step individually (so 1st step has 20 seconds and the 2nd step has 20 seconds). So this 20 second time limit should not cause the workflow to fail. The timing on this test was updated from shorter values to accommodate the startup time of certain container runners, the previous timelimit of 5 seconds was too short, which is why it is now 20 seconds.

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

Path: tests/timelimit2-wf.cwl

Branch/Commit ID: main