Explore Workflows

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

Graph Name Retrieved From View
workflow graph step-valuefrom3-wf_v1_1.cwl

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

Path: testdata/step-valuefrom3-wf_v1_1.cwl

Branch/Commit ID: 124a08ce3389eb49066c34a4163cbbed210a0355

workflow graph gathered exome alignment and somatic variant detection for cle purpose

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

Path: definitions/pipelines/gathered_cle_somatic_exome.cwl

Branch/Commit ID: f9600f9959acdc30259ba7e64de61104c9b01f0b

workflow graph bwa_pe.cwl

https://github.com/nci-gdc/gdc-dnaseq-cwl.git

Path: workflows/bamfastq_align/bwa_pe.cwl

Branch/Commit ID: 6b43e8b03256492f2b36ffcf548704daaafee6f6

workflow graph search.cwl#main

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

Path: cwltool/schemas/v1.0/v1.0/search.cwl

Branch/Commit ID: b82ce7ae901a54c7a062fd5eefd8d5ceb5a4d684

Packed ID: main

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: 7ced5a5259dbd8b3fc64456beaeffd44f4a24081

workflow graph Build STAR indices

Workflow runs [STAR](https://github.com/alexdobin/STAR) v2.5.3a (03/17/2017) PMID: [23104886](https://www.ncbi.nlm.nih.gov/pubmed/23104886) to build indices for reference genome provided in a single FASTA file as fasta_file input and GTF annotation file from annotation_gtf_file input. Generated indices are saved in a folder with the name that corresponds to the input genome.

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

Path: workflows/star-index.cwl

Branch/Commit ID: 4a80f5b8f86c83af39494ecc309b789aeda77964

workflow graph assemble.cwl

Assemble a set of reads using SKESA

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

Path: assemble.cwl

Branch/Commit ID: 8ea3637b0f11eac1ea5599c41d74e00d85fb778d

workflow graph Varscan Workflow

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

Path: definitions/subworkflows/varscan_germline.cwl

Branch/Commit ID: ffab5424bb8b5905aecf6f8e2e6387da7f3df562

workflow graph DESeq2 (LRT) - differential gene expression analysis using likelihood ratio test

Runs DESeq2 using LRT (Likelihood Ratio Test) ============================================= The LRT examines two models for the counts, a full model with a certain number of terms and a reduced model, in which some of the terms of the full model are removed. The test determines if the increased likelihood of the data using the extra terms in the full model is more than expected if those extra terms are truly zero. The LRT is therefore useful for testing multiple terms at once, for example testing 3 or more levels of a factor at once, or all interactions between two variables. The LRT for count data is conceptually similar to an analysis of variance (ANOVA) calculation in linear regression, except that in the case of the Negative Binomial GLM, we use an analysis of deviance (ANODEV), where the deviance captures the difference in likelihood between a full and a reduced model. When one performs a likelihood ratio test, the p values and the test statistic (the stat column) are values for the test that removes all of the variables which are present in the full design and not in the reduced design. This tests the null hypothesis that all the coefficients from these variables and levels of these factors are equal to zero. The likelihood ratio test p values therefore represent a test of all the variables and all the levels of factors which are among these variables. However, the results table only has space for one column of log fold change, so a single variable and a single comparison is shown (among the potentially multiple log fold changes which were tested in the likelihood ratio test). This indicates that the p value is for the likelihood ratio test of all the variables and all the levels, while the log fold change is a single comparison from among those variables and levels. **Technical notes** 1. At least two biological replicates are required for every compared category 2. Metadata file describes relations between compared experiments, for example ``` ,time,condition DH1,day5,WT DH2,day5,KO DH3,day7,WT DH4,day7,KO DH5,day7,KO ``` where `time, condition, day5, day7, WT, KO` should be a single words (without spaces) and `DH1, DH2, DH3, DH4, DH5` correspond to the experiment aliases set in **RNA-Seq experiments** input. 3. Design and reduced formulas should start with **~** and include categories or, optionally, their interactions from the metadata file header. See details in DESeq2 manual [here](https://bioconductor.org/packages/release/bioc/vignettes/DESeq2/inst/doc/DESeq2.html#interactions) and [here](https://bioconductor.org/packages/release/bioc/vignettes/DESeq2/inst/doc/DESeq2.html#likelihood-ratio-test) 4. Contrast should be set based on your metadata file header and available categories in a form of `Factor Numerator Denominator`, where `Factor` - column name from metadata file, `Numerator` - category from metadata file to be used as numerator in fold change calculation, `Denominator` - category from metadata file to be used as denominator in fold change calculation. For example `condition WT KO`.

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

Path: workflows/deseq-lrt.cwl

Branch/Commit ID: a409db2289b86779897ff19003bd351701a81c50

workflow graph bact_get_kmer_reference

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

Path: task_types/tt_bact_get_kmer_reference.cwl

Branch/Commit ID: 42df0c0f9a4e5697abadd9cb52440691fafc8f5d