Release Notes for Version 1.12 of Suppose:
N.L.Crookston RMRS-Moscow, October 29, 1999

Last revision of these notes:  April 25, 2000

Changes from version 1.11 to 1.12:

1. Build in first level PPE support. This provides for building PPE
runs, support for PPE keywords, and support for other extensions that
require the PPE.  A section to the help files was added to address the
PPE support capabilities.  In short, basic support for all
capabilities of Suppose as needed by PPE now exists except that
Suppose can not read and parse PPE-generated output files.  So, the
Generate Reports and and Generate Graphs facilities are not working. 
Several additional adjustments will be needed to provide full PPE support
(so users can do most of what is described in the PPE user's manual).

While PPE support exists in Suppose, it is not yet "turned on".

2. Changed the way Suppose handles the addition of extension keywords
to the runstream.  Formally, Suppose contained hard code that built the
transition keywords (like COVER, ESTAB, or MPB).  Now there is a new
MSText section in the parameters file called "extenPrefixes" where the
these transition keywords are specified.

December 7, 1999:

3. Changed the "Use FVS Keywords" window so that the most recent
Extension, Category, and Keyword, are reselected when the Extension
list changes.

4. Added "Parms" support for several Fire Model keywords.

5. Modified Suppose to display and manipulate 26 character-long stand 
identification codes.

December 14, 1999:

6. Suppose often would not warn a user prior to writting over the top
of an existing file. This has been changed so that warnings are issued
more routinely on Windows, but not Motif.

7. Modified the PPE Support to automatically write the StartYr,
MstrInt, and MstrCycs keywords.

December 21, 1999:

8. Changed the habitat list for the NI variant.

9. Changed the help files to specify 26 chars in the stand ids.

Jan 5, 2000

10. Fixed a bug with the PPE support. PPE support is being tested.

11. Modified the program so that that checks the users "FVSHOME"
(normally the directory where Suppose is started) for FVS programs.
Only those programs that are installed are available to the user.  If
none are installed, suppose continues to run as if all were installed
(a Warning is issued).

This feature actually has more implications that meets the eye.  For
example, lets say that a user desires to run the Fuels and Fire
Extension (currently available for the ni variant).  The user then
loads nifm.exe into c:\fvsbin. With the older Suppose, if the user did
not pick a Fire Model keyword, Suppose would attempt to run ni.exe and
the user hadn't loaded that program as well, the run would fail
without even an error msg.  The new Suppose will run nifm as it is the
"only" program it can find that is based on the ni variant.
Therefore, using the newer version, only one program based on the
variant need be installed on the users computer. (Except in the case
of PPE...but the overall idea still applies).

Jan 13, 2000

12. Modified the parameters file to include support for the parms
feature on ThinAuto, MinHarv, SpecPref, and TCondMLT keywords. 

Jan 14, 2000

13. Found and fixed a bug that caused the Potential Flame Report 
from the Fuels and Fire Extension to be skipped by the Read FVS Output
function.

Feb 17, 2000

14. Added several entries to the "programs" to include several PPE
variants and to include so fire.

Mar 15, 2000

15. Added support for the GenDefol models (a.k.a. Budlite) in the
parameters file.

Mar 23, 2000

16. Added support for cr (in addition to the existing sw, sp, lp,
bp, and sf) to the mistletoe entries in the parms file.

April 12, 2000

17. Modified support for the WWPB model, included more ppe programs,
modified the way Suppose picks variants so that it always finds a
variant and therefore crashes less often.  Fixed a bug that was
causing crashes when a component was being set up to be scheduled by
condition. Changed the Edit window so that it handles cases with
several hundred stands with more grace.

18. Added automatic insertion of the AGPLabel into the .key
files...mostly to support the PPE's MSPolicy facility.

April 13, 2000

19. Fixed AreaLocs, Neighbors, and RdAccess PPE keywords (thanks
Drew), modified Suppose to terminate when it can't find the program it
needs to run an existing keyword.

April 25, 2000

Modified several parms file entries for the PPE and the WWPB
model. Enabled/created the ppcrp, ppnip, ppsop, and ppcip programs.