Difference between revisions of "GSEA v2.08. Release Notes"

From GeneSetEnrichmentAnalysisWiki
Jump to navigation Jump to search
Line 8: Line 8:
 
</li>
 
</li>
 
<li><p>In the previous version of GSEA, there were display issues when viewing the selection menu of .gmt files in the MSigDB database from the <em>Run Gsea</em> screen and the <em>Chip2Chip mapping</em> screen. These issues have now been fixed and it is now clearer which files correspond to the latest MSigDB as they are now always displayed at the top of the list and in a bold font. </p>
 
<li><p>In the previous version of GSEA, there were display issues when viewing the selection menu of .gmt files in the MSigDB database from the <em>Run Gsea</em> screen and the <em>Chip2Chip mapping</em> screen. These issues have now been fixed and it is now clearer which files correspond to the latest MSigDB as they are now always displayed at the top of the list and in a bold font. </p>
 +
</li>
 +
<li><p>The latest version of MSigDB is significantly larger than previous versions and we now recommend that you run GSEA with no less than 1 GB of memory. If you run GSEA from the command line, use the -Xmx Java option to specify increased heap size.  For example, <tt>java -Xmx1024m -jar gsea2-2.08.jar</tt>.</p>
 
</li>
 
</li>
 
</ol>
 
</ol>

Revision as of 15:51, 14 October 2012

In release 2.0.8, there is no change to the GSEA algorithm.

The changes include:

  1. When you Browse MSigDB, by default it will now display version 3.1 of the MSigDB gene sets.

    To browse earlier versions of MSigDB, type msigdb_v3.xml or msigdb_v2.5.xml in the File path or URL to the MSigDB database and click the Load database button.

    Loading MSigDB3.1.jpg


  2. In the previous version of GSEA, there were display issues when viewing the selection menu of .gmt files in the MSigDB database from the Run Gsea screen and the Chip2Chip mapping screen. These issues have now been fixed and it is now clearer which files correspond to the latest MSigDB as they are now always displayed at the top of the list and in a bold font.

  3. The latest version of MSigDB is significantly larger than previous versions and we now recommend that you run GSEA with no less than 1 GB of memory. If you run GSEA from the command line, use the -Xmx Java option to specify increased heap size. For example, java -Xmx1024m -jar gsea2-2.08.jar.