Reporting Problems or Possible Bugs

If you find what seems to be a problem or a possible bug with GEMPACK, please report it as indicated below.

We are usually able to respond to such reports within 48 hours. If a bug is found, we are usually able to send a bug fix within that time.

Save Files Before Trying to Work Around the Problem

If you find a possible bug, we know that you will want to try to work around it.

But please, first save the files as they are. Otherwise we know from experience that you may find it impossible to reproduce the problem.

If we can reproduce a bug, we can usually fix it quickly. But if we cannot reproduce it, we probably cannot help.

Sending Files Needed to Reproduce the Problem

Please zip up in a single ZIP file all files needed to reproduce the problem.

If the problem occurs in a simulation (with GEMSIM or a TABLO-generated program), we need all files beginning with the TAB file. So please zip up the TAB file, the Stored-input file used to run TABLO, the Command file, all starting data files, and any shock or supplementary data files needed.

Please include in the ZIP file, the LOG file from your run which shows the problem. This is important for us to know that we have reproduced the same problem as you saw.

Please also send a brief description of the problem. This might be something like:

Please send the ZIP file and information about the problem to GEMPACK Support. Please attach to your email a copy of the diagnostic file that you can generate with ViewHAR (see end of this page).

Checking That You Have Included All Files

If possible, please unzip into an empty directory the files you think are necessary.

Then run the job(s) again to check that you have all required files and that you can reproduce the problem. [If the problem is with a simulation, make sure that you start by running TABLO.]

This is what we need to do to reproduce your problem. If the above works for you, chances are that we will be able to reproduce your problem from the ZIP file you send.

If The Error Comes When You Are Using RunMONASH/RunDynam etc

Then getting the relevant files into a ZIP file is easy. Just ask RunMONASH etc to make a Zip Archive using menu item
Zip..Save Ingredients as ZIP archive

We also need the LOG file so that we know whether or not we have reproduced your error. And please tell us which year/period and which run (Base/Rerun/Policy) the crash occurred on.

Unfortunately RunMONASH ZIP Archives can be very large - sometimes too large for email. If so, you may be able to send yours to us via the web site
www.YouSendIt.com

Reporting problems with Windows programs: the Diagnostic file

If you have a problem with a GEMPACK Windows program such as ViewHAR or TABmate, you should, as described above, zip up and send to us any input files needed to reproduce the problem. You may need to describe the precise sequence of button-clicks which led to the problem. Sometimes a picture is useful, which you could save in a Word document as follows:

In addition, you should send us a copy of the diagnostic file. For ViewHAR, go Help....About/Diagnostics and press the Diagnostics button. A diagnostic file should be displayed, which you can save or copy to the clipboard. TABmate, ViewSOL, etc, work in a similar way.

Indeed, it's a good idea to send us this diagnostic file (say, from ViewHAR) even if your problem is not specifically related to a Windows program. The file tells us what operating system and CPU you run, how much RAM and free disk space you have, and many other facts that may be relevant to your problem.