http:^^www.cs.washington.edu^research^projects^ai^www^pdb^pdb.html

来自「This data set contains WWW-pages collect」· HTML 代码 · 共 726 行 · 第 1/2 页

   <tr><th>Labels</th><td> Label the node branches with conditions branched on:
      <table border=1>
      <tr><th>all: Label all branches.
      <tr><th>multiple: Label only branches with multiple
                      children.
      <tr><th>none: Don't label.
      </table></td></tr>
   <tr><th>Resize</th><td> Shrink or enlarge the displayed search tree by a
                 constant factor.</td></tr>
</table>
<tr><th><h4>VCR traversal buttons</h4>
<image src="images/vcr-buttons.gif"><br>
These buttons are for navigating through the plan space  and visualizing
the planning process.
<p>
<table border=3>
<tr><th> 	<td><image src="images/vcr-button1.gif"></td>
	<td>Backup the VCR until stop button is pressed.</td>
</tr>
<tr><th>
	<td><image src="images/vcr-button2.gif"></td>
	<td>Backup the VCR to the plan visited just prior to the current
            one.</td>
</tr>
<tr><th>
	<td><image src="images/vcr-button3.gif"></td>
	<td>Stops the VCR traversal animations.</td>
</tr>
<tr><th>
	<td><image src="images/vcr-button4.gif"></td>
        <td>Progress the VCR to the next visited plan.</td>
</tr>
<tr><th>
	<td><image src="images/vcr-button5.gif"></td>
        <td>Progress the VCR until a mouse button is pressed. </td>
</tr>
</table>   
<p>       
<tr><th><h4>Mouse Commands</h4>
<table border=3>

       
<tr><th> Plan Tree Nodes
<tr><th> Plan Window Markers
   <table border=3>
   <tr><th> L: Select Window: Moves the window to another node. This
                 is done by clicking once on the marker to move and once
	     on the node to move to.
   </table>   
</table>
<hr>

<!---------------------------------------------------------------------->

<h2><a name="PlanD">Individual plan display</a></h2><p>

<p>       
<img align=left src="images/plan.gif">
<p>       
<h3>The Plan Window</h3>
Clicking on a selected node produces a Plan Window,
which provides a more detailed view of the plan associated with that
node.  The upper part of this window shows the parent, siblings, and
children of the current node, while the lower part describes the plan
at that node. The plan can be viewed in one of two ways: in textual
format the plan is printed in the same way that the results of
planning are returned by UCPOP, while in graphic format the steps
are drawn in a partial order from left to right, with lines
representing links connecting effects with preconditions.
<br clear=left>

<h4>Navigating the Plan Window</h4>

The small tree at the top of the Plan Window represents the immediate
``family'' of the current node: its parent,
siblings, and children. It also allows you to navigate the planning tree
simply by selecting any of these nodes: the Plan Window will
immediately update itself using the node you selected as the new 
current node.

<h4>Moving the Plan Window from the VCR</h4>

Whenever a Plan Window is opened, a unique ID number is assigned to it and 
drawn
next to the node in the VCR Window at which it is pointing. You can move the
Plan Window to point at a different node just by selecting this number once and
then selecting the new node.

<h4>Menu Commands</h4>
<table border=3>       
<td>Windows</td><td colspan=2>Please refer to 
	<a href="#Layou">General window layout</a></td>
<tr><td rowspan=6> Plan</td>
      <th> Refine</th><td> Refine the current plan. Brings up a dialog with
                 search options.
      <tr><th>Search Limit</th><td> Number of nodes to search before
                      stopping.
      <tr><th>Choose Flaw</th><td> If yes, the user must select from a
                      list of current flaws. Search limit will be set to
                      1.
      <tr><th>Record Firings</th><td> Yes to record all search control
                      rule firings(slow).

   <tr><th> Print</th><td> Print the current window. Asks for filename via
                 dialog.
   <tr><th> Inspect</th><td> Inspect the current node.
<tr><td rowspan=2> Options</td>
   <th> Graphics</th><td> Change the representation of the plan
      <table border=3>
      <tr><th>Graphics</th><td> Graphical, partial-order view.
      <tr><th>Text</th><td> Textual View
      </table>
   <tr><th> Verbosity</th><td> Control detail or representation
      <table border=3>
      <tr><th>Verbose</th><td> Print out conditions and steps fully
      <tr><th>Terse</th><td> Show only steps
</table>       
</table>
<tr><th><h4>Mouse Commands</h4>
<table border=3>       
<tr><th> Plan Tree Nodes
   <table border=3>
   <tr><th> L</th><td> Select Node</th><td> Pressing the left button on a node
                 causes the window to display the plan associated with
                 that node. The navigational display is updated, as is
                 the VCR window associated with the plan window.
   <tr><th> M</th><td> Describe object</th><td> If Composer is running, a Composer
                 window will be opened on the plan associated with the
                 selected node.
   </table>
<tr><th> Plan Structures
   <table border=3>
   <tr><th> L</th><td> Choose Flaw</th><td> Pressing the left button on a flaw(shown
                 in red) will bring up a plan refinement dialog with the
                 selected flaw already chosen for refinement. Clicking
                 the left button on other structures has no effect.
   <tr><th> M</th><td> Describe object</th><td> If Composer is running, a Composer
                 window will be opened on the structure associated with
                 the highlighted graphic.
   <tr><th> Shift-L</th><td> Move Object</th><td> Pressing Shift-L over a step in
                 graphic display mode will let you drag the step to a new
                 position. This allows you to view the plan in a more
                 reasonable manner than the automatic layout provides.
   </table>
</table>   

<h4>History</h4>
On the bottom of the window is a simple history mechanism.  It records
the nodes visited and allows one to follow the path of plan exploration
<em>by the user</em> in the plan window.<p>
    <table border=3>       
    <tr><td><img src="images/vcr-button2.gif"></td>
	<td>Go to the previous visited node.</td>
    <tr><td><img src="images/vcr-button4.gif"></td>
	<td>Go to the next visited node.</td>
    </table>       

<hr>
<h2><a name="Brows">PDB browsers</a></h2><p>

<p>       
<img align=left src="images/browser.gif">
<p>      
<h3>Browser Window</h3>
The PDB browser is used to provide an organized view and uniform frontend
to inspect different objects related to planning
problems,  for example,  domains, problems,  axioms,  facts,  operators and
sessions.  <br clear=left>

<h4>Menu Commands</h4>
<table border=3>       
<tr>
<td>Windows</td><td colspan=2>Please refer to 
	<a href="#Layou">General window layout</a></td>
<tr><td> Object</td>
   <td><table border=1>
   <th> Print</th><td> Print the current window.
   <tr><th> Inspect</th><td> Inspect the current object.
   </table></td>
</table>
<h4>Browser Commands</h4>
    <table border=3>       
    <tr><td><img src="images/vcr-button2.gif"></td>
	<td>Scroll the browser menus towards the top of the heirarchy.</td>
    <tr><td><img src="images/vcr-button4.gif"></td>
	<td>Scroll the browser menus towards the bottom of the heirarchy.</td>
    </table>       

<tr><th><h4>Mouse Commands</h4>
<table border=3>
<tr><th> L</th><td> Select Object</th><td> Clicking on an item in one of the browser
            menus will bring up the menu associated with that item(if
            any) in the pane to the right of the selection, as well as
            the object associated with that item(if any).
</table>   
<p>
<hr>
<p>
<!---------------------------------------------------------------------->

<a name="Examp"><h2>A Simple Example</h2></a>

<h4>Specify a Problem</h4>

Select <tt>New Session</tt> from the <tt>Debugger</tt> menu. You will then
be able to specify the domain and problem to use. Try selecting
the <tt>uget-paid</tt> problem used in the previous section. Once you
have done this, you are ready to specify the search control options.

<h4>Set the Search Control Options</h4>

Using the <tt>New Session</tt> dialog, set the search function to 
<tt>ucpop::bf-control</tt>.
This is the same search function used for this problem in the previous example.
For purposes of this example, you do not need to set any of the other options.

<h4>View the Results of Planning</h4>

When you click on the <tt>Plan</tt> button, UCPOP will begin planning.
The Plan System Overview window will display a progress report, and 
return the results of planning when done. At this time, you will be able
to see the solution generated by the planner.

<h4>Open a VCR Window</h4>
The session you just created should be listed in the Plan System Overview Window. Select
this session with the left button and press the <tt>VCR</tt> button. This will bring up 
a VCR Window. You are now able to view the actual search tree explored by the planner.

<h4>Use the VCR Window</h4>
Experiment with the VCR Buttons, 
as well as with scrolling the tree around using the scrollbars.

<h4>Open a Plan Window</h4>
Scroll to the top left corner of the tree and select the node labeled
<tt>START</tt>.<br> If you click on this node again, a Plan Window
will appear.  In this case, you will see that the plan has only the
goal step and initial state in it.  This is the first plan created by
the planner. Now scroll down to the bottom left node (the solution),
and open a new window on it. To see just how much work went into the
<tt>uget-paid</tt> solution, go to the <tt>Options</tt> menu, from which
you can select a graphical view of the plan. This view shows each step
in the plan, with preconditions on the left and postconditions on the
right. Links are drawn as lines between the steps.  These links were
inserted into the plan one at a time, each one represented by a branch
in the tree.

<h4>Use the Plan Window</h4>
Explore the area around the <tt>START</tt> node using the Plan Window. Note how
much easier it is to see the relationships between the various nodes compared
to the VCR Window, where the whole tree is being displayed at once.
<p>
<!---------------------------------------------------------------------->
<hr>
<h2><a name="Custo">Customizations and options</a></h2><p>
<h4>Display types</h4>
Some of the defaults used by PDB are not appropriate for monochrome or
grayscale displays.  On such systems,  PDB provides a set of defaults
that are suitable. <p>
You can define <tt>(setf *pdb-use-colors* nil)</tt> in your Lisp startup file
(e.g. .clinit.cl on Allegro Common Lisp),  or anytime <em>before</em> loading
PDB.  This will cause PDB to adopt monochrome defaults for its windows.
<p>
<h4>Variables</h4>
The following are some user customizable variables.  You can customize PDB
by defining a function and setf it to *pdb-startup-hook*.  
You can define this function in your Lisp initialization file;
PDB will call this function when you run pdb-setup.  For example:
<listing>
(defun my-pdb-init-function ()
   (setf *shell-width* 900)
   (setf *plan-height* 1000))
(setf *pdb-startup-hook* #'my-pdb-init-function)
</listing>
The table below lists some of the variables that can be set:
<p>
<table border=3>
<tr><th> <th>Variable</th><th>Description</th><th>Default</th>
	 <th>Note</th></tr>
<tr><th> <th>*shell-width*<br>*shell-height*</th>
     <td>Width and height of the shell window.</td>
     <td>600<br>400</td>
     <td>It is best not to set these variables below the 
     defaults.</td>
</tr>
<tr><th> <th>*vcr-width*<br>*vcr-height*</th> 
     <td>Width and height of the VCR window. </td>
     <td>800<br>600</td>
</tr>
<tr><th> 	<th>*plan-height*<br>*plan-width*</th>
	<td> Width and height of the plan window. </td>
	<td>500<br>400</td>
</tr>
<tr><th> 	<th>*browser-height*<br>*browser-width*</th>
	<td> Width and height of the browser window.</td>
	<td> 500<br>400
</tr>
<tr><th> 	<th>*vcr-show-progress*</th>  
	<td>When drawing the VCR window,  a window indicating
drawing progress will be displayed if this variable is set to t.</td>
	<td>t
</tr>
</table>
</table>
<p>
There are other variables that customize colors and fonts as well.  Please
refer to the file "pdb/shell.lisp".

<hr>
<h2><a name="KBugs">Known bugs</a></h2><p>
Some of these problems are resulted from bugs in CLIM2.0 implementation
on AllegroCL 4.2.  When you send bug reports,  please check the list
below first.
<ul>
<li>Launching composer with many windows open could hang the X server (have 
to kill the ACL process).  Sometimes this also happen if you random click on CLIM
windows when composer windows are being mapped.
<li>Transient window/dialog boxes can sometimes disappear/abort after user
  move the window.
<li>In choose flaw dialog,  the flaw actually appears multiple times e.g.
	(clear ?x3) & (clear ?x3).  But they're both selected.  Can be
	confusing.
<li>Iconify and deiconify doesn't work in our CLIM2.0 implementation.  
As a result if you
iconify a plan window,  they cannot be brought back automatically by clicking
on the node as intended.
<li>When exiting a VCR window,  all its children plan windows should be 
exiting too.  However this behavior cannot be achieved by the CLIM2.0
implementation on our system.
<li>The shell window does not resize correctly vertically because of CLIM2.0
gadget limitations.
<li>Plan nodes will not be highlighted (boxed) if Num Lock or Scroll Lock key is on.
<li>Synchronization problem: asking PDB to display output before the window shows up will
fail.
<li>This is likely a CLIM bug.  When the shell window refreshes the first time,  pressing random
buttons will cause a "medium-transformation" error.  Just continue with the top-level option in
ACL.
<li>Help documents are slightly outdated and not very helpful.
</ul>
<p>
If PDB should ever crash,  you can either continue by choosing one
of the several continue options provided by your lisp system,  or 
restart PDB.  You can simply restart by issuing <tt>(pdb-setup)</tt> again.
Restarting will erase all previous sessions.  Please also include a stack trace
(for example using :zoom in Allegro CL) and send a message to 
[e-mail].
<p>
<hr>
<h2><a name="Portg">Porting PDB</a></h2></p>
PDB is written with flexibility in mind,  and could be adopted to other partial order planners that
is similar to UCPOP.  PDB has already been ported to a descendent of UCPOP,  XII.  Work is 
under way to port PDB to other partial order planners such as Buridan.
<p>
If the planner is very similar to UCPOP,  only functions specific to the planner need to be
redefined.  The file vcr-external.lisp contains the interface functions called by PDB to 
display plan components.  You just need to redefine these functions for your planner.
To change the PDB- Lisp-interpreter interface  for your planner,  modify the file 
vcr-interface.lisp.
<p>

<hr>
</body>
</html>