Explore Workflows
View already parsed workflows here or click here to add your own
Graph | Name | Retrieved From | View |
---|---|---|---|
|
gcaccess_from_list
|
![]() Path: task_types/tt_gcaccess_from_list.cwl Branch/Commit ID: bba6c580ab88e077f6aa2c2ee7c73159f3f9156e |
|
|
downsample unaligned BAM and align
|
![]() Path: definitions/subworkflows/downsampled_alignment.cwl Branch/Commit ID: ffd73951157c61c1581d346628d75b61cdd04141 |
|
|
bam_readcount workflow
|
![]() Path: definitions/subworkflows/bam_readcount.cwl Branch/Commit ID: ffd73951157c61c1581d346628d75b61cdd04141 |
|
|
cluster_blastp_wnode and gpx_qdump combined
|
![]() Path: task_types/tt_cluster_and_qdump.cwl Branch/Commit ID: 7f857f7f2d7c080d27c775b67a6d6f7d94bce31f |
|
|
RNA-Seq pipeline paired-end
The original [BioWardrobe's](https://biowardrobe.com) [PubMed ID:26248465](https://www.ncbi.nlm.nih.gov/pubmed/26248465) **RNA-Seq** basic analysis for a **paired-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 paired-end RNA-Seq data. It performs the following steps: 1. Use STAR to align reads from input FASTQ files according to the predefined reference indices; generate unsorted BAM file and alignment statistics file 2. Use fastx_quality_stats to analyze input FASTQ files and generate quality statistics files 3. Use samtools sort to generate coordinate sorted BAM(+BAI) file pair from the unsorted BAM file obtained on the step 1 (after running STAR) 4. Generate BigWig file on the base of sorted BAM file 5. Map input FASTQ files to predefined rRNA reference indices using Bowtie to define the level of rRNA contamination; export resulted statistics to file 6. Calculate isoform expression level for the sorted BAM file and GTF/TAB annotation file using GEEP reads-counting utility; export results to file |
![]() Path: workflows/rnaseq-pe.cwl Branch/Commit ID: 4a5c59829ff8b9f3c843e66e3c675dcd9c689ed5 |
|
|
Workflow to run pVACseq from detect_variants and rnaseq pipeline outputs
|
![]() Path: definitions/subworkflows/pvacseq.cwl Branch/Commit ID: 441b85003fdc10cf4cbf333d89acb4d23b0fef32 |
|
|
Raw sequence data to BQSR
|
![]() Path: definitions/subworkflows/sequence_to_bqsr.cwl Branch/Commit ID: a7838a5ca72b25db5c2af20a15f34303a839980e |
|
|
tt_blastn_wnode
|
![]() Path: task_types/tt_blastn_wnode.cwl Branch/Commit ID: f5c11df465aaadf712c38ba4933679fe1cbe03ca |
|
|
RNA-Seq pipeline paired-end stranded mitochondrial
Slightly changed original [BioWardrobe's](https://biowardrobe.com) [PubMed ID:26248465](https://www.ncbi.nlm.nih.gov/pubmed/26248465) **RNA-Seq** basic analysis for **strand specific pair-end** experiment. An additional steps were added to map data to mitochondrial chromosome only and then merge the output. Experiment files in [FASTQ](http://maq.sourceforge.net/fastq.shtml) format either compressed or not can be used. Current workflow should be used only with the pair-end strand specific RNA-Seq data. It performs the following steps: 1. `STAR` to align reads from input FASTQ file according to the predefined reference indices; generate unsorted BAM file and alignment statistics file 2. `fastx_quality_stats` to analyze input FASTQ file and generate quality statistics file 3. `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 file 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 |
![]() Path: workflows/rnaseq-pe-dutp-mitochondrial.cwl Branch/Commit ID: 1131f82a53315cca217a6c84b3bd272aa62e4bca |
|
|
Cellranger aggr - aggregates data from multiple Cellranger runs
Devel version of Single-Cell Cell Ranger Aggregate ================================================== Workflow calls \"cellranger aggr\" command to combine output files from \"cellranger count\" (the molecule_info.h5 file from each run) into a single feature-barcode matrix containing all the data. When combining multiple GEM wells, the barcode sequences for each channel are distinguished by a GEM well suffix appended to the barcode sequence. Each GEM well is a physically distinct set of GEM partitions, but draws barcode sequences randomly from the pool of valid barcodes, known as the barcode whitelist. To keep the barcodes unique when aggregating multiple libraries, we append a small integer identifying the GEM well to the barcode nucleotide sequence, and use that nucleotide sequence plus ID as the unique identifier in the feature-barcode matrix. For example, AGACCATTGAGACTTA-1 and AGACCATTGAGACTTA-2 are distinct cell barcodes from different GEM wells, despite having the same barcode nucleotide sequence. This number, which tells us which GEM well this barcode sequence came from, is called the GEM well suffix. The numbering of the GEM wells will reflect the order that the GEM wells were provided in the \"molecule_info_h5\" and \"gem_well_labels\" inputs. When combining data from multiple GEM wells, the \"cellranger aggr\" pipeline automatically equalizes the average read depth per cell between groups before merging. This approach avoids artifacts that may be introduced due to differences in sequencing depth. It is possible to turn off normalization or change the way normalization is done through the \"normalization_mode\" input. The \"none\" value may be appropriate if you want to maximize sensitivity and plan to deal with depth normalization in a downstream step. |
![]() Path: workflows/cellranger-aggr.cwl Branch/Commit ID: 2c486543c335bb99b245dfe7e2f033f535efb9cf |