Difference between revisions of "MSigDB v6.0 Release Notes"

From GeneSetEnrichmentAnalysisWiki
Jump to navigation Jump to search
Line 14: Line 14:
 
<li> Updated information of one set at the request of its contributor, Dr. Dimitris Anastassiou (Columbia University).  
 
<li> Updated information of one set at the request of its contributor, Dr. Dimitris Anastassiou (Columbia University).  
 
<li> Amended errors in two BASSO_HAIRY_CELL_LEUKEMIA set.
 
<li> Amended errors in two BASSO_HAIRY_CELL_LEUKEMIA set.
 +
 +
<h2> Changes to C5 collection - oncogenic signatures</h2>
 +
<p> Grouping sets by gene ontology (GO) terms can potentially produce identical sets for different GO terms. We have a procedure in place to detect and resolve these cases. Unfortunately, in the previous release of the database, several identical sets slipped through. Alerted by astute users of MSigDB (thank you!), we improved the procedure and were able to identify and eliminate 249 duplicate sets. </p>

Revision as of 20:23, 5 April 2017

GSEA Home | Downloads | Molecular Signatures Database | Documentation | Contact

This page describes the changes made to the gene set collections for Release 6.0 of the Molecular Signatures Database (MSigDB).

Change of license terms

MSigDB v6.0 is now available under a Creative Commons license, plus additional terms for some sub-collections of gene sets. Note however that earlier versions of MSigDB are still under the older license terms. See the License Term page for details.

Updates to C2:CGP - curated gene sets

  • Added two sets (submitted by Dr. Quintens Roel, Belgian Nuclear Research Centre).
  • Updated information of one set at the request of its contributor, Dr. Dimitris Anastassiou (Columbia University).
  • Amended errors in two BASSO_HAIRY_CELL_LEUKEMIA set.

    Changes to C5 collection - oncogenic signatures

    Grouping sets by gene ontology (GO) terms can potentially produce identical sets for different GO terms. We have a procedure in place to detect and resolve these cases. Unfortunately, in the previous release of the database, several identical sets slipped through. Alerted by astute users of MSigDB (thank you!), we improved the procedure and were able to identify and eliminate 249 duplicate sets.