Test and CAE Data Handling

With a single command, extracts multiple types of information such as requests (for example nodes or elements from a CAE file; channels from a test file) or several components at once (for example X, Y and Z displacements), and therefore returns an output that is a matrix. Instead of declaring multiple readvectorcommands, readmultvectors accomplishes the same output with fewer operations.

readvector and readmultvectors support arguments that can represent a single entity or a range of entities that are to be queried when the initial and final indices are given.

For example, querying an entity list comprised of 1, 10, 15, 16, 17 and 30 could mean a list of channels in a Test file or a list of elements in a CAE File:

When using readvector or readmultvectors, if you provide requests for the initial ID (1 in this case) and the final ID (30), then the requests in between are also read. If you use readcae, only the specified list is read.

The readcae3d is the dedicated function for reading CAE results when at least one of the following needs to be considered: corner data, averaging method, layer or coordinate system.

For all other use cases, readvector, readmultvectors and readcae are recommended.

Depending on the way that CAE results are queried, model information, which is not possible to retrieve from the default HyperGraph readers, may be required. If model information is required, use readcae3d as its underlying mechanism takes the model into account when contouring the results.

• Corner Data: Results based on corner data illustrate the expansion of the scope of the standard CAE readers because this abstraction, which is based on the Finite Element Method, relies on both results and model data:

  
  
  

  A, B, C and D represent the centroid of the elements, whereas A1, B1, C1, D1 and the following numbers represent the integration points of each element.

  The calculations at the centroid correspond to what can be visualized with HyperGraph readers, but these calculations come from individual computations performed at the integration points of each element. The results are then extrapolated to generate the corner data.

  When the corner data option is applied and results such as stress are queried, nodal stress results are obtained, and the requests change from elements to nodes.

• Averaging Method: Due to the limitation of HyperGraph readers, it is not possible to change the averaging method or the coordinate system using solely results available in HyperGraph.

  Nodal averaging of elemental results refers, for example, to the average of all the element corner results passing through a given node.

• Coordinate Systems: CAE results are usually associated with the global coordinate system, but when another system is used, the results should be transformed accordingly:

  
  
  

  This difference of results, depending on the model, affects mainly the data types and components, which means that subcases, time steps and requests (nodes and elements) are the same regardless of the reading mechanism.

• Layers: You can display a contour for a specified element layer if the definition for the element layer is available. In some cases, layers do not apply, such as with mass or solid elements.