|
|
| Line 1: |
Line 1: |
| − | [http://www.broadinstitute.org/gsea/ GSEA Home] | | + | See the [http://software.broadinstitute.org/gsea/msigdb/collections.jsp MSigDB Collections page] on the main website. |
| − | [http://www.broadinstitute.org/gsea/downloads.jsp Downloads] |
| |
| − | [http://www.broadinstitute.org/gsea/msigdb/ Molecular Signatures Database] |
| |
| − | [http://www.broadinstitute.org/cancer/software/gsea/wiki/index.php/Main_Page Documentation] |
| |
| − | [http://www.broadinstitute.org/gsea/contact.jsp Contact]
| |
| − | <br>
| |
| − | <br>
| |
| − | <p>This page provides detailed descriptions of all collections of gene sets in MSigDB.</p>
| |
| − | <p>To learn about changes and other information specific for a particular release of MSigDB, please refer to the corresponding [[Release_Notes]].</p>
| |
| − | | |
| − | <h2>H: hallmark gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v5.0 MSigDB.</p>
| |
| − | | |
| − | <p>We envision this collection as the starting point for exploring MSigDB resource and GSEA.</p>
| |
| − | | |
| − | <p>Hallmark gene sets represent specific well defined biological states or processes and display coherent expression. The hallmark gene sets were generated by a computational methodology based on identifying gene set overlaps and extracting coherent representatives of them. Details of the procedure will become available after the manuscript describing it is accepted for publication. The hallmark gene sets reduce noise and redundancy and provide a better biological space for GSEA and other gene set-based analyses of genomic data.</p>
| |
| − | | |
| − | <p>This collection is an initial release of 50 hallmarks which condense information from over 4,000 original overlapping gene sets from v4.0 MSigDB collections C1 through C6. We refer to the original gene sets as “founder” sets.</p>
| |
| − | | |
| − | <p>Hallmark gene set pages provide links to the corresponding founder sets for more in-depth exploration. In addition, hallmark gene set pages include links to microarray data that served for refining and validation of the hallmark signatures.</p>
| |
| − | | |
| − | <p>To cite your use of the collection, and for further information, please refer to</p>
| |
| − | Liberzon A, Birger C, Thorvaldsdóttir H, Ghandi M, Mesirov JP, Tamayo P.
| |
| − | <br>The Molecular Signatures Database (MSigDB) hallmark gene set collection.
| |
| − | <br>Cell Syst. 2015 Dec 23;1(6):417-425. [http://www.ncbi.nlm.nih.gov/pubmed/26771021 PMID: 26771021]
| |
| − | | |
| − | <h2>C1: positional gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v1.0 MSigDB (the initial release).</p>
| |
| − | | |
| − | <p>Genes from the same genomic location (chromosome or cytogenetic band) are grouped in a gene set. Cytogenetic annotations are from three sources:</p>
| |
| − | <ol>
| |
| − | <li>[http://www.genenames.org Human Genome Organization (HUGO) Gene Nomenclature Committee (HGNC)]</li>
| |
| − | <li>[http://www.ncbi.nlm.nih.gov/unigene/ UniGene]</li>
| |
| − | <li>[http://www.affymetrix.com Affymetrix] microarray annotations</li>
| |
| − | </ol>
| |
| − | <p>We merged the relevant annotations from these resources and derived a single cytogenetic band location for every gene symbol. These were then grouped into sets. Decimals in cytogenetic bands were ignored. For example, 5q31.1 was considered 5q31. Therefore, genes annotated as 5q31.2 and those annotated as 5q31.3 were both placed in the same set, 5q31.</p>
| |
| − | <p>When there were conflicts, the UniGene entry was used.</p>
| |
| − | <p>These sets are helpful in identifying effects related to chromosomal deletions or amplifications, dosage compensation, epigenetic silencing, and other regional effects.</p>
| |
| − | | |
| − | <h2>C2: curated gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v1.0 MSigDB (the initial release).</p>
| |
| − | | |
| − | Gene sets collected from various sources such as online pathway databases, scientific publications and personal contributions from domain experts.
| |
| − | <h3>CGP: chemical and genetic perturbations</h3>
| |
| − | <ul>
| |
| − | <li>Sets curated from biomedical literature
| |
| − | <p>Over the past few years, microarray studies have identified signatures of several important biological and clinical states (e.g. cancer metastasis, stem cell characteristics, drug resistance). These gene sets are valuable biological results. Unfortunately, because gene sets are typically published as tables in a paper, the important biological findings they represent are not easily accessible to computational tools. Our first goal was to convert published gene sets into an electronic form. Towards this we compiled a list of microarray articles with published gene expression signatures. From each article, we extracted one or more gene sets from tables in the main text or supplementary information. Notably, our focus was on capturing the identity (e.g. gene symbol, GenBank accession) of all members in a gene set rather than on relationships between individual genes.</p>
| |
| − | <p>A number of these gene sets come in pairs: an xxx_UP (xxx_DN) gene set representing genes induced (repressed) by the perturbation.</p>
| |
| − | <p>Names of CGP sets start with the last name of the first author of the source publication. The majority of CGP sets were curated from publications and include links to the [http://www.ncbi.nlm.nih.gov/pubmed PubMed] citation, the exact source of the set (e.g., Table 1) and links to the corresponding raw data in [http://www.ncbi.nlm.nih.gov/geo/ GEO] or [http://www.ebi.ac.uk/arrayexpress/ ArrayExpress] repositories. When the set involves a genetic perturbation, brief description includes a link to the gene's entry in the NCBI [http://www.ncbi.nlm.nih.gov/gene Entrez Gene] database. When the set involves a chemical perturbation, brief description includes a link to the chemical's entry in the NCBI [ PubChem Compound] database.</p>
| |
| − | <ul>
| |
| − | <li>curated by the MSigDB curation team</li>
| |
| − | <li>contributed by the [http://depts.washington.edu/l2l/ L2L] database</li>
| |
| − | <p>These sets came from the [http://depts.washington.edu/l2l/ L2L] database of published microarray gene expression data (described in [http://genomebiology.com/2005/6/9/R81 Newman and Weiner]) and were kindly shared with MSigDB. These sets list John Newman as the contributor.</p>
| |
| − | </ul>
| |
| − | </li>
| |
| − | <li>Sets contributed by Dr. Chi Dang from the [http://www.myccancergene.org/site/mycTargetDB.asp MYC Target Gene Database].</li>
| |
| − | <li>Individual gene set compilations contributed by MSigDB collaborators. These sets usually are not based on any specific publication.</li>
| |
| − | </ul>
| |
| − | | |
| − | <h3>CP: canonical pathways</h3>
| |
| − | Gene sets from the pathway databases. Usually, these gene sets are canonical representations of a biological process compiled by domain experts. These gene sets were either extracted from the online sources by MSigDB curation team or were contributed by teams of pathway databases in collaboration with MSigDB curation team.
| |
| − | <ul>
| |
| − | <li>[http://www.biocarta.com/ BioCarta]</li>
| |
| − | <li>[http://www.genome.jp/kegg KEGG]</li>
| |
| − | <li>[http://matrisomeproject.mit.edu Matrisome Project]</li>
| |
| − | <li>[http://pid.nci.nih.gov/ Pathway Interaction Database (PID)]</li>
| |
| − | <li>[http://www.reactome.org/ Reactome]</li>
| |
| − | <li>[http://www.sigmaaldrich.com/life-science.html SigmaAldrich]</li>
| |
| − | <li>[http://www.signaling-gateway.org/ Signaling Gateway]</li>
| |
| − | <li>[http://stke.sciencemag.org/ Signal Transduction KE (STKE)]</li>
| |
| − | <li>[http://www.superarray.com/ SuperArray]</li>
| |
| − | </ul>
| |
| − | | |
| − | <h2>C3: motif gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v1.0 MSigDB (the initial release).</p>
| |
| − | | |
| − | <p>Gene sets group genes by <i>cis</i>-regulatory motifs. The motifs are catalogued in [http://www.nature.com/nature/journal/v434/n7031/abs/nature03441.html Xie et al.] and represent known or putative conserved regulatory elements in promoters and 3’-UTR regions. These sets make it possible to link changes in a genomic experiment to a conserved, putative cis-regulatory elements.</p>
| |
| − | <h4>Transcription factor targets (TFT)</h4>
| |
| − | <p>These sets share upstream <i>cis</i>-regulatory motifs which can function as potential transcripton factor binding sites. We used two approaches to generate these gene sets.</p>
| |
| − | <p>Motif gene sets of ‘conserved instances’ consist of the inferred target genes for each motif <strong>m</strong> of 174 upstream motifs highly conserved among five mammalian species (<i>H. sapiens</i>, <i>M. musculus</i>, <i>R. norvegicus</i> and <i>C. lupus familiaris</i>). The motifs are catalogued in [http://www.ncbi.nlm.nih.gov/pubmed/15735639 Xie, et al. (2005, Nature 434, 338–345)] and represent potential transcription factor binding sites. Each motif gene set consists of all human genes whose promoters (defined as regions -2kb to +2kb around transcription start site) contained at least one conserved instance of motif <strong>m</strong>. If the motif’s sequence matched a transcription factor binding site documented in v7.4 [http://www.gene-regulation.com/ TRANSFAC] database, then we appended the name of the TRANSFAC binding matrix to the motif sequence in the gene set name, e.g.: MOTIFSEQ_FOO, where MOTIFSEQ is the sequence of motif <strong>m</strong> and FOO is the TRANSFAC matrix name (e.g., V$MIF1_01). The set’s full description in this case is the TRANSFAC entry for the matching matrix. If the motif’s sequence matched no transcription factor binding site from TRANSFAC v.7.4, then we named the set as MOTIFSEQ_UNKNOWN where MOTIFSEQ is the consensus sequence of motif <strong>m</strong>.</p>
| |
| − | <p>We also extracted 460 mammalian transcriptional regulatory motifs from v7.4 [http://www.gene-regulation.com/ TRANSFAC] database. We then generated the motif gene sets consisting of the inferred target genes for each motif. Every such set consists of human genes whose promoters (defined as regions -2kb to +2kb around transcription start site) contain at least one instance of the motif. We named these sets by the corresponding TRANSFAC matrix identifiers, e.g., V$MIF1_01. The set’s full description is the TRANSFAC entry for the matching matrix, in a format described [http://www.gene-regulation.com/pub/databases/transfac/doc/matrix1SM.html here].</p>
| |
| − | <p>Brief descriptions of sets in this collection follow this syntax: "Genes with promoter regions [-2kb,2kb] around transcription start site containing motif MOTIFSEQ". If the motif's sequence matched a TRANSFAC binding matrix and the name of the matrix corresponded to a human gene symbol, then the text continued as follows: "... which matches annotation for GENE_SYMBOL: FULL GENE NAME." Otherwise, the text continues as follows: "Motif does not match any known transcription factor".</p>
| |
| − | | |
| − | <h4>microRNA Targets (MIR)</h4>
| |
| − | <p>These gene sets consist of the inferred target gene for each motif <strong>m</strong> of 221 3'-UTR motifs highly conserved among five mammalian species (<i>H. sapiens</i>, <i>M. musculus</i>, <i>R. norvegicus</i> and <i>C. lupus familiaris</i>). The motifs are catalogued catalogued in [http://www.ncbi.nlm.nih.gov/pubmed/15735639 Xie, et al. 2005, Nature 434, 338–345] and represent potential microRNA binding sites. Each motif gene set consists of all genes whose 3’-UTR contained at least one conserved instance of motif <strong>m</strong>.</p>
| |
| − | | |
| − | <h2>C4: computational gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v1.0 MSigDB (the initial release).</p>
| |
| − | | |
| − | Gene sets defined by mining large collections of cancer-oriented genes.
| |
| − | | |
| − | <h5>CGN: Cancer Gene Neighborhoods</h5>
| |
| − | These sets are defined by expression neighborhoods centered on cancer-related genes. This collection has originally been described in [http://www.pnas.org/content/102/43/15545.abstract Subramanian, Tamayo et al. 2005].
| |
| − | | |
| − | Starting with a list of 380 cancer associated genes curated from internal resources and a published cancer gene database [REF], [http://www.pnas.org/content/102/43/15545.abstract Subramanian, Tamayo et al. 2005] mined four expression compendia datasets for correlated gene sets. Using the profile of a given gene as a template, Subramanian and Tamayo ordered every other gene in the data set by its Pearson correlation coefficient. A cutoff of <i>R</i> ≤ 0.85 was then applied to extract correlated genes. The calculation of neighborhoods was done independently in each data set. In this way, a given oncogene may have up to four "types" of neighborhoods according to the correlation present in each compendium. Neighborhoods with ≶ 25 genes at this threshold were omitted yielding the final 427 sets.
| |
| − | <p>The names of these gene sets start with a code indicating the corresponding expression compendium followed by the symbol of the cancer associated gene.</p>
| |
| − | <p>The compendia and their codes are listed below:</p>
| |
| − | <ul>
| |
| − | <li><strong>GNF2</strong> [http://www.pnas.org/content/101/16/6062.abstract Novartis normal tissue compendium]</li>
| |
| − | <li><strong>CAR</strong> [http://cancerres.aacrjournals.org/content/61/20/7388.abstract Novartis carcinoma compendium]</li>
| |
| − | <li><strong>GCM</strong> [http://www.pnas.org/content/98/26/15149.abstract Global cancer map]</li>
| |
| − | <li><strong>MORF</strong> [http://www.pnas.org/content/102/43/15545.abstract GSEA PNAS 2005]</li>
| |
| − | <p>An internal compendium of gene expression data sets, including many of Broad Institute's Cancer Program in-house Affymetrix HG-U95 cancer samples (1,693 in all) from a variety of cancer projects representing many different tissue types, mainly primary tumors, such as prostate, breast, lung, lymphoma, leukemia, etc.</p>
| |
| − | </ul>
| |
| − | | |
| − | <h5>CM: Cancer Modules</h5>
| |
| − | | |
| − | <p>First introduced in v2.5 MSigDB.</p>
| |
| − | | |
| − | <p>Gene sets are <i>identical</i> to the modules described in [http://www.nature.com/ng/journal/v36/n10/abs/ng1434.html Segal et al]. Starting with 2,849 gene sets from a variety of resources such as KEGG, Gene Ontology, and others, the authors mined a large compendium of cancer related microarray data and identified 456 transcriptionally co-regulated modules. Two sets with fewer than 10 NCBI human Entrez Gene IDs have been deprecated since v3.0 MSigDB.</p>
| |
| − | <p>The names of these sets start with MODULE_ followed by the number of module according to the contributor's notes. Gene set pages contain external links to further details about these sets.</p>
| |
| − | | |
| − | <h2>C5: GO gene sets</h2>
| |
| − | | |
| − | <p>First introduced in v2.5 MSigDB. The collection underwent complete overhaul in v5.2 MSigDB.</p>
| |
| − | | |
| − | <p> Gene sets in this collection are derived from the controlled vocabulary of the [http://www.geneontology.org Gene Ontology (GO)] project.</p>
| |
| − | <p>The Gene Ontology project is a collaborative effort to develop and use ontologies to support biologically meaningful annotation of genes and their products. Each entry in GO (a GO term) has a unique numerical identifier of the form <tt>GO:nnnnnnn</tt>, and a term name. Each term belongs to one of the three ontologies, <tt>molecular function</tt>, <tt>cellular component</tt> or <tt>biological process</tt>. The ontologies are structured as directed acyclic graphs that represent a network in which a child (i.e., more specialized) term can have one or more parents (i.e., less specialized) terms. Every GO term must obey the <tt>true path rule</tt>: if the child term describes a gene product, then all its parent terms must also apply to that gene product. Annotation is the process of assigning GO terms to gene products. A GO annotation consists of a GO term associated with a specific reference that describes the work or analysis upon which the association between a specific GO term and gene product is based. Each annotation must also include an [http://www.geneontology.org/GO.evidence.shtml evidence code] to indicate how the annotation to a particular term is supported. A gene product might be associated with several GO terms.</p>
| |
| − | <p>There are three sub-collections according to three key biological domains in GO.</p>
| |
| − | <h5>CC: GO Cellular component.</h5>
| |
| − | Gene sets grouped by GO terms from the Cellular Component (CC) ontology. This ontology describes the location of a gene product, within cellular structures and within macromolecular complexes.
| |
| − | <h5>MF: GO Molecular function.</h5>
| |
| − | Gene sets grouped by GO terms from the Molecular Function (MF) ontology. This ontology describes what a gene product does at the biochemical level. It describes only what is done without specifying where or when the event actually occurs or its broader context.
| |
| − | <h5>BP: GO Biological process.</h5>
| |
| − | Gene sets grouped by GO terms from the Biological Process (BP) ontology. This ontology describes a broad biological objective to which the gene product contributes. A process is accomplished via one or more ordered assemblies of functions. It often involves transformation in the sense that something goes into a process and something different comes out of it.
| |
| − | <h5>Outline of the procedure</h5>
| |
| − | <p>All sets are based on associations of GO terms to human genes. Genes annotated with the same GO term make the corresponding GO term gene set.</p>
| |
| − | <p>The input files are:</p>
| |
| − | <ul>
| |
| − | <li><b>gene2go</b>
| |
| − | <p>the file used for v2.5 was downloaded on January 22, 2008)</p>
| |
| − | <p>the file used for v5.2 was downloaded on May 3, 2016</p>
| |
| − | </li>
| |
| − | <p>This file reports GO terms that have been associated with genes in NCBI Entrez Gene. It is generated by processing the gene_association file on the [http://www.geneontology.org/GO.current.annotations.shtml GO FTP site] and comparing the DB_Object_ID to annotation in NCBI Entrez Gene, as also reported in <tt>gene_info.gz</tt>. The file is available [ftp://ftp.ncbi.nih.gov/gene/DATA/ here]. It is a tab delimited plain text file with one <tt>tax_id / gene_id / evidence_code</tt> per line.</p>
| |
| − | <li><b>gene ontology</b>
| |
| − | <p>the file used for v2.5, <b>gene_ontology_edit_obo</b>, was downloaded on January 25, 2008)</p>
| |
| − | <p>the file used for v5.2, <b>go-basic.obo</b>, was downloaded on May 3, 2016</p>
| |
| − | </li>
| |
| − | <p>This file contains the entire GO ontology in OBO v.1.2 format [http://www.geneontology.org/GO.format.obo-1_2.shtml]. The file is produced by Gene Ontology Consortium and is updated every 30 minutes [http://www.geneontology.org/ontology/gene_ontology_edit.obo]. Monthly releases are also available [ftp://ftp.geneontology.org/pub/go/ontology-archive/]. OBO is the plain text file format used by [http://www.oboedit.org/ OBO-Edit], the open source, platform-independent application for viewing and editing ontologies.</p>
| |
| − | </ul>
| |
| − | <h6>v2.5 MSigDB (2008)</h6>
| |
| − | <p>For each GO term we got the corresponding human genes from the gene2go file. For v2.5, we have retrieved only associations with manually assigned evidence codes (IDA, IPI, IMP, IGI, IEP, ISS and TAS) because they usually reflect stronger evidence for the association of a given gene product with the corresponding GO term. Next, we have applied the path rule. Gene products are associated with the most specific GO terms possible. All parent terms up to the root automatically apply to the gene product. Thus, the parent GO term gene sets should include all genes associated with the children GO terms. Then we removed sets with fewer than 10 genes. Next we removed very large sets for extremely broad GO terms by manually inspecting large sets corresponding to GO terms at depths 2 and 3. Finally, we resolve redundancies by applying the following rules:</p>
| |
| − | <ul>
| |
| − | <li>a set equals parental GO term set: keep the parent, discard the child GO term</li>
| |
| − | <li>a set equals many parental GO term sets: keep the child, discard the parent GO terms</li>
| |
| − | <li>equal sets are siblings: discard both</li>
| |
| − | <li>equal sets do not have a child - parent relationship; discard both</li>
| |
| − | </ul>
| |
| − | <h6>v5.2 MSigDB (2016)</h6>
| |
| − | <p>For each GO term we got the corresponding human genes from the gene2go file. No associations were filtered by evidence codes. Instead, we have specifically excluded associations with the root GO terms ([http://amigo.geneontology.org/amigo/term/GO:0008150 GO:0008150], [http://amigo.geneontology.org/amigo/term/GO:0005575 GO:0005575], [http://amigo.geneontology.org/amigo/term/GO:0003674 GO:0003674]) and the 'unknown' GO terms ([http://amigo.geneontology.org/amigo/term/GO:0000004 GO:0000004], [http://amigo.geneontology.org/amigo/term/GO:0005554 GO:0005554], [http://amigo.geneontology.org/amigo/term/GO:0008372 GO:0008372]). Next, we applied the true path rule. Gene products are associated with the most specific GO terms possible. All parent terms up to the root automatically apply to the gene product. Thus, the parent GO term gene sets should include all genes associated with the children GO terms. We then removed sets with fewer than 10 or more than 2,000 Entrez Gene IDs. Finally, we resolved redundancies as follows. We computed <tt>Jaccard's coefficients</tt> for each pair of sets, and marked a pair as highly similar if its <tt>Jaccard's coefficient</tt> was greater than 0.85. We then grouped pairs of highly similar sets into "chunks" according to their GO terms and applied two rounds of filtering for every "chunk". The first round was computational: we kept the largest set in the "chunk" and discarded the smaller sets. This left "chunks" of highly similar pairs of sets of identical sizes, which we further pruned manually by preferably keeping the more general set (i.e., the set with the more general GO term in the ontology tree).</p>
| |
| − | | |
| − | <h2>C6: oncogenic signatures</h2>
| |
| − | <p>First introduced in v3.1 MSigDB.</p>
| |
| − | <p>Gene sets represent signatures of cellular pathways which are often dis-regulated in cancer. The majority of signatures were generated directly from microarray data from NCBI GEO or from in house unpublished expression profiling experiments which involved perturbation of known cancer genes. In addition, a small number of oncogenic signatures was curated from scientific publications.</p>
| |
| − | <h2>C7: immunologic signatures</h2>
| |
| − | | |
| − | <p>First introduced in v4.0 MSigDB, this collection is also called <strong>ImmuneSigDB</strong>, and is a compendium of gene sets that represent cell types, states and perturbations involving the immune system.
| |
| − | </p>
| |
| − | | |
| − | <p>We captured Affymetrix microarray datasets (human or mouse samples) published in the immunology literature that have the data deposited to [http://www.ncbi.nlm.nih.gov/geo Gene Expression Omnibus (GEO)]. We reviewed each microarray dataset in the context of its study and defined meaningful pairwise comparisons (e.g. WT vs. KO; pre- vs. post-treatment etc.) that would lead to biologically useful gene sets. Only meaningful, rather that all possible comparisons, were made. All data was processed uniformly. For each two-class comparison, the genes were ranked according to an information-based similarity metric (RNMI) from top up-regulated to bottom down-regulated genes in the two groups. Gene sets comprised genes differentially expressed with an FDR < 0.02, and a maximum number of genes was set at 200 (i.e., all gene sets had at most 200 differentially expressed genes). This way we generated two gene sets from each assigned comparison of two groups—‘‘Group_A_vs_Group_B_UP’’ and ‘‘Group_A_vs_Group_B_DN,’’ for the top up-regulated and bottom down-regulated genes, respectively, identified for the genes most different in the samples in group A compared to the samples in group B.
| |
| − | </p>
| |
| − | | |
| − | <p>This collection was generated as part of our collaboration with the [http://haining.dfci.harvard.edu Haining Lab] at Dana-Farber Cancer Institute and the [http://www.immuneprofiling.org Human Immunology Project Consortium (HIPC)].</p>
| |
| − | <p>To cite your use of the collection, and for further information, please refer to
| |
| − | <br>Godec J, Tan Y, Liberzon A, Tamayo P, Bhattacharya S, Butte A, Mesirov JP, Haining WN.
| |
| − | <br>Compendium of Immune Signatures Identifies Conserved and Species-Specific Biology in Response to Inflammation.
| |
| − | <br>Immunity. 2016 Jan 19; 44(1): 194-206. [http://www.ncbi.nlm.nih.gov/pubmed/26795250 PMID: 26795250]</p>
| |
