Model Browser User's Guide    

Model Tree

The tree in the All Models pane displays the hierarchical structure of the models you have built. Views and functionality within the browser differ according to which node is selected.

The following is an example of a model tree.

The elements of the tree consist of the following:

  1. Project node
  2. Test plan node
  3. Response node
  4. Local node
  5. Response feature nodes

You can rename all nodes, as in Windows Explorer, by clicking again or by pressing F2 when a node is selected.

There is a context menu available. When you right-click any node in the model tree, you can choose to delete or rename that node, or create a new child node.

Tree Structure

The preceding example shows a more extensive model tree, with two two-stage models as child nodes of a single response model.

There can be many models within (or under, as child nodes in the tree) each response model node.

There can also be many different response nodes within a single test plan, and each project can contain several different test plans. However, there is only one project node in the tree at any time.

Response features can themselves have child nodes -- several models can be tried at each response feature node and the best selected. There is an example showing this at the end of the section on Icons: Blue Backgrounds and Purple Worlds.

Icons: Curves, Worlds, and Houses

The icons are designed to give visual reminders of their function.

Icons: Blue Backgrounds and Purple Worlds

Icon changes convey information about modeling processes.

In the following example you can see child nodes of a response feature. You can try different models within a response feature, and you must select one of the attempts as best. In this example you can see that Cubic is selected as best, because it has a blue background, so it is the model being used for the Blow_2 response feature.

When a model is selected as best, it is copied up a level in the tree together with the outliers for that model fit.

When a new global or local model is created, the parent model and outliers are copied from the current level to the new child node. This gives a mechanism for copying outliers around the model tree.

A tree node is automatically selected as best if it is the only child, except two-stage models which are never automatically selected; you must use the Model Selection window.

If a best model node is changed the parent node loses best model status (but the automatic selection process will reselect that best model if it is the only child node).


  Project Level: Menus Test Plans