"Ashock" Statement Bug Fix for Source-Code Release 6 of GEMPACK


This bug relates to "ashock" statements. These statements are normally only used in conjunction with recursive dynamic models (such as MONASH, GTEM etc).

Details of "ashock" Command file statements can be found in section 8.9 of GPD-4 (October 1998).

If you do not use "ashock" statements you do not need to download this fix.

If you use "ashock" statements (perhaps in conjunction with our Windows interfaces RunDynam, RunMONASH, RunGTEM etc), we strongly recommend that you download this fix because this bug can cause incorrect results.

The bug was likely to cause incorrect results if there were 2 or more "ashock" statements for the same variable as in

ashock phous 1 = 3 ;
ashock phous 2 = 4 ;

In the above case it is likely that the shocks were given to the wrong components of variable phous.

However the bug usually did not produce wrong results when there was only one "ashock" statement for each variable as in

ashock phous = file phous.shk ;

The following fix is recommended for those with any version of Release 6.0 of Source-Code GEMPACK.

The fix here also fixes the "shock" bug in Release 6.0.

Warning. Do NOT install this fix if you have a different release of GEMPACK.

Below we give instructions for installing this fix for the Windows PC versions of GEMPACK.
If you need to install this fix on a different version of GEMPACK( for example, a Unix version), please contact the developers of the code.

To install this fix for use with a Windows PC version of Source-Code Release 6 of GEMPACK, proceed as follows.

1. Download the file CMCHSH.ZIP (19K) and put it into the SUBS subdirectory of the directory in which your GEMPACK is installed (usually, C:\GP\SUBS).

2. Go to a DOS box and change into this SUBS subdirectory.

3. Whether you are using LF90 or F77L3, issue the following commands.

unzip32 -o cmchsh.zip
zip cm cmchsh.for
replib cm

This will replace the existing CMCHSH in your GEMPACK library with the bug fix.

The fix will only work on .EXE files you make after you install the fix. In particular, you may want to rerun LTG on TABLO-generated programs after you install this fix.

Go back to
Bug Fixes Page