Release Notes for Version 1.07 of Suppose:
N.L.Crookston RMRS-Moscow, March 24, 1998

Last revision of these notes: April 10, 1998

Changes from version 1.06 to 1.07:

1. Bare Ground support:

A Bare Ground button was added to Select Simulation Stands.  This
button will create a bare ground stand and add it to baregrnd.slf
(which is created if it does not exist).  If baregrnd.slf is not
referenced in the suppose.loc, it is automatically added.

If no suppose.loc is found when the Select Simulation Stands window is
opened, then the user is given the choice of selecting a locations
file or Suppose will automatically create one.  If one is
automatically created, Suppose will look for baregrnd.slf and add it
to the suppose.loc.  If no baregrnd.slf is found, one is created.

When Suppose creates a bare ground stand, it leaves all the site
information blank.  Users can add some keywords (StdInfo or ModType,
for example) to specify the site data or use the Edit Stand List File
tool.

Usage note: If you don't have tree data, leave the tree data file
field blank in the stand list file entry for a stand.  Suppose will
automatically generate the NoTrees keyword (this has always been the
case). 

2. If the user edits an slf or locations file when the Select
Simulations Stands window is opened, Suppose now automatically updates
the contents of the Select Simulations Stands window. Prior to this
change, users were required to close this window and reopen it to make
the changes in the locations or slf files to take effect.

3. The 8 character-long standIDs within FVS have limited the utility of
the generate graphs and generate report facilities of Suppose.  To
address this problem, Suppose now reads an "untruncated" version of
the stand ID when it scans the FVS output.  As a result, the stand IDs
displayed in the "Case" identifications are exactly the same stand IDs
used to identify the stands in the stand list file (.slf) (unless the
user changes the stand IDs using the Change Group Membership window in
which case the names the user enters are used).  Note that FVS has not
been changed, this is only a change in Suppose.

4. A new variable, called "StandID", has been added to the Summary
Statistics report.  The variable is constant over all years.  The use
for this variable is to provide a simple way for Generate Report users
to get a meaningful identification code into tables that are
subsequently "pasted" into other applications.

5. Yet another small change to the suppose.prm file was made to
correct access to the snags file used by the fvs2svs post processing
program (I hope I have it this time!).  Like all issues, this one may
be revisited.

============ April 6th update:

6. Some window focusing problems that resulted in some ugly sounding
error messages (but no fatal errors) have been fixed.

7. The parms file was fixed for the SVS-Windows Movies option.

8. The parms file was updated to reflect the new forest codes of the
West Cascades and Pacific Northwest Coast variants (per FVS Bulletin
348).

============ April 10th update:

9. The parms file has change to reflect the change in the StrClass
keyword, from SStage, which not longer works in FVS programs built
after April 10.

The Event Monitor variables that are automatically computed when the
structural classification is used have changed.  Here is a table of
the old and new variable names (the old variable names will not work):

      Old names New names
      --------- ---------
       BSSTAGE   BSCLASS
       ASSTAGE   ASCLASS
       BSTGDBH   BSTRDBH
       ASTBDBH   ASTRDBH
       BPERCOV   BCANCOV
       APERCOV   ACANCOV

Note that the SpMcDBH function arguments have not changed.

If you are using the SStage keyword in an existing keyword file, you
must delete it (using the Edit Simulation feature), and then add the
StrClass keyword.  If you are using Event Monitor variables in a
Compute or IF test, the components that use them can be edited rather
than deleted and re-built.

10. The behavior of the Import feature of Edit Stand List File as been
slightly modified.  In the previous versions, grouping codes that you
set in the template were ignored if any grouping code (that is, a B
record) was present in the imported DIR file (these are files used on
the DG-based submittal system).  Now, grouping codes you set in the
template are appended to those found in the DIR file.  The same change
was made for the addfiles.

11. An error was found in the Import feature of Edit Stand List File.
The error resulted in the created slf file to contain B records that
do not contain all the data present in the window (the remaining data
were written to an extra line that was subsequently ignored by
Suppose).  This error could cause incorrect and misleading
simulation results.  Anyone using the import feature should get a new
version of Suppose and check the slf files already created using this
feature (the error does not cause problems with all slf files).