4
Dataset 15 - Test Locations (Points) This dataset is interpreted when the TEST data type is specified. Record 1 (4I10,3E13.5) Field 1: External point number. Field 2: Definition coordinate system number. Field 3: Displacement coordinate system number. Field 4: Not used. Fields 5 to 7: Coordinates of the node in the definition system. The coordinates are assumed to be in the global Cartesian coordinate system. Record 1 is repeated for each node. Dataset 82 - Trace Links This dataset is interpreted as TEST data type or as FE data. If imported with the UF FEM interface, then the trace links are stored as PLOTEL tables. Record 1 (3I10) Field 1: Not used. Field 2: Number of entries in the display sequence (N) Field 3: Not used. Record 2 (80A1) Not used. Record 3 and following (8I10) Fields 1- N: Entries defining the display sequence (8 values per record). The display sequence is converted into point connections each connecting 2 points. Zero entries in the display sequence indicates a 'pen up' position and hence no connection is created. Example: 1 2 3 0 5 6 7 1

Datasets UFF

Embed Size (px)

DESCRIPTION

explication des fichiers UFF avec FEMTools

Citation preview

Dataset 15 - Test Locations (Points)This dataset is interpreted when the TEST data type is specified.Record 1 (4I10,3E13.5)Field 1: External point number.

Field 2: Definition coordinate system number.

Field 3: Displacement coordinate system number.

Field 4: Not used.

Fields 5 to 7: Coordinates of the node in the definition system.

The coordinates are assumed to be in the global Cartesian coordinate system.Record 1 is repeated for each node.

Dataset 82 - Trace LinksThis dataset is interpreted as TEST data type or as FE data. If imported with the UF FEM interface, then the trace links are stored as PLOTEL tables.Record 1 (3I10)Field 1:Not used.

Field 2:Number of entries in the display sequence (N)

Field 3:Not used.

Record 2 (80A1) Not used.Record 3 and following (8I10)Fields 1- N:Entries defining the display sequence (8 values per record).

The display sequence is converted into point connections each connecting 2 points. Zero entries in the display sequence indicates a 'pen up' position and hence no connection is created.Example:1 2 3 0 5 6 7 1becomes:Trace link 1 connecting points 1 and 2Trace link 2 connecting points 2 and 3Trace link 3 connecting points 5 and 6Trace link 4 connecting points 6 and 7Trace link 5 connecting points 7 and 1The connection numbers are automatically determined by the interface program. A connection is created if between two consecutive entries, none is zero.Dataset 55 - Test Data at PointsThis dataset is interpreted when the TEST data type is specified.This dataset type is used to read operational and mode shapes. No other analysis results are interpreted by the interface program when the TEST data type is specified. For each mode shape, a new dataset 55 is used. The number of shapes in the FEMtools database will be equal to the number of occurrences of dataset 55.Records 1 to 5 (80A1) are not used.Record 6 (6I10)Field 1: Model type. This must be 1 (= structural model).

Field 2: Analysis type. This value can be2: normal modes3: complex eigenmodes (first order)5: frequency response7: complex eigenmodes (second order)

Field 3: Data characteristics.2: 3 DOF global translation vector (NDV=3)3: 6 DOF global translation and rotation vector (NDV=6)

Field 4: Response type. This value can be0: undefined8: displacements11: velocity12: acceleration

Field 5: Data type. This value can be2: single precision real3: single precision complex (old format)5. single precision complex

Field 6: Number of data values per point (NDV = a number between 1 and 6).

Notes- If the Data Type in Field 5 Is complex, then the Analysis Type is considered to be complex eigenmodes, even if it is defined as normal modes.- If Response type is undefined (field 4), and Analysis type = 5 (Field 2), then the translator assume operational shapes are displacements. In addition, a warning is displayed that an undefined response type was detected.- The mode shapes are read in sequential order, which determines the mode number. The total number of modes is equal to the number of appearances of dataset 55.The interpretation of the following records is depending on the analysis type. Analysis type = 2 (normal modes)Record 7 (8I10)Field 1:2

Field 2:4

Field 3: Not used.

Field 4: Mode number (not used).

Fields 5 to 8:Not used.

Record 8 (6E13.5)Field 1: Frequency (Hz)

Field 2: Modal mass (not used).

Field 3: Modal viscous damping ratio.

Field 4: Modal hysteretic damping ratio .

Fields 5 to 6: Not used.

Record 9 (I10)Field 1: External point number.

Record 10 (6E13.5)Fields 1 - 3:Modal shape data at this point (NDV real values).

Records 9 to 10 are repeated for each point.Analysis type = 3 (complex modes)Record 7 (8I10)Field 1:2

Field 2:6

Field 3: Not used.

Field 4: Mode number (not used).

Fields 5 to 8:Not used.

Record 8 (6E13.5)Field 1: R1Real part of eigenvalue (rad/sec)

Field 2:R2Imaginary part of eigenvalue (rad/sec)

Field 3: Real part of Model A (not used).

Field 4: Imaginary part of Model A (not used).

Field 5: Real part of Model B (not used).

Field 6: Imaginary part of Model B (not used).

Record 9 (I10)Field 1: External point number.

Record 10 (6E13.5)Fields 1 - 6:Mode shape data at this point (NDV pairs of real and imaginary values).

Records 9 to 10 are repeated for each point.Complex eigenvalues are converted into Hz by the interface program taking SQRT(R1*R1+R2*R2)/(2*PI). Complex mode shape data is stored as complex data in the FEMtools database. Normalization is possible in FEMtools with the command NORMALIZE. Refer to the FEMtools User or Command Reference Manual for more information.