Difference between revisions of "Gsea enhancements"

From GeneSetEnrichmentAnalysisWiki
Jump to navigation Jump to search
 
(82 intermediate revisions by 3 users not shown)
Line 1: Line 1:
As the software is almost perfect, there are few bugs and little need for enhancements.<br /><br />Bugs found 3/15/2006 include:<br /><br />1. Generate a report, go to &quot;Other&quot; 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>
 +
<p>Bugs from this page that were verified/rejected before we started using Bugzilla, can be found in  [http://wwwdev.broad.mit.edu/gsea/doc/GSEA_enh_history.doc GSEA_enh_history.doc].<br /><span style="font-weight: bold;"></span><span style="color: rgb(255, 0, 255);"></span><br /></p>

Latest revision as of 14:04, 16 May 2006


We are now using Bugzilla to record and track GSEA bugs.

Bugs from this page that were verified/rejected before we started using Bugzilla, can be found in GSEA_enh_history.doc.