Professional Documents
Culture Documents
Chapter 3 LUSAS File Types: Annotating The Model
Chapter 3 LUSAS File Types: Annotating The Model
Chapter 3 LUSAS
File Types
LUSAS uses a significant number of different file types for a varied range of
purposes. This diagram shows the manner in which external files link with LUSAS
and related programs. The file types covered are summarised below.
q Model Files (mdl) are created by LUSAS Modeller and are used to store all
model definition information.
q Analysis Data Files (dat) are created by LUSAS Modeller during the
tabulation phase. They are required by LUSAS Solver in order to perform an
analysis.
q Results Files (mys) are created by the LUSAS Solver and contain all of the
analysis results for access by LUSAS Modeller. Results files are also referred
to as plot files.
q Command Files (cmd, vbs, jva) contain a collection of LUSAS Modeller
commands so that, when they are replayed, a sequence of operations may be
carried out automatically. Command files can be recorded by LUSAS
Modeller or edited directly using a text editor. See also LUSAS Programmable
Interface.
q Session Files (ses) are created automatically by LUSAS Modeller every time
LUSAS Modeller is run. They contain a record of all commands issued
during a session.
q Interface Files (dxf, igs, lyp, def, lms)
allow graphical structural
information to be exchanged between LUSAS Modeller and external
packages.
q Picture Files (pic) allow the screen contents to be saved in a neutral file
format. Picture files are used to subsequently display the information or, in
conjunction with the expose program, to create files which may be printed or
plotted.
q Start-up Files (str) are user-defined files which are created to control the
LUSAS Modeller initialisation sequence. They can contain system parameter
information and/or LUSAS Modeller initialisation commands.
21
Model Files
Model files contain all the information regarding the current LUSAS database and
settings. The information is stored in an unformatted binary form and may only be
accessed using LUSAS Modeller. A model file is not saved automatically, LUSAS
Modeller prompts on exit as a reminder to save changes to a model file.
File manipulation is controlled using sub-menu entries below the main File menu,
giving access to the following facilities:
q New Prompts to close an existing model file if open, and opens a new
model file. Model initialisation will delete all feature, attribute and utility
datasets and re-read any start-up files carrying out any configuration
instructions contained in them.
q Save or Save As The current model may be saved to disk at any time by
selection of either the Save option or the Save As... option. Save As allows
specification of a alternative filename. If Save is used on a new model a
filename is required. LUSAS will prompt for confirmation to proceed if a
non-standard file extension is entered, or if a file already exists with the given
name.
Note. LUSAS stores all actions carried out during a session in a temporary session
file, which is deleted upon exit from the program. To avoid losing work carried out
during the session, the model should be saved to disk before exiting LUSAS.
q Open Previously saved model files may be opened by selecting the required
model file using the File Selector dialog box. LUSAS may prompt for
confirmation before the currently loaded model is overwritten. Files may be
opened with read only status to prevent accidental alteration.
q Close Closes the currently open file.
Under the UNIX operating system, LUSAS will ensure binary-compatibility of model
files across different platforms. Model files may also be prepared such that they can
be accessed on a PC, using the system parameter NOTNAT. Setting this parameter
to 1 in the LUSAS start-up file swaps the byte-order when the model is saved.
22
q Restart File Configures the LUSAS data file to create a LUSAS restart
file.
q Load output file Loads the output file created during the solution process.
23
24
Results Files
2. Load the linear model file containing the pre-processing information from the
linear static analysis using File > Open.
3. Edit any properties and define any additional control datasets required.
4. Load the results from the linear analysis using File > Open, change the file
extension to .mys then select the file to open.
5. Display the deformed mesh by adding the Deformed Mesh layer .
6. Now tabulate the deformed mesh using File > LUSAS Datafile, and select
Deformed option from the LUSAS Datafile dialog.
Results Files
When an analysis is performed by LUSAS Solver it will create a LUSAS results file.
The LUSAS results file, or plot file as it is sometimes referred to, has a .mys
extension. A PLOT FILE line, requesting that a results file written, is automatically
added to a linear analysis data file during the LUSAS Modeller tabulation process.
However, for an analysis that uses a control section, such as nonlinear, transient or
dynamic analysis, it is necessary to specify how often results are required by
supplying a number of increments after which LUSAS Solver will write results to the
plot file.
The information in the results file is stored in an unformatted or binary form and
may only be accessed using LUSAS Modeller. The plot file will contain the results of
the analysis and sufficient model information to post-process the results. Full details
of the finite element mesh (nodes and elements), material and geometric property
numbers, support positions and equivalent nodal loads are stored in the results file.
To access results from the LUSAS analysis, files can be opened in a similar way to
model files. See also Results Processing.
Note. Results files may be opened for write access, in a similar manner to model
files, allowing any defined combination, envelope or fatigue datasets to be saved with
the results file. Use the menu entry Files > Results File > Read With Write Access
to open the results file.
Command Files
Command files may be created and used to store a sequence of LUSAS commands
for replay at a later stage. Command files are particularly useful for subsequent
reproduction of pictures or for storing combinations of commands which are used
frequently. The following lists some suitable uses for a command file approach:
q Properties standard property definitions.
q Mesh Divisions standard set of mesh discretisation datasets.
25
26
Command Files
DEF LI 1 1 2
DEF ME "line" BEAM 5
1@1
3@2
1@1
ASSI ME LI 1 1
DRA ME
DRA NOD LAB
or an expanded form:
DEFINE POINT PN=1 X=0 Y=0 Z=0
DEFINE POINT PN=2 X=10 Y=0 Z=0
DEFINE LINE BY_POINTS LN=1 PN=1;2
DEFINE MESH BY_NAME IMSH=1 FEATYP=LINE LNAME=BEAM
NMBELM=5 RATIO=1@1 3@2 1@1
DRAW MESH COLOUR=100.100.100 LTYPE=0
DRAW NODEL LABEL HEIGHT=4.0 ROTATION=0.0
COLOUR=0.100.100
There are several advantages in using the expanded form of command files. All
parameters are specified including default parameters, such as colours. This makes
the expanded form more readily understandable:
DRA ME => DRAW MESH COLOUR=100.100.100 LTYPE=1
Optional parameters can be omitted from a command file without the need to use
commas:
DRA ME ,, 1 => DRAW MESH LTYPE=1
Parameters from most commands may be specified in a non-default order:
DEF POI 1 5 10 8 => DEFINE POINT PN=1 Z=8 X=5 Y=10
Abbreviated commands may prove to be non-unique and cause errors in future
versions if new commands are added. It will therefore be easier to maintain upwards
compatibility between software versions if the full versions are used.
Case Study. Recording a Macro
A macro can be thought of as a series of commands that can be used again and
again. In LUSAS, macro recording is controlled using the command file facility. A
command file may be opened at any time and a series of commands recorded. Once
stored, the command file may then be replayed at a later stage to execute that
recorded sequence of commands. To record a macro, carry out the following steps:
27
28
Print Files
1. Open a new sub-session file using Files > Command File > Open recording.
2. Invoke expanded files using Files > Command File > Expand.
3. Open the abbreviated command file using Files > Command File > Open. The
commands it contains will be replayed and expanded into the active sub-session
file.
4. Close the sub-session file using Files > Command File > Close. The LUSAS
sub-session file, will now contain the full expanded form of the replayed
command file.
Print Files
When any information is printed in LUSAS, it is sent by default to the text output
window. This output may alternatively, or in addition, be re-directed to a print file.
A print file has a .prn extension.
Print file manipulation is controlled using menu entries below the main Files >
Print File menu. The following facilities are available:
q Open The print file is opened by specifying a valid filename. LUSAS will
prompt for confirmation to proceed if the specified file already exists or if a
non-default file extension is used. All printed output is re-directed from the
text output window to the print file while it is open. Output to the screen can
be maintained while a print file is open by selecting the Print to Screen as
Well when Printing to File button in the Files > Options dialog box.
q Close The print file may be closed at any time. With no print file open,
printed output will be re-directed to the text output window.
q Annotate Lines of text can be added to the top of a print file beneath any
header and title information. The annotation settings are controlled using the
menu entry shown here. Apart from information advantages, print file
annotation can be useful for storing the contents of parametric variables,
especially if they are required as input to a user-defined external program or
awk script. See the chapter titled Parametric Language later in this manual
for full details.
Formatting Print Files
Print file page layout format is controlled using the Files > Print File > Page
Format menu entry. Control of centre-, right- and left-justified headers, footers and
titles is provided. Headers and footers appear on every page while titles appear on
the first page only unless output on every page is requested. One blank line is
automatically added between header and title rows in the print file and two blank
29
Description
$CD
$CV
$DT
Current Date
$LV
$MD
$MV
$PN
Page number
$PT
$VN
$Evuser
Tip. Environment variables may be used in page format macros. This may be
useful for automatically picking up the name or telephone extension of an engineer
and adding it to printed output using a standard company page definition. The
environment variable may consist of any valid text string. On a PC, environment
variables are set using the DOS set command, and under UNIX the setenv command
is used. For full details of how to set environment variables consult the
documentation supplied with your system.
To remove all page format information select Files > Print File > Disable Page
Format.
30
Print Files
Case Study. Page Formatting of Text Output
The page format of the standard output of any LUSAS print command can be set as
follows:
1. Choose to set the page format using File->Print File->Page Format.
2. Set the number of columns to 80. Set the number of lines per page to 60. In the
left justified header field add a title, e.g. BEAM RESULTS. In the right justified
header field add the date by entering the macro $DT.
3. Enter LUSAS $VN in the left justified footer field. This will include the LUSAS
version number in this position. Add Page $PN in the right justified footer field.
This will include the current page number. In the left justified title field add $PT
which will insert the main problem title from the analysis data file. Finally, select
the Add a Page Throw Character option and OK the dialog box.
4. Annotation can be added to the print file using File > Print File > Annotation If
required. Annotation will appear in the print file below any header fields.
5. Print some results to the file, for example print displacements using PostView >
Nodal Results > Print Components.
6. Close the print file using Files > Print File > Close.
The resulting text output will be formatted as follows:
BEAM RESULTS
24/02/97
LINEAR STATIC ANALYSIS OF A CURVED CANTILEVER
LINEAR/DYNAMIC ANALYSIS
Current Results File = /gillian/anderson.mys ID
Current Selected Load ID
DX
DY
THZ
RSLT
1
.0000E+00
.0000E+00
.0000E+00
.0000E+00
3
.0000E+00
3.420
5.893
-4.799
-.2740E-01
4
.0000E+00
.6200
.6410
-.1629
-.1520E-01
31
.0000E+00
DU
5
.0000E+00
1.901
2.169
-1.044
-.2364E-01
6
.0000E+00
3.005
4.047
-2.711
-.2692E-01
7
.0000E+00
.0000E+00
.0000E+00
.0000E+00
.3147E-
01
8
.0000E+00
.0000E+00
.0000E+00
.0000E+00
.7655E-
01
9
.0000E+00
.0000E+00
.0000E+00
.0000E+00
.9843E-
01
.0000E+00
.0000E+00
10
.0000E+00
.0000E+00
-.1048
LUSAS 12.1-0
Page 1
32
POINT
Point
LINE
Straight Line
3DLINE
Straight Line
ARC
Arc Line
CIRCLE
POLYLINE
Spline Line
SOLID
Straight-edged Surface
3DFACE
Straight-edged Surface
TRACE
Straight-edged Surface
POLYGON MESH
POLYFACE MESH
Bicubic Surface
Extended Entities
Not supported.
Tip. Units and entity orientation can be modified by defining a local coordinate set
and making this the default before importing. For example, the units may be
33
q The amount of information which may be transferred via the DXF file is
limited due to limitations in the DXF file format (for example, a volume
cannot be expressed in standard DXF data).
q AutoCAD version 13 uses DXF extended entities for some items. LUSAS
does not support import of extended entities and will warn to this effect if an
AutoCAD version 13 DXF file is detected.
q Closed surfaces are not translated by LUSAS.
q Closed poly-lines and three-sided polygon meshes are not translated.
DXF Export
A DXF interface file may be created from LUSAS for use in an external program.
LUSAS datasets are converted into their equivalent DXF entity. Control over the
amount of information exported is provided, i.e. All or Active features and/or mesh
may be specified. This is valid for both pre-processing model files and results files.
The following parameter is available on the export dialog to control creation of DXF
files:
q Level Indicator indicates whether Features Only, Mesh Only or
Features + Mesh are to be exported. The level indicator is only required
when a model file is open and features are active. When no model is active,
such as during post-processing, only the mesh is exported. Additional options
are available to include Volume mesh entities in the export process. Only
element faces are exported when exporting Volume feature mesh records.
LUSAS feature types supported by the DXF export facility are listed in the table
below:
LUSAS Feature/Mesh
3DLINE
ARC
POLYLINE
3DFACE
3DLINE/ARC/POLYLINE
3DLINE
POLYFACE MESH
34
LUSAS Feature/Mesh
PLOYFACE MESH
35
Description
100
Circular arc
102
Composite
curve
Combined Line.
104
Conic arc
Spline Line
106
Copious data
108
Plane
Surface.
110
Line
Straight Line.
112
Parametric
spline curve
114
Parametric
spline surface
116
Point
Point.
118
Ruled surface
Surface.
120
Surface of
revolution
122
Tabulated
cylinder
Surface.
124
Transformation
matrix
126
Rational Bspline
36
IGES Entity
Description
128
Bicubic Surface.
130
Offset curve
Currently unsupported.
140
Offset surface
142
Curve on a
parametric
surface
144
Trimmed
parametric
surface
Title
LUSAS Equivalent
25
Title
26
Time/Date/Vers
ion
31
grid
Point.
32
line
33
patch
34
hyperpatch
Volume.
47
trimmed surface
Tip. Imported PATRAN data is particularly suited to tidying, since all defined
geometry is spline data. See Tidying Imported Lines and Surfaces for more details.
37
Type 8.
CL (Concentrated load)
Type 7, 15.
Not supported.
Type 6.
Type 6, 16.
Not supported.
Not supported.
Not supported.
Not supported.
Type 10.
Type 11.
Not supported.
Not supported.
Not supported.
The following table details supported and unsupported Packet Types in the PATRAN
Neutral File exported by LUSAS.
Packet
Title
Description
01
Nodal Data
Fully supported.
02
Element Data
38
Packet
Title
Description
03
Material
Properties
04
Element
Properties
05
Coordinate
Frames
06
Distributed
Loads
39
Packet
Title
Description
Node Forces
08
Node
Displacements
09
Bar Element
Initial
Displacement
Not supported.
10
Node
Temperatures
11
Element
Temperatures
12
DOF Lists
Not supported.
13
P/MECHANIS
M Entities
Not supported.
14
MPC Data
15
Nodal Heat
Source
40
Packet
Title
Description
16
Distributed Heat
Source
17
Convection
Coefficients
18
Radiation
Emissivity
Values
19
View Factor
Data
Not supported.
21
Named
Component
Definition
25
Title Card
Supported.
26
Summary Data
There are two system parameters that will affect the format of the resulting
PATRAN neutral file:
q PATVER Version number printed in the summary. The default value is 2,
which will print 2.5 in the summary data packet. If data from PATRAN
version 3 or higher is required, this parameter should be set to 3.
q ELMPRP controls the formatting of the element properties (04) and
element data (02) packets, which are different for PATRAN version 2.5 and 3
and above. If the PATRAN neutral format for version 3 or above is required,
this parameter should be set to 3. If this parameter is not set, or if it is set to
anything other than 3, then a PATRAN 2.5 neutral file will be created.
System parameters can be set in a start-up files.
41
Details
Geometric Properties
Composite Geometry
Geometric Assignments
Material Properties
Composite Material
Properties
Composite Assignments
42
Picture Files
About Picture Files
Picture files may be used for storing graphical information in a neutral format for
subsequent redisplay in LUSAS or for conversion to plotter-dependent graphics files.
Picture files are stored in readable text format using the format shown in the table
overleaf.
Manipulation of Picture Files
Picture files may be save using the File > Picture Save menu entry in either .pic or
.wmf format.
Note. Picture files are written only during the graphical operations that draw
information to the screen, they cannot be opened in retrospect once the required
picture has been created.
Warning. If the screen is erased, either wholly or partially, while a picture file is
open, the picture file will be initialised and all previous contents will be lost. This
mistake is especially easy to make when working with sub-windows. Also, if a
section of the screen is selectively erased by use of annotation in the background
colour this will be recorded by the picture file, but its treatment when obtaining a
hardcopy is plotter dependent.
Picture File Format
Picture files are stored in readable text format. The individual picture file records use
the following general format:
code, r1, r2, r3, r4, i1, i2, i3
format (i5, 4f10.3, i10, 2i5)
This information can be used to write programs that will read information stored in
the picture file and carry out additional processing. The information is stored in
packets of data as defined in the following table.
44
Picture Files
Code
Function
Parameters
Description
Move
r1, r2
Draw
r1, r2
Symbol
Character
Colour
r1, r2, r3
r1
r1, r2
10
Polygon
Fill
Window
Coordinat
es
45