Jam agents in a Nutshell Version 65 76i 1
Download 391.89 Kb.
|
EXAMPLE PLANSA number of example and test plans are included in the JAM agent distribution. These are located in com/irs/jam/examples directory. Many of these plans are for regression tests – tests to make sure that changes to the agent architecture do not break or otherwise cause illegal or unusual agent behavior. We briefly describe each of these plans in this section. JAM programmers are encouraged to copy the example files and play with modifications to them to learn about JAM actions, semantics, constructs, and runtime behavior. agent-go.jamDemonstrates the JAM agent mobility functionality (actions and receiver class). Requires an instance of the AgentMobilityServer (in the com/irs/jam directory) to be running to receive the agent. blocks-world.jamThis plan contains a solution to a simple implementation in the classic “blocks world” domain. The top-level plan establishes the goal of having Block1 on top of Block2 on top of Block3 on top of the table. The file specifies three different initial world models for the agent. The top set of facts specifies a starting situation that is identical to the goal state. The agent should recognize this and performs no actions. The second set of facts specifies Block1 on Block2 and Block2 and Block3 on the table. The agent needs to clear Block2 before performing any stacking. The third set of facts sets up the blocks so that they are initially inverted from the goal state (i.e., Block3 on Block2 on Block1). basic.jamThis plan contains a procedural test of deeply nested plan constructs of all sorts. checkpoint-agent.jamExercises the built-in checkpointing functionality of JAM. Both the version of checkpointAgent that returns the execution state of the agent as a JAM variable as well as the version that writes the agent state to a file is invoked. memberaccess.jamDemonstrates how to access Java class members without having to write any special interfacing code. load.jamDemonstrates use of the load action, where new agent specifications can be given to the agent while the agent is running. retrieveall.jamDemonstrates the retrieveall and nextfact actions by stepping through two different world model relations that have multiple world model entries with the same relation name. variablescope.jamDemonstrates how variables are scoped and how they can be passed between goals and subgoals. unpost.jamDemonstrates the post and unpost actions for adding and removing top-level goals to the agent. threads3.jamShows the behavior of many JAM constructs, including parallel, do_all, do_any, atomic, and do…while. javanew.jamExercises the "new" primitive function for creating Java objects from the JAM plan level without the need to write a special primitive function for each object type. hanoi.jamThis agent specification file solves the Towers of Hanoi game. The number of disks can be changed by modifying the first goal argument in the file. methodinvoke.jamTests JAM's capability to invoke Java-native class methods as expression functions. Also tests JAM's capability to detect null Java object pointers from the plan level. introspec.jamTests a couple of special primitive functions that provide JAM’s plans insight into the status of aspects of goals and variables that wouldn’t otherwise be accessible. Specifically, it shows how to use the predicate pIsToplevelGoalp to test whether a plan/intention is running for a goal that is a toplevel goal and pIsVariableInitializedp to test whether a JAM variable has had a value assigned to it. relations.jamThis file tests and demonstrates the many relational and computational functions implemented within JAM. subgoals.jamThis file tests goal/plan argument passing and scoped variables. Behaviorally, “Plan 2” will fail the first time it is executed because the update changes the World Model entry and invalidates “Plan 2”'s context. The agent retries the top-level goal and this time “Plan 2” and “Plan 3” run successfully. threads1.jamThis file tests simple subgoaling and demonstrates specification of both goal and plan utility, several constructs including parallel and atomic, and several actions and primitive functions. debugging.jamThis file tests simple subgoaling, actions, and primitive functions. trycatch.jamThis file demonstrates the programming paradigm of wrapping subgoaling with an or construct to achieve a form of TRY-CATCH. The first branch of the or “tries” to achieve the subgoal. If the subgoal fails, then the second branch “catches” the failure. A surrounding do-while construct retries the subgoal a number of times before giving up. doallany1.jamThis file contains the same plans as ex6.jam except for the use of do_any rather than the or. This highlights the non-deterministic nature of the do_any and how the deterministic nature of or can be used to advantage. observerfail.jamThis file demonstrates the behavior of the JAM interpreter to an attempt at subgoaling from within the Observer procedure. In short, the interpreter simply prints out a warning message and execution is otherwise not affected. nativejava.jamThis file tests and demonstrates the invocation of dynamically discovered and loaded, externally-defined, class functions. The test Java class used in the test plan is included in the comments at the top of the file as well as included as a distinct file in the "examples" directory of the JAM distribution. Directory: IRS IRS -> Regulating railway safety in an environment characterised by change IRS -> The state education department IRS -> The state education department IRS -> An architecture for Access to a compute Intensive Image Mosaic Service in the nvo IRS -> The state education department Download 391.89 Kb. Share with your friends:
|