Explore Workflows

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

Graph Name Retrieved From View
workflow graph Subworkflow for Annotation

\"Subworkflow for Metagenome Annotation This subworkflow is for annotation of predicted protein coding sequences. \"

https://github.com/RyoMameda/workflow_cwl.git

Path: Workflow/annotation_sw.cwl

Branch/Commit ID: e062424fbea28f174342f99fd2518237b1d26c32
workflow graph blastp_wnode_struct

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

Path: task_types/tt_blastp_wnode_struct.cwl

Branch/Commit ID: f697b1836fea55d442bedc2bb77afe5d4ef94b05
workflow graph kmer_top_n_extract

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

Path: task_types/tt_kmer_top_n_extract.cwl

Branch/Commit ID: 09774c78a965dd8f6c315597a53eef5998a3c1b6
workflow graph LBA_target.cwl

https://git.astron.nl/RD/LINC.git

Path: workflows/LBA_target.cwl

Branch/Commit ID: 96f1caf46ca4859e7cb49919dcb13bf53abf4393
workflow graph trim-chipseq-pe.cwl

Runs ChIP-Seq BioWardrobe basic analysis with paired-end input data files.

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

Path: workflows/trim-chipseq-pe.cwl

Branch/Commit ID: 80d64741638b14de5cf58236b6d6d99713c62086
workflow graph mpi_simple_wf.cwl

Simple 2 step workflow to check that workflow steps are independently picking up on the number of processes. First run the parallel get PIDs step (on the input num procs) then run (on a single proc) the line count. This should equal the input.

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

Path: tests/wf/mpi_simple_wf.cwl

Branch/Commit ID: 0cbbd92a87b1ba1d484bf50170c2749536fbbe77
workflow graph scatter-wf4.cwl#main

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

Path: tests/wf/scatter-wf4.cwl

Branch/Commit ID: 0cbbd92a87b1ba1d484bf50170c2749536fbbe77

Packed ID: main
workflow graph autosubmit.cwl

An example workflow created using Autosubmit's basic a000 workflow as reference. The `platform.yml` is ignored as it contains only information about platforms (e.g. it could be given to a tool like Troika as-is). `expdef.yml` and `autosubmit.yml` basically provide CWL inputs. `jobs.yml` contains the steps of the CWL workflow, with their dependencies. In CWL dependencies are specified via inputs and outputs. When task A outputs a value X, and task B has an input of type A/X, then the dependency A -> B is created in CWl. This is different than Autosubmit, and needs some care to guarantee the correct order in the workflow graph of start dates, members, chunks, etc.

https://github.com/kinow/kinoshita.eti.br.git

Path: notes/autosubmit/autosubmit.cwl

Branch/Commit ID: 039fdcc04236f1ad36248798bd93ada3f2158844
workflow graph bacterial_screening.cwl

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

Path: vecscreen/bacterial_screening.cwl

Branch/Commit ID: 22ffe27d9d4a899def7592d75d5871c1856adbdb
workflow graph Workflow to run pVACseq from detect_variants and rnaseq pipeline outputs

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

Path: definitions/subworkflows/pvacseq.cwl

Branch/Commit ID: 258bd4353ad1ca7790b3ae626bf42ab8194e7561