Known Issues

From GeneSetEnrichmentAnalysisWiki

(Difference between revisions)
Jump to: navigation, search
Line 43: Line 43:
Solution</strong>: Corrected in GSEA v2.0.1.<br />
Solution</strong>: Corrected in GSEA v2.0.1.<br />
<hr width="100%" size="2" />
<hr width="100%" size="2" />
<h3>Error in log while running GSEA</h3>
<h3>&quot;No probe called&quot; error in log while running GSEA</h3>
<p><strong>Problem</strong>: When you run GSEA, sometimes the following errors appear in the log file:</p>
<p><strong>Problem</strong>: When you run GSEA, sometimes the following errors appear in the log file:</p>
<p>ERROR - No Probe called: USP9X /// USP9Y on this chip (chip name is &gt;GENE_SYMBOL&lt;)<br />
<p>ERROR - No Probe called: USP9X /// USP9Y on this chip (chip name is &gt;GENE_SYMBOL&lt;)<br />

Revision as of 17:18, 29 February 2008

<a href="">GSEA Home</a> | <a href="">Downloads</a> | <a href="">Molecular Signatures Database</a> | Documentation | <a href="">Contact</a>


GSEA version 2

Error in memory.size when running GSEA-R

Problem: When running the example programs provided for R, the following error occurs:


[1] " *** Running GSEA Analysis..."<br />Error in memory.size(size) : don't be silly!: your machine has a 4Gb address limit

Solution: This is produced by the following line early in the GSEA.1.R file:



This line set the memory limit to a large size as a work around to a platform problem with an earlier R version.
The easiest fix is just to comment out that line:

 #      memory.limit(6000000000)

This will allocate the default amount of memory. If after this change the program runs out of memory, change the line to:

 memory.limit(max. size in Mbytes available)

Firewall / FTP connection issues for CHIP annotations or Gene Set Databases

Problem: When you try to access the CHIP annotation files or the Gene Set Database / MSigDB Browser you see an error t the effect: "Error listing Broad website//  Connection reset//"

Cause: This is probably because you are behind a network firewall or someother network configuration that prevents you from accessing FTP servers on port 500. The Broad chip files and gene sets are placed on a publically accessible Broad FTP server. The GSEA Java Desktop program tries to access the Broad FTP site to provide you easy access to the files but the network configuration blocks access.

Work-around: (1) See if you can temporarilly disable your firewall when using GSEA (2) Consult with your local network administrator to see if they have any suggestions or prior experience such issues (3) Download the .CHIP, GeneSet databases and MSigDB XML file from the link below to your local file system. Expand it with WinZIP and then load the files into the program as *local files* rather than over the network.

This large ZIP file contains ALL current (as of March 19, 2007) .CHIP annotations, GENE_SET databases and MSigDB.xml file:

<a href=""></a>

We are working on a URL based access for the next release.

Error running leading edge analysis

Problem: When you select a report for leading edge analysis, the following error sometimes occurs:

at org.genepattern.gsea.LeadingEdgeWidget.setData(EIKM)
at xapps.gsea.LeadingEdgeReportWidget.setData(EIKM)
at xapps.gsea.LeadingEdgeReportWidget$
at Source)

: Corrected in GSEA v2.0.1.

"No probe called" error in log while running GSEA

Problem: When you run GSEA, sometimes the following errors appear in the log file:

ERROR - No Probe called: USP9X /// USP9Y on this chip (chip name is >GENE_SYMBOL<)
ERROR - Turning off subsequent error notifications

Solution: You can ignore these errors. The three slashes (///) indicates that the chip file contains ambiguous mappings, where a probe on the chip cannot be mapped to exactly one HUGO gene symbol. GSEA displays this error and ignores these probes.


GSEA version 1

java.lang.OutOfMemoryError (GSEA v1)

Problem: On the Mac, you can run GSEA from the command line, but when you attempt to use the GSEA application from the desktop you receive errors similar to the following:

Full Error Message ----


Stack Trace ----
  1. of exceptions: 1



Solution: Corrected in GSEA v2. In GSEA v1, this is a memory issue with the gsea installer on the Mac. As a workaround, use the following command to launch the GSEA application rather than double clicking the icon:

java -Xmx1800m xapps.gsea.Main

java.lang.NullPointerException (GSEA v1)

Problem: By default, a gene set enrichment analysis uses phenotype permutations. If you have too few samples for phenotype permutation, the following error occurs:

Stack Trace ----
  1. of exceptions: 1


    at xtools.gsea.AbstractGsea2Tool.execute_one(
    at xtools.gsea.AbstractGsea2Tool.execute_one_with_reporting(
    at xtools.gsea.Gsea.execute(
    at Source)

Solution: Corrected in GSEA v2. In GSEA v1, use gene_set permutation rather than phenotype permutation. For more information, see the description of the Permutation type parameter on the Run GSEA Page in the GSEA User Guide.

GSEA on Linux

Browser links do not work under Linux

Problem: When running the GSEA desktop application under Linux, buttons and links that would normally open a browser window do not open the browser window.

Work-around: After running an analysis, you cannot click on the Success link to display the result. However, you can go to the directory that contains the analysis report output and open the index.html file in that directory.

Personal tools