This is the full soar-suite 8.5.2

Documentation/soar7-to-soar8.txt

@@ -0,0 +1,77 @@
+      List of changes required in upgrading from Soar 7 to Soar 8.
+			     John E. Laird
+			   December 11, 1998
+
+This document list the changes that have to be made to Soar 7 programs
+so that they run under Soar 8.
+
+1. All preferences in attributes are eliminated.  Soar 8 uses 
+   preferences exclusively for the selection of operators.  
+   A. Previous use of preferences such as best (>) and worst (<) for
+      values of attributes to create defaults must be eliminated. You
+      may need to add operators to select the values of these attributes
+      explicitly. 
+   B. Parallel preferences (&) are no longer needed to allow
+      multi-valued attributes - attributes that have more than one value
+      in working memory.  All attributes (except the operator attribute
+      of a state) can have multiple values.
+   C. There are no longer any attribute impasses.
+
+2. The order of input, decision, and output has changed.  The new
+ordering is:
+
+ input ->  operator propose -> decision -> operator apply  -> output
+   ^         i-support                      o-support &         |
+   |                                        i-support           |
+   --------------------------------------------------------------
+
+   A. Input is called only once per decision.
+   B. Output is called only once per decision.
+   C. Only rules that create i-supported structures fire during the
+      operator propose phase.  Rules fire in parallel and to quiescence.
+   D. During the operator apply phase, all matched rules fire in
+      parallel and to quiescence.
+   These changes do not necessarily lead to any change in your software,
+   and may even allow you to simplify your software.
+
+3. Selected operators are removed (the <s> ^operator <o> working memory
+   element is removed) as soon as the operator either no longer has an
+   acceptable preference, or if it would not stay selected because of
+   changes in the preferences.  A new operator is selected only during
+   decision (thus, there may be parts of the cycle in which no operator
+   is selected).  
+
+   This process replaces the reconsider preference for operators - Soar
+   8 does not support reconsider.  You will need to remove all of the
+   rules that create reconsider preferences (terminate*operator rules).
+
+   You may need to ``tweak'' the conditions of your proposals so that an
+   operator is not removed too early or too late. You may also need to
+   split an operator that created or changed many internal data
+   structures in sequence into separate operators because the operator
+   will probably be retracted as soon as the first data structure is
+   modified (which will probably cause the operator proposal to
+   retract).
+
+4. Goals (substates) are automatically retracted if any of the
+   o-supported structure in them become ``inconsistent'' with higher
+   levels of the goal/state stack. A goal with o-supported structure is
+   removed if any of the working memory elements in higher level
+   goals/states that were tested along the path to creating the
+   o-supported structure are removed.
+
+   The easiest thing to do in response to this change is move
+   o-supported structures up to the top-level state.
+
+5. Dot notation is legal in actions.
+
+Some other changes that aren't required, but might be nice to note:
+
+1.  RHS dot notation
+2.  Ability to run til agent produces output 
+3.  Some ONCs are "free"  (detected immediately, without extra decision cycles)
+
+In the section on the new decision cycle, we should indicate that 
+the TSI includes a facility to allow users to stop after the decision
+phase.  We could also include the info needed to set up callbacks 
+after the decision phase.

Soar Suite 8.5.2 Release Notes.txt

@@ -0,0 +1,185 @@
+         Summary of changes between SoarSuite 8.5.1 and SoarSuite 8.5.2
+                            July, 2004
+
+
+A summary of changes in SoarSuite 8.5.2 is listed immediately below. For more
+details, including changes not mentioned in the summary and a list of known
+issues see the Details section after the summary.
+
+======================
+New Windows Installer:
+======================
+
+	The Windows installer is now built with a different technology which
+is much easier for us and results in a much smaller package.
+
+=========================
+Several kernel bug fixes:
+=========================
+
+	Almost all known bugs fixed, including all known crash bugs. See the
+details section below for more information.
+
+==================
+New TankSoar Bots:
+==================
+
+	TankSoar now comes with two new bots.  Mapping-bot demonstrates how a
+tank might build up an internal map of the level.  Obscure-bot is a challenge bot
+for people to test their own bots against.  The code is provided in an obfuscated
+binary.  See obscure-bot.txt in the TankSoar agents directory for details.
+
+==========================
+SoarDoc and DMGen updated:
+==========================
+
+	These changes were actually in the the 8.5.1 release, but we failed
+to note them.
+SoarDoc:
+ - Fixed special character handling when UseExistingComments is used.
+ - Added ShowProdSourceInline which shows production source code
+   inline in the production documentation
+ - Ability disable datamap node coloring
+ - Fixed case-sensitivity issues for production names and list sorting.
+DMGen:
+ - Fixed handling of mixed-case production names.
+
+======================
+Documentation Updated:
+======================
+
+	The tutorials have had some typo fixes and screenshot updates, and also
+explain substates better.
+
+==================
+Tcl Soar Debugger:
+==================
+
+	The TSDebugger has several bug fixes which may have affected some
+users.
+
+===================
+VisualSoar Updated:
+===================
+
+	VisualSoar has several small bug fixes.
+
+======================
+Critical SGIO bug fix:
+======================
+
+	Our fix for bug 254 in the last release actually caused serious
+problems. This has been fixed for real now.
+
+====================================================================
+                            Details
+====================================================================
+
+Below is a fairly complete list of enhancements, changes, bug fixes, and known
+issues, with bug numbers for reference. For more information and up to date list
+of what's been fixed please visit the Soar bugzilla server at:
+
+    https://winter.eecs.umich.edu/soar-bugzilla/.
+
+New bug submissions and enhancement requests are welcome!
+
+
+Soar-8.5.2
+==========
+
+Bug Fixes
+---------
+353  stats command keeps recording between runs
+389  missing error handling for set_watch_prod_group_setting
+
+Enhancements
+------------
+358  change soar8 command error message
+
+Known Issues
+------------
+312  agent structure isn't cleaned up properly
+356  All matches get same support as last processed match
+
+TSDebugger 4.0.1
+================
+
+Bug Fixes
+---------
+365  rules that contain a capital letter break productions tab
+376  stop button doesn't work with Eaters, TankSoar
+396  error when closing group from task bar
+398  extra 0 gets printed when soar connected to environments
+
+Known Issues
+------------
+336  negated conditions don't print properly in the console window
+397  grouping bar in production tab not always right
+
+SGIO 1.1.2
+==========
+
+Bug Fixes
+---------
+254  Some special characters in StringWME's do not transfer to Soar
+
+Eaters 3.0.8
+============
+
+Bug Fixes
+---------
+391  garbage printed to debugger output when Stop After Decision Phase is on
+
+TankSoar 3.0.8
+==============
+
+Bug Fixes
+---------
+map loading menu now defaults to maps directory
+188  Selecting Map->Random Map causes error message when agent present on
+	current map
+392  garbage printed to debugger output when Stop After Decision Phase is on
+393  command 'run 1' generates 'invalid command step' error
+
+Enhancements
+------------
+new challenge bot (obscure-bot) and mapping bot provided
+
+Known Issues
+------------  
+399  can't use reset tank command in tank control panel tanks menu
+
+Documentation
+=============
+
+Bug Fixes
+---------
+349  tutorial images need to be updated
+375  typo in tutorial part 1: move-north  
+386  typos in tutorial part 1 (search control)  
+
+Enhancements
+------------
+Added information to tutorial about substates.
+
+Known Issues
+------------
+380  typo in section 5.6.3
+381  o-support-mode command missing newest support modes 
+
+VisualSoar 4.5.3
+================
+
+Bug Fixes
+---------
+361  adding a dir that doesn't exist to agent path on file->new project fails with no warning
+362  initial rules in a project are not justified correctly
+363  if project loaded then create new project, title bar does not change
+364  file with same name as datamap have same window names
+366  Initialize-<task> Operator not in datamap
+368  dragging node onto itself makes node disappear
+372  fails to detect extra whitespace after :
+
+Known Issues
+------------
+Too many to list. See bugzilla for details.

dmgen-1.0.0/license.txt

@@ -0,0 +1,34 @@
+Copyright 1995-2004 Soar Technology, Inc., University of Michigan. All 
+rights reserved.
+
+Redistribution and use in source and binary forms, with or without 
+modification, are permitted provided that the following conditions are 
+met:
+
+   1.	Redistributions of source code must retain the above copyright 
+      notice, this list of conditions and the following disclaimer. 
+
+   2.	Redistributions in binary form must reproduce the above copyright
+      notice, this list of conditions and the following disclaimer in 
+      the documentation and/or other materials provided with the 
+      distribution. 
+
+THIS SOFTWARE IS PROVIDED BY THE SOAR CONSORTIUM ``AS IS'' AND 
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 
+TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE SOAR 
+CONSORTIUM  OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE 
+GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, 
+WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 
+DAMAGE.
+
+The views and conclusions contained in the software and documentation 
+are those of the authors and should not be interpreted as representing 
+official policies, either expressed or implied, of Soar Technology, Inc., 
+the University of Michigan, or the Soar consortium.
+

dmgen-1.0.0/readme.txt

@@ -0,0 +1,5 @@
+dmgen - Soar datamap generation tool by Soar Technology, Inc.
+
+Please see doc/dmgen.doc for details on running dmgen. The 
+main dmgen program script is src/dmgen.tcl.
+