Explore Workflows

GSEAPY: Gene Set Enrichment Analysis in Python ============================================== Gene Set Enrichment Analysis is a computational method that determines whether an a priori defined set of genes shows statistically significant, concordant differences between two biological states (e.g. phenotypes). GSEA requires as input an expression dataset, which contains expression profiles for multiple samples. While the software supports multiple input file formats for these datasets, the tab-delimited GCT format is the most common. The first column of the GCT file contains feature identifiers (gene ids or symbols in the case of data derived from RNA-Seq experiments). The second column contains a description of the feature; this column is ignored by GSEA and may be filled with “NA”s. Subsequent columns contain the expression values for each feature, with one sample's expression value per column. It is important to note that there are no hard and fast rules regarding how a GCT file's expression values are derived. The important point is that they are comparable to one another across features within a sample and comparable to one another across samples. Tools such as DESeq2 can be made to produce properly normalized data (normalized counts) which are compatible with GSEA.

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

Path: workflows/gseapy.cwl

Branch/Commit ID: a839eb6390974089e1a558c49fc07b4c66c50767

Pairwise comparison

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

Path: task_types/tt_kmer_compare_wnode.cwl

Branch/Commit ID: 5e92165ac2c11608ab2db42fe2d66eabe72dbb40

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

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

Path: workflows/rnaseq-pe-dutp.cwl

Branch/Commit ID: 1131f82a53315cca217a6c84b3bd272aa62e4bca

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

Path: cwltool/schemas/v1.0/v1.0/count-lines6-wf.cwl

Branch/Commit ID: 047e69bb169e79fad6a7285ee798c4ecec3b218b

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

Path: task_types/tt_kmer_ref_compare_wnode.cwl

Branch/Commit ID: 7f857f7f2d7c080d27c775b67a6d6f7d94bce31f

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.

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

Path: workflows/cellranger-aggr.cwl

Branch/Commit ID: a839eb6390974089e1a558c49fc07b4c66c50767

### Devel version of QuantSeq 3' FWD, FWD-UMI or REV for single-read mRNA-Seq data

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

Path: workflows/trim-quantseq-mrnaseq-se-strand-specific.cwl

Branch/Commit ID: 9d5cbdd3ea0bb417518115d8092584254598a440

https://github.com/MGuevaraO/qsm_pipeline.git

Path: qsm_pipeline_v1.cwl

Branch/Commit ID: 882e36d61371650b06fe1a839a84c488ccdcf77f

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

Path: definitions/subworkflows/single_sample_sv_callers.cwl

Branch/Commit ID: 441b85003fdc10cf4cbf333d89acb4d23b0fef32

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

Path: progs/gp_makeblastdb.cwl

Branch/Commit ID: 664e99a23a3ed4ba36c08323ac597c4fbcd88df1