Keypoint Command

The Keypoint and Keypoints commands are used in FEA analyses to define key points that are used to define paths when generating a mesh.

Scripted Keypoints

In scripted input files, the Keypoint command has two forms.

Keypoint Command

The first form is to define a key point:

Keypoint #1,#2,#3,<#4>

where

• #1 is the id to give to the new keypoint. The id must be unique among all other key points.
• #2 and #3 are the x and y coordinates of the key point (or R and Z coordinates for axisymmetric analyses).
• #4 (optional) can be "polar" to indicate the coordinates are given in polar coordinates (r and θ) instead of Cartesian coordinates (x and y for planar or R and Z for axisymmetric). By default, the polar coordinates are from the origin (0,0), but the polar origin can be changes with the Origin Command.

Keypoints Command

A key point can be used in more than one path. The first time it is used it is defined as above. For all subsequent uses, however, it is reused by giving just the id. Thus, the second form of the Keypoint command is to refer to a previous key point using the Keypoints command:

Keypoints #1,<#2>,...

where #1 (and optionally #2 ...) are the id of previously defined key points to use consecutively in definition of a path. The form of the Keypoint command must always be with a path block.

XML Keypoints Block

The <Keypoints> block must be within the singe <Mesh> block and must be the first element in that block. The Keypoints block has the form:

  <Keypoints>
    <pt x='0' y='0' id='lowerleft'/>
    <pt x='0' y='10' id='upperleft'/>
    <pt x='50' y='0' id='lowerright'/>
    <pt x='50' y='10' id='upperright'/>
  </Keypoints>

It can define any number of key points. Each subordinate <pt> command defines a key point, provides its x and y coordinates and gives it an id. The id's can be text or numbers and must all be unique among key points.

Notes

1. A Keypoint command to define a key point can appear by itself or within an Path block, but all Keypoints commands must be within a Path block.
2. To programmatically access keypoint coordinates, you can use the "at" expressions @key.ID.x or @key.ID.y. Here ID is the defined key point id and these expressions return that key point's x or y coordinate.
3. The Keypoint and Keypoints commands are only allowed for FEA analyses.