• Relationships amongst items within a RPL set, i.e. a listing of what functions are called by a rule or block or what rules or blocks call a given function.

• Performance information on each item in the RPL set. In addition, name, state, description and arguments are listed.

• Performance. Examining the calling relationships and performance data of rules, blocks, and functions can be useful when analyzing and improving the performance of a RPL set.

• Analysis and Understanding. Navigating through the calling-tree while reading the description text can be useful for interpreting a RPL set.

• Documentation. Printing a portion of a calling-tree along with its item’s descriptions and state provides concise documentation of a RPL set.

• Groups view. The first treeview is the classic view of utility and policy groups and their members as displayed in the RPL set editor dialog. It is provided here as an entry point into a RPL set because it will be familiar to users. This view differs from the RPL set editor dialog, because it also includes the RPL Statement items defined for each block or function.

• Descending view. This treeview displays the items that are called by a given item. Expanding the treeview under an item reveals the items that are called by the given item. This view is called the descending view because it provides a descending view of the static call graph.

• Ascending view. This treeview displays the items that call a given item. Instead of descending the static call graph as in the previous view, it ascends the call graph to reveal all the items that call the given items.

• From the ruleset editor: Ruleset, then Analysis

• From the RPL group editor: Group, then Analysis

• From the Rule editor: Rule, then Analysis

• From the Function editor: Function, then Analysis

• Use the mouse to move the vertical scrollbars up and down.

• Navigate up and down using the keyboard using the Up-arrow and Down-arrow keys.

• Pressing a letter on the keyboard will navigate to the next item that begins with the given letter.

• The user can move between children and parents in several ways.

• The [+] and [-] buttons on the left side of each row to expand and collapse the row.

• The Left-arrow and Right-arrow keys on the keyboard expand and collapse rows and navigate between children and parents. The first arrow press moves up or down a level and the second arrow press expands or collapses the level.

• View, then Expand All or Alt + Right-arrow will expand all the rows in the current listview. Note that for very large RPL sets, expanding all rows may require significant computational time.

• View, then Collapse All or Alt + Left-arrow will collapse all the rows in the current listview.

• View, then Expand Children or Ctrl + Right-arrow will open all child rows of the current item. This is a quick way to expand just a portion of the current treeview.

• View, then Collapse Parents or Ctrl + Left-arrow will close all the parent rows of the given item. This is a quick way of collapsing a large block of a treeview to simplify the current view.

• Double-click an item in a listview.

• Edit, then Open Editor or Alt+E.

• Name. Name of the RPL item. For RPL statements, this name is generated from the left-hand-side of the statement and cannot be modified by the user, e.g. “ASSIGN TO Reservoir.Slot[]”. This column also displays an icon representing the items type.

• Description. The user-specified description text associated with an item. This text can be edited using the item’s RPL editor which can be opened by double-clicking the item in the treeview, using the key command Alt+E, or selecting Open Editor from the context-menu or Edit, then Open Editor from the main menu.

• On. Whether the item is currently active. This field can be edited from the RPL set or RPL group dialogs.

• Return type. The return-type of a function.

• Num arguments. The number of arguments that must be passed to a function.

• Argument list. The specific list of argument types that must be passed to a function.

• Object-type. The text name for the item’s type. An icon representing the item’s type is also displayed in the Name column.

• Priority. The numerical priority of a block.

• Out-degree. The number of RPL items called by this item, i.e. the number of children of this item in the Descending view.

• Orphan. An orphan is an item that is not being called by any other item. In the Ascending view, an orphan has no children.

• In-degree. The number of RPL items that call this item, i.e. the number of children of this item in the Ascending view.

• Time. The number of seconds spent in evaluating this item during the most recent model run. This value is computed using the ANSI-C clock() function which returns the number of CPU cycles the program has used (user time), measured in some system-dependent units (milliseconds on Windows). The value displayed in this column is the difference of the clock() values returned before and after executing the item, then scaled using the CLOCKS_PER_SEC macro to get a final value in seconds.

• Evaluations. The number of times this item was executed during the most recent model run.

• Dispatch Count. For a Rulebased Simulation rule, this is the number of dispatch methods that have executed due to values being set by the rule.

• Dispatch Time. For a Rulebased Simulation rule, this is the time spent executing dispatch methods as a result of values being set by the rule

• Sets. The top-level RPL set.

• Groups. Policy or utility groups.

• Blocks. block items such as rules, methods, or expression slots.

• Print statements. Print statements contained in blocks.

• Other statements. All statements, besides print statements, contained in blocks. Unlike print statements, these statements all assign values in their left-hand-side.

• User functions. All internal (RPL language) user functions.

• Predefined functions. The predefined functions and the utility groups that contain them.

• Window, then Sync Views. When this is active, selecting an item in one of the listviews will also select it in the other two listviews.

• Window, then Replace Existing Editor. When this is active, opening a RPL editor (by double-clicking an item or using the Edit, then Open Editor menu item) will close the previous RPL editor and replace it with the new editor. This saves the user from having to close each editor dialog when quickly examining the contents of numerous editors.

• Window, then Show Multiple Lines. When this is active, the treeviews will display all the lines of a multiple line description. This can be turned off when the user would rather see just the top-line of multiple line descriptions.

• [Depth Toolbar], then Maximum Depth. Sets the maximum depth of in the treeviews. This value is typically only of interest with RPL sets that use recursion, i.e. where two functions call each other. With recursive RPL sets, the Expand Children or Expand All features need to specify a maximum depth since the recursive calls would continue infinitely. In this case the treeview will only expand to this depth.