HyperView User's Guide

Locator Strings

Locator Strings

 Previous topic Next topic No expanding text in this topic  

Locator Strings

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

The examples below briefly outline the method that is used by HyperView to identify node/elements/parts within a model using locator strings:

Variation 1

“entity_id”

e.g *NodeLocator(“102”)

HyperView will find the node with the ID "102".  If there are multiple node pools, HyperView will arbitrarily use the first node pool it encounters.  The current active model is used to resolve any ambiguity in the case of overlaid models.

The same mechanism is used for other entity types to locate the specified ID.  See additional examples below:

*ElementLocator(“20”)  // Find element with id 20. First found element pool will be used

*PartLocator(“34”)     // Find part with id 34. First found part pool will be used

*SystemLocator(“2”)    // Find system with id 2. First found system pool will be used.

Variation 2

“model_id entity_id”

e.g *NodeLocator(“2 102”)

HyperView will find the node with the ID "102" in the model whose ID is "2".  If there are multiple node pools, HyperView will arbitrarily use the first node pool it encounters. The current active model is used to resolve any ambiguity in case of overlaid models.

The same mechanism is used for other entity types to locate the specified ID.  See additional examples below:

*ElementLocator(“1 20”)  // Find element with id 20 in model id 1

*PartLocator(“2 34”)     // Find part with id 34 in model id 2

*SystemLocator(“1 2”)    // Find system with id 2 in model id 1

Variation 3

“entity_pool_label entity_id”

e.g *NodeLocator(“Accelerometer 200”)

HyperView will find the node with the ID "200" in the node pool with label “Accelerometer”.  The current active model is used if there are overlaid models.

The same mechanism is used for other entity types (the corresponding entity's pool will be used) to locate the specified ID.  See additional examples below:

*ElementLocator(“Shell 20”)      // Find element with id 20 in the element pool “Shell”

*PartLocator(“Part 34”)          // Find part with id 34 in the part pool “Part”

*SystemLocator(“Marker 2”)       // Find system with id 2 in the system pool “Marker”

Variation 4

“model_id entity_pool_label entity_id”

e.g *NodeLocator(“1 Accelerometer 200”)

HyperView will find the node with the ID "200", in the node pool with the label “Accelerometer”, in the model whose ID is "1".

The same mechanism is used for other entity types (the corresponding entity's pool will be used) to locate the specified ID.  See additional examples below:

*ElementLocator(“1 Shell 20”)  // Find element with id 20 in element pool “Shell” in model id 1

*PartLocator(“1 Part 34”)      // Find part with id 34 in part pool “Part” in model id 1

*SystemLocator(“1 Marker 2”)   // Find system with id 2 in system pool “Marker” in model id 1

Variation 5

This variation is applicable only for "node" entity types.

“model_id part_pool_label part_id node_pool_label node_id”

e.g *NodeLocator(“1 Shell 23 Node 200”)

HyperView will find the node with the ID "200" in the node pool with label “Node”.  Since the part pool and part ID is also specified, the node id is searched within the context of that part.

If the above method fails to locate the node, then the node with ID "200" in the node pool “Node” will be used to locate the node.

Variation 6

This variation is applicable only nodes on the cross section cuts.

“model_id part_pool_label part_id node_pool_label node_id1 node_id2 percentage”

e.g *NodeLocator(“1 Shell 23 Node 200 201 0.567”)

HyperView will attach the measure/note to a location determined by the last three parameters.  Since the part pool and part ID is also specified, the node IDs are searched within the context of that part.

In the example above, HyperView will attach the measure/note at 56.7% between node 200 and 201.

Variation 7

For nodes that are formed at the intersection of two cross-section cuts, the following syntax is valid:

“model_id part_pool_label part_id node_pool_label node_id1 node_id2 percentage1 node_id3 node_id4 percentage2 percentage3”

e.g *NodeLocator(“1 Shell 23 Node 200 201 0.567 203 204 0.789 0.85”)

HyperView will attach the measure/note to a location determined by the last seven parameters.  Since the part pool and part ID is also specified, the node IDs are searched within the context of that part.