Demonstration Highlights
- The ForMAT user begins by checking for new mission statement.
- The ForMAT user generates some ForMAT
queries to see if any FMs in ForMAT are related to the mission.
- The ForMAT user enables the PRODIGY/Analogy system and the FTP Watchdog. This will signal ForMAT to record
specific user actions and send them to PRODIGY/Analogy. The FTP Watchdog will
manage inter-process communication.
- The ForMAT user (as of now) manually parses the mission statement into a set of goals/subgoals (objectives) with associated arguments
using the ForMAT goal editor. These goals are translated into PRODIGY goals, often in existentially quantified form, so
that PRODIGY can plan with variables.
- A set of "triggers" have been predefined.
They are recorded in the history and signal PRODIGY/Analogy for modification suggestions. For example, when the
ForMAT user saves the goals/subgoals for a new mission; the "save-goal" ForMAT
operation will "trigger" PRODIGY/Analogy to provide plan similarity
information.
- Using the ForMAT goals as probe into a case-base of past planning
solutions, PRODIGY/Analogy retrieves a set of
cases most similar to the current problem. Subsequently it sends a message to the ForMAT user that PlanC and PlanE
are similar. This is displayed as a message from PRODIGY/Analogy and/or as a
task item in the ForMAT task window.
- The ForMAT user reads the suggestions and can use one or all of them to
build a TPFDD. During this process, ForMAT provides history (and relevant
trigger information) to PRODIGY/Analogy, and PRODIGY/Analogy responds
accordingly. The ForMAT user can accept, reject,
or ignore suggestions from PRODIGY/Analogy by using functions provided in
the ForMAT "task window".
- The ForMAT user will use the "check consistency" feature in the ForMAT
"goal editor" to do some consistency checking of the newly developing TPFDD.
The "check consistency" operation is also a "trigger" to PRODIGY/Analogy to
provide further modification support.
Click here for further details on the demonstration.
Correspondence:
mcox+@cs.cmu.edu
Last Edited: August 16, 1996
