| − | As the software is almost perfect, there are few bugs and little need for enhancements.<br /><br /><span style="font-weight: bold;">Found/requested 3/22<br /></span><br />1. I expected chip or no chip specified to determine whether gene symbols/titles showed up in gene set detail report. Ran GSEA with p53, native, no chip, and got no gene symbol as expected. Added chip and got gene symbol as expected.<span style="font-weight: bold;"><span style="font-weight: bold;"> </span></span>But, then removed chip and still got the gene symbols (as if they were stored in memory or something). Parameters on the report confirm that I did not have chip specified. All three reports (nochip, chip, and chip_nochip) are in dropbox/foraravind.<br /><br />2. Created my own gene set file, one gene set with text description and another with URL. Ran GSEA. The Enrichment Result report tries to link my gene sets to MSigDB rather than using my descriptions. (That report also on the dropbox/foraravind.)<br /><br /><br /><br /><br /><span style="font-weight: bold;"><span style="font-weight: bold;" /><br /><br />Feature Additions for build 3/2</span>1<br /><br />1. Leading edge interactive viewer<br />2. Added a preferences field for path to user home dir.<br />3. made native the default space in gsea. Not sure if this is better??<br /> <span style="color: rgb(0, 0, 255);"> I prefer gene_symbol since that's what we recommend.</span><br />4. default collection of gene sets available via ftp<br /><br /><span style="font-weight: bold;">Found/requested 3/17:</span><br /><br />1. Add Command button to Leading Edge page.<br /><br /><span style="color: rgb(255, 0, 0);">Cant do this easilly because of the way the command thing is setup.<br /><span style="color: rgb(0, 0, 255);">You said you could do this after all.</span><br /></span><br />2. Leading edge from command line give me fatal errors:<br /> 719 [FATAL] Could not make dir: C:\Documents and Settings\hkuehn\.xtools_home\databases at <br /> edu.mit.broad.xbench.core.api.VdbManagerImpl._mkdir(VdbManagerImpl.java:89)<br /> 719 [FATAL] Could not make dir: C:\Documents and Settings\hkuehn\.xtools_home\chip2chip at <br /> edu.mit.broad.xbench.core.api.VdbManagerImpl._mkdir(VdbManagerImpl.java:89)<br /> 799 [FATAL] Could not make dir: C:\Documents and Settings\hkuehn\.xtools_home\reports_cache_foo at<br /> edu.mit.broad.xbench.core.api.VdbManagerImpl._mkdir(VdbManagerImpl.java:89)<br /><br />Must set -DGSEA=true flag<br />So,<br /><br /> <pre>java -Xmx ... -DGSEA=true xtools.....</pre> <br /><br />3. MSigDB page, the Find sets that Overlap search gives page with no Export button; make that page more like the<br /> Find sets that contain this gene page.<br /><br /><span style="color: rgb(255, 153, 0);">Joshs reworked impl will replace this and the export option should be added to it</span><br /><br />4. On Run GSEA, change parameter name from "Analyze in the feature space" to "Gene/probe identifier format"<br /><br /><span style="color: rgb(255, 0, 0);">Lets talk. <span style="color: rgb(0, 0, 255);">Forgot to bring this up in our last chat.</span></span><br /><br />5. Remove Downloads>Download Gene Sets (no longer needed now that we have MSigDB page).<br /><br /><span style="color: rgb(51, 153, 102);">Done</span><br /><br />6. Change first two Help items to "GSEA web site" and "GSEA documentation". First points to home page of web site and<br /> second points to the doc page of the web site.<br /><br /><span style="color: rgb(51, 153, 102);">Done</span><br /><br /><span style="font-weight: bold;">Bugs found 3/15/2006 include:</span><br /><br />1. Generate a report, go to "Other" section, look at parameters. Error, file cannot be found.<br /><br />Fixed.<br /><br />2. Started a pretty long analysis, killed it. It took a few minutes versus a few seconds. If that's expected, perhaps change message to say may take a few minutes.<br /><br />Whats a long analysis? (for leading edge clustering more than a handful of sets, say 20, is likely pointless)<br /><br />3. Leading edge report brings up the gct files in a text editor rather than Excel; can't really read them in a text editor.<br /><br />Opening gct files now works like this: First check prefs to see if excel (or the other programs) exist at location indicated in the prefs. If so, use it. Otherwise issue a generic open file command in windows that will open up the file in whatever editor has been registered by windows for that file type. On the mac, the later mode is always done. On unix i dont know what will happen.
| + | <p><span style="font-weight: bold;"><br /></span>We are now using [http://bugzilla.broad.mit.edu/gsea/ Bugzilla] to record and track GSEA bugs. <br /></p> |
