Contents     Functions              PDF Index

ufread

• 15 Grid point
• 55 Analysis data at node
• 58 Function at nodal DOF
• 82, Trace Line
• 151, Header
• 780, 2412, Elements
• 773, 1710 Material Database
• 772, 788, 789, 2437, Element Properties
• 2414, Analysis data

Purpose

Read from Universal Files.

Syntax

      ufread
      ufread('FileNameOrList')
UFS = ufread('FileName')
UFS = ufread('FileList*.uff') 

Description

The Universal File Format is a set of ASCII file formats widely used to exchange analysis and test data. As detailed below ufread supports test related UFF (15 grid point, UFF55 analysis data at node, UFF58 response data at DOF) and with the FEMLink extension FEM related datasets.

ufread with no arguments opens a GUI to let you select a file and displays the result using feplot and/or iiplot. ufread('FileName') opens an feplot or iiplot figure with the contents. UFS=ufread('FileName') returns either a FEM model (if only model information is given) or a curve stack UFS pointing to the universal files present in FileName grouped by blocks of files read as a single dataset in the SDT (all FRFs of a given test, all trace lines of a given structure, etc.). You can specify a file list using the * character in the file name.

You get a summary of the file contents by displaying UFS

 >> UFS

 UFS = UFF curve stack for file 'example.uff'

 {1} [.Node (local) 107x7, .Elt (local)  7x156] : model        
  2  [.w    (UFF)   512x1, .xf  (UFF)    512x3] : response data
  3  [.po   (local)  11x2, .res (local) 11x318] : shape data   

which indicates the content of each dataset in the stack, the current data set between braces { }, the type and size of the main data fields. For response data (UFF type 58), the data is only imported when you refer to it (UFS(i) call) but it is imported every time you do so unless you force loading into memory using UFS(i)=UFS(i).

The UFS object gives you direct access to the data in each field. In the example above, you can display the modeshapes using

 cf       = feplot;
 cf.model = UFS(1);
 cf.def   = UFS(3);

When loading response data, you may want to transfer all options from the universal file to an iiplot stack entry using calls of the form ci.Stack{'curve','Test'}=UFS(3).If you need to extract partial sets of DOF, consider fe_def SubDof.

15 Grid point

Grid points stored in a node matrix (see node ) in a UFS(i).Node field.

The format is a (4I10,1P3E13.5) record for each node with fields
[NodeID PID DID GID x y z]
where NodeID are node numbers (positive integers with no constraint on order or continuity), PID and DID are coordinate system numbers for position and displacement respectively (this option is not currently used), GID is a node group number (zero or any positive integer), and x y z are the coordinates.

55 Analysis data at node

UFF55 Analysis data at nodes are characterized by poles .po and residues .res (corresponding to DOFs .dof) and correspond to shape at DOF datasets (see more info under the xfopt help).

The information below gives a short description of the universal file format. You are encouraged to look at comments in the ufread and ufwrite source codes if you want more details.

Type specific values depend on the Signification value and are stored in the .r55 field.

58 Function at nodal DOF

UFF58 Functions at nodal DOF (see Response data) are characterized by frequencies w, a data set xf, as well as other options. The information below gives a short description of the universal file format. You are encouraged to look at comments in the ufread and ufwrite source codes if you want more details. Functions at nodal DOFs are grouped by type and stored in response data sets of UFS.

82, Trace Line

UFF82 Trace Line matrix LDraw where each non-empty row corresponds to a line to be traced. All trace lines, are stored as element groups of UFS(1).Elt.

LDraw can be used to create animated deformation plots using feplot.

( ,1:2) [NumberOfNodes GroupID]
( ,3:82) [LineName] (which should correspond to the group name)
( ,83:end) [NodeNumbers] (NumberOfNodes of them, with zeros to break the line)

151, Header

Header stored as a string matrix header (with 7 rows).

780, 2412, Elements

These universal file formats are supported by the SDT FEMLink extension.

773, 1710 Material Database

These universal file formats are supported by the SDT FEMLink extension.

All materials properties are read, but obviously only those currently supported by the SDT are translated to the corresponding row format (see m_elastic and section 7.4).

772, 788, 789, 2437, Element Properties

These universal file formats are supported by the SDT FEMLink extension.

All element (physical) properties are read, but obviously only those currently supported by the SDT are translated to the corresponding row format (see p_beam, p_shell, section 7.3).

2414, Analysis data

These universal file formats are supported by the SDT FEMLink extension.

Note that the list of FEMLink supported dataset is likely to change between manual editions. Please get in touch with SDTools if a dataset you want to read is not supported.

See also

nasread, ufwrite, xfopt