arrowHome
arrowFeatures
arrowFAQ
arrowDocumentation
Download
arrowSystem
arrowRequirements
arrowRegistration
arrowLicense
arrowChangelog
arrowJavadoc
arrowTest Reports
arrowContact Us
arrowAcknowledgments
sidebar2

Frequently Asked Questions


How do I run it?

The software package is distributed as a Java Web Start application so all you have to do to launch the latest version is go to the launch page and click on one of the memory size buttons to run it.

If your locally cached copy is already up-to-date it will launch from your cache; if there is a more recent version available, it will be downloaded to your desktop and launched automatically.


How do I see more debugging information?

You'll need to open the Java Console by going to Start --> Programs --> Java Web Start and starting the Java Web Start applications manager. Then make sure File --> Preferences --> Advanced --> Show Java Console is checked.

Debugging messages to standard error/out will be output on this console.


How do I look at the source code?

We keep track of our source code in a version control system called CVS. If you are an internal developer or outside collaborator, you'll need an account on our CVS server to access the source code and commit changes. For commercial and other for-profit organizations or for academic and other not-for-profit organizations, we will need to make special arrangements, please e-mail Jelai Wang or Dr. Grier Page for details. In general, we will make every effort to accommodate requests for source code.


Where do you keep your specs?

If you are interested in how we've implemented a particular statistical test, normalization, transformation, multiple testing adjustment, etc., you can read this document. If you are on our intranet, go to S:\MDAC\Administration\Analysis_plans.


How do I submit a bug report or or feature request?

Easy! Just log in to our bugzilla server and submit a bug report or an RFE (request for enhancement). For bug reports, you should include the following information:
  • The HDBSTAT version and build number
  • The version of Java reported in the log window
  • The operating system name and version
  • The web browser name and version
  • The output from the HDBSTAT log window
  • The output to the Java Web Start console (if available)
  • The input files and parameters you used (if applicable)
  • Your login name (if reporting an authentication bug)
The more the complete the initial bug report, the faster the bug can be reproduced, found, and fixed.


How do I run a development build?

The development builds are deployed from here.


What if I am observing weird behavior?

We have a 'clean slate' procedure that has fixed every unexplained issue we've had so far. Basically you,
  1. Clear your web browser cache,
  2. Clear the Java Web Start cache,
  3. Kill all ghost java processes, and then
  4. Reboot the computer.
If the issue has not been resolved and you have successfully reproduced the behavior then you should report a bug.

How do I launch offline?
  1. You must download and launch the version you want at least once online. This version is cached for future online launches.
  2. Right-click on an appropriate memory size button, then select "Save Target as..." option. This procedure will download the required JNLP on to your computer. Open this file and allow the application to start. You will need to enter your login and password.
  3. To test offline launch, take your computer offline (disconnect your computer from the network) and double-click on the downloaded JNLP file. The application should successful launch.

How do I select an appropriate memory size?

You should generally select the maximum amount of memory that does not exceed the physical memory installed on the computer. For instance, if you have 1 GB of RAM installed, you can choose to run the application with either 512 MB or 1024 MB of RAM. The best choice ultimately depends on the dataset size and number of hypotheses tested. Bigger datasets and a large number of hypotheses will require more memory.


What do alpha, beta and RC mean?

Release phase

In-house Testing

Collaborators/
External Testing

Bug-Free

Overall
Stability

Notes

alpha

 

 

 

 

All major features implemented. Subject to Unit, Component & System Testing.

beta

 

 

 

 

Subject to Broader range of end-users & Platform independent testing. Also includes user-interface tweaks & performance optimization.

RC

 

 

 

 

Release candidate.



How do I run the old prototype?

The following are a few demo videos from the original SAS prototype. They are AVI files and best played in Windows Media Player.

  1. Import data to MDAC database (5.7 MB)

  2. Analyze data from a flat file (17.9 MB)

  3. Analyze data from MDAC database (12.8 MB)

  4. Delete a dataset from the database (1.4 MB)

The authentication dialog is behind the main application frame.
  • Symptom:
    The user is unable to click on the main frame because the focus is on the authentication dialog. The authentication dialog is behind the main frame, and the user may not have noticed that dialog yet, resulting in much frustration. The culprit is not quite clear, but it's likely Java Web Start.
  • Workaround:
    On Windows, use Alt-Tab to bring the authentication dialog to the front.

The program fails to start.
  • Symptom:
    This symptom is usually accompanied by a Java Web Start console, but the main application frame is missing. We are still in the process of tracking down the cause of this behavior, but current evidence points to Java Web Start or the JVM as the culprit.
  • Workaround:
    Open the Task Manager and kill the ghost javaw.exe process. Restart, it should work this time. If not, see the clean slate procedure.



Disclaimer