W01 Beam Editor Data File Structure (Version 1.

0)
During execution of beamer.exe, a <name>.E01 file will contain any errors or messages. Read the first line of the
e01 file. If ** ERROR ** then an error description follows until the first space. If ** MESSAGE ** follows, then
a message follows until the first space. Read until the end of file is encountered. If no ** ERROR ** lines are
encountered then there are no errors in the file, and the job can proceed without problem.

Temperatures read in as zero are not used since this is the data card initialization value. If an actual
temperature of zero must be entered, increase or decrease the value by some nonzero amount.

All entered stiffness values must be greater than zero. The absolute value of quantities only allowed to be positive
are automatically taken to minimize the potential for errors.

The setting in the w01 file is used to control the associated units in the form1. advanced seismic control file. If
English or Metric is encountered in a processing w01 file then units are changed at that time. Spectra are stored
internally in English units and then are converted when needed to be written to a particular data file for the type of
dynamic analysis requested. The units type is returned in the e01 error checking file on return from beamer. The
label ** ENGLISH or ** METRIC can be found.

All SPRINGs and RSPRINGs must be double node entities.

User’s may use property lines after the first to augment previous property lines. For example to change the
insulation thickness when passing next to a platform, the input would appear:
PIPE, 14.75, 0.375, 0
STR,1,2
STR,2,3
BND,3,4,5
STR,5,6
STR,6,7 Starting over platform, insulate with PP
PIPE,,,1

Data Card Structure:

Any line starting with a (*), (‘), (“), or (/) is a comment line and is ignored.

ENGLISH – FE/Pipe default English units are used in this file.

METRIC – FE/Pipe default metric units are used in this file
NODE, <id>,<x>,<y>,<z> <node label text>
DNODE, <id>,<x>,<y>,<z>,<id_from> <node label text>
PROP,<Emod>,<nu>,<alpha>,<Tref>
LOAD,<rho_pipe>,<rho_insul>,<rho_refractory>,<rho_liquid>, <Temperature>,<Pressure>
PIPE,<OD>,<Thk><Thk_insul>,<Thk_ref>
STR,<ifrom>,<ito> <element label text>
BND,<ifrom>,<itangent>,<ito>, <radius>,<angle>,<Ki>,<Ko> <element label text>
FIX,<inode>, Kx,Ky,Kz,KRx, KRy, KRz ,<nDisp>, <Reaction label text> … zero stiffness = NO RESTRAINT
TFIX,<inode>,<cx>,<cy>,<cz>, <K> ,<nDisp>, <Reaction label text> … zero stiffness = DEFAULT STIF
RFIX,<inode>,<cx>,<cy>,<cz>,<K> , <nDisp>, <Reaction label text> … zero stiffness = DEFAULT STIF
SPRING,<inode>,<cx>,<cy>,<cz>, <K>, <jnode>, <nDisp>, <Reaction label text> … zero stif = DEFAULT STIF
RSPRING,<inode>,<cx>,<cy>,<cz>,<Kr>,<jnode>, <nDisp>, <Reaction label text> zero stif = DEFAULT STIF
DISPL,<nDisp>, <type>,<Value1>,…<Value6>
FORCE,<inode>,<type>,<Fx>,<Fy>,<Fz>,<Mx>,<My>,<Mz>
SPAR,<ifrom>,<ito>, <K>
STRUC,<Area>,<Ixx>,<Iyy>,<J>,<itype>,<Depth>,<Width>

Paulin Research Group Houston, Texas 1

MEMBER,<ifrom>,<ito>, <angle_to_orient> <element label text>
JOIN,<inode>
GLOB18 – Use 18dof pipe elements as the default
GLOB6 – Use 6 dof pipe elements as the default <default>
RIGID, <value> … enter the default rigid stiffness for supports and components. Used on TFIX, RFIX, SPRING,
RSPRING, and SPAR cards.

ORESTR,<Ki>,< Kj>,< Kk>,< Kl > Ovalization restraints at each nodal cross section. This card must come before
the STR card or BND card whose cross section is restrained, and it will apply only to the single STR or BND card
which follows it in the data listing. (See figure below.)

OSUPT, <#>,<x1>,<x2>,<x3>,<x4>,<x5>,<x6>,<x7> Beam elements supporting ovalization can have supports or

loads applied to the beam surface. These inputs permit these applications. Up to 4 such supports and/or loads can
be defined for each beam segment. The <#> field is used to describe which of these fields is specified. (See figure
below.)

<nDisp> on FIX, TFIX, RFIX, SPRING, and RSPRING cards is used to point to one or more displacement cards
for the fixity. There must be one displacement card per line of action per load case type. <type> on the DISPL
card has the same meaning as the Force <type> described below. 6-13001 can be added as the thermal case #1
displacement. (Used for thermal only runs when 3Sm is exceeded.)

The DISPL card should only have a single displacement value entered for TFIX, RFIX, SPRING, or RSPRING card
types. The DISPL card can have six displacements only when used with a FIX card.

The JOIN command is used to identify nodes that should be “public” to the beam data base that will be created. A
database file with the <name> file will be created each time the beamer.exe is run to error check or to process the
data file. The file will be in a “child” state to be read in as needed. “Child” models in FE/Pipe always come back
into the FE/Pipe model generator. The beamer output files without use of the join, can be run by themselves
without having to use modgen, as long as a load case file is setup.

Force <type> - 1 – 3000 weight

2 – 14001 operating
3 – 14002 – occasional
4 – 14003
5 – 14004
6 – 13001 – thermal

File Manipulation

The spectrum data files have the following format:

Paulin Research Group Houston, Texas 2

 'Should have values from 0 to 5 that are constants to control the
'use of the file:
'A1 , A2, a3, a4, a5, a6
'F1 , g1
'F2 , g2
'…
'fN , gN
'a0-1 if the ZPA entered by the user in the Load screen is DynaVessel is to be used to multiply the spectrum
acceleration values. 0 if the ZPA entered by the user should not be used, i.e. if the spectrum as entered has already
been properly scaled.
'a1-If nonzero, then a constant to multiply the acceleration values in the file. (Used for unit conversions.)
'a2-If nonzero, then the critical damping used to generate the spectrum, and the value that should override any
program value.
'a3-Not used.
'a4,a5 - not used at present, but they must be in the file as zeros.
'Process the control values to be sure of validity

The <name>.dyn file contains basic dynamic load directives.

The <name>.sop file controls which engine to use. In this case it will either be the static solver or EIGEN. Inside
the EIGEN routine there is an harmonic solver, the eigensolver and the transient solver.

Paulin Research Group Houston, Texas 3

File Formats:

Force Data Writing (m1f file)

Note that any 3000 level forces will be included in the mass matrix. Single point loads will be applied in all three
directions when the system is being setup for a dynamic load case.

Concentrated Loads:

First Line
id = 3000(wgt), 14001(ope),14002(occ),14003(thermal)
ident = <node number> (positive, this is how the program knows its not an element load)
ishape = -2 for force, -3 for moment
number of control points = 2 for force 3 for moment
iparent = -1
load type = 0
Second line
force magnitude
<0.0d0>
Third Line (first control point)
<x>,<y>,<z>, <int> coordinate and node for point where load is applied
Forth Line (second control point)
<cx>,<cy>,<cz> <int> cosines of load application.

Thermal:
First Line
id = 13001
ident = -element number (minus the element number)
ishap = -10
number of control points = 10
iparent = 0
load type = 116
Second Line:
temperature (inside)
temperature (outside)
Third Line (the first “control point”)
<real><real><real><int> … used to locate the center for the display of the load (graphic only)
Fourth Line
<0><0><0><0>
Fifth Line
<from end x>,<from end y>,<from end z>, <int> … used to orient the load display (graphic only)
Sixth Line
<to end x>, <to end y>, <to end z>, <int>
Seventh Line & Eight Lines:
if straight then
<delta x>, <delta y>, <delta z>, <int> … from to to
<delta x>, <delta y>, <delta z>, <int> … from to to
else if bend then
<delta x>, <delta y>, <delta z>, <int> … from to center point (tipt)
<delta x>, <delta y>, <delta z>, <int> … center point to to point
end if

Paulin Research Group Houston, Texas 4

Nineth line thru the total number of control points contain information to draw the load in modgen. Not needed for
analysis.

Pressure:
First line
id=11001
ident = -element number
ishape = -8
number of control points = 8
iparent = 0
load type = 112
Second Line:
pressure
0.0
Third Line (first control point – Copy third through eighth lines from thermal load.

Last two lines are zero records.

Weight and Operating:

First Line:
id = 3000 (WEIGHT) = 14001 (OPERATING)
ident = -element number
ishap = -9
number of control points = 9
iparent = 0
load type = 103
Second Line:
weight per length
0.0
Third Line (the first “control point”)
<real><real><real><int> … used to locate the center for the display of the load (graphic only)
Fourth Line
<0><-1><0><0> … this line gives the direction of gravity and is used in the analysis.
Fifth Line
<from end x>,<from end y>,<from end z>, <int> … used to orient the load display (graphic only)
Sixth Line
<to end x>, <to end y>, <to end z>, <int>
Seventh Line & Eight Lines:
if straight then
<delta x>, <delta y>, <delta z>, <int> … from to to
<delta x>, <delta y>, <delta z>, <int> … from to to
else if bend then
<delta x>, <delta y>, <delta z>, <int> … from to center point (tipt)
<delta x>, <delta y>, <delta z>, <int> … center point to to point
end if

Nineth line thru the total number of control points contain information to draw the load in modgen. Not needed for
analysis.

Occasional Uniform Loads:

Paulin Research Group Houston, Texas 5

First Line:
id = 14002
ident = -element number
ishape = -9
number of control points = 9
iparent = 0
load type = 103
Second Line
load per length
0
Third Line
<x><y><z>, <int> … center of element for drawing the load
Fourth Line
<x><y><z>,<int> … direction of uniform load
Remaining Control Point LInes

The first few lines of a typical <name>.m1f file are shown below:
0 53
13001 -1 -10 10 0 116
1.500000e+002 1.500000e+002
5.000000e+001 0.000000e+000 0.000000e+000 -1
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
11001 -1 -8 8 0 112
3.000000e+002 0.000000e+000
5.000000e+001 0.000000e+000 0.000000e+000 -1
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
3000 -1 -9 9 0 103
5.683768e+001 0.000000e+000
5.000000e+001 0.000000e+000 0.000000e+000 -1
0.000000e+000 -1.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
14001 -1 -9 9 0 103
5.683768e+001 0.000000e+000
5.000000e+001 0.000000e+000 0.000000e+000 -1
0.000000e+000 -1.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
14002 -1 -9 9 0 103
1.000000e+000 0.000000e+000
5.000000e+001 0.000000e+000 0.000000e+000 -1
1.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
1.000000e+002 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451
0.000000e+000 0.000000e+000 0.000000e+000 -842150451

Restraint File Format (m1g)

Paulin Research Group Houston, Texas 6

c m1g file format:
c ----------------
c 0 <num items>
c <header rec>
c <load rec>
c <cntrl points>
c
c <header rec> = <id>,<inode>,<ishape>,<no cntrl pts>,<ipar>,<ityp>
c <load rec> = <IFIXITY>,<ustiff>
c <cntrl point #1> - Location of restraint
c <cntrl points #2-4> - direction of translational restraints
c <cntrl points #5-7> - direction of rotational restraints
c
c The control points in the m1g file correspond to the IFIXITY value,
c which is any combination of six 1's or zeros, a "1" indicating that
c there is a support in that slot, the first three for translational
c fixities, and the second three for rotational fixities.
c
c The <ityp> was intended to be used for displacements at a later
c date, but does not look like it was ever implemented. <ipar> is
c not used, and ishape=-7 and "no cntrl pts" = 7.

Structural Section Property Record:

Both the structural and piping data is written to the m1j file. FE/Pipe knows how to use the data in the m1j file
based on the element type in the m1e file. The m1j record for structural shapes is included below:

i 0 -20 20 0 0
Area, Izz, Ixx, <int>
J, Izz/(Depth/2), Ixx/(Width/2), <int> … These values are used to compute stresses (section modulii)
<shape type – see below>, Depth, Width, <int>
<StrongAxis_X>, <StrongAxis_Y>, <StrongAxis_Z>, <int>
<WindDia>,0,0, <int>
.. 15 more lines of 0,0,0, <int>

Structural Shape Types:

The code below is taken from pipe28.t and is used to determine what type of shape should be used to draw the
structural type:

element_type = el_data_type[element_data]
IF element_type ~ '2L' THEN
# Double angle shape is a "T"
shape = 2
ELSE IF element_type ~ 'ST' THEN
shape = 2
ELSE IF element_type ~ 'WT' THEN
shape = 2
ELSE IF element_type ~ 'MC' THEN
# Channel Shape
shape = 4
ELSE IF element_type ~ 'C' THEN
# Channel Shape

Paulin Research Group Houston, Texas 7

 shape = 4
ELSE IF element_type ~ 'L' THEN
# Angle Shape
shape = 3
ELSE IF element_type ~ 'TS' THEN
# Tube shape (square)
shape = 5
ELSE IF element_type ~ 'User' THEN
# User defined shape, use the rectangle.
shape = 5
ELSE
# Default to wide flange shape.
shape = 1
ENDIF

Joining Beam Models Together

There are a number of logic issues involved when two beam models are included together and must connect to each
other as the user wishes.

It is most desireable that connected nodes from one system to another are linked in “stiffness” space, and so can
retain their original geometries. In this way, the shifting of nodes for system consistency does not change the
element geometry. (Collective rounding of fractions through hundreds of feet of pipe can produce significant errors
in the matchup that user’s must be careful with.)

The best alternative here is to get the element dimensions from the original coordinates and NOT from the final
node locations – the node locations being used only for global visualization. As of January 2006, this is NOT done
in FE/Pipe. Beam stiffnesses are based on global coordinates. As the beam solution is improved for DynaPIPE,
this will hopefully be adjusted as more elemental data needs to be passed from the input routine to the element
generator.

Another problem arises when two nodes are at exactly the same point in space, but should not be joined by the
merge nodes command. This is accomplished in FE/Pipe by the user of the parent id. If the nodal parent id is zero,
then it is included in all merge nodes lists, and joined with any other node adjacent to it that is within the specified
merge nodes tolerance. If the nodal parent id is -1, then the nodes on the element are NOT included in the global
merge nodes list. Typically, beams produced by pipe28 have parent ids = -1. By default, beams included in the
database by an include,elements command, produce nodes with a 0 id, and therefore each of these nodes are
included in any merge nodes list and merged geometrically. BEAMER uses the include,elements command, but
also uses the “node_parent_id,-1” command before the include, elements command is issued to set all created nodes
parent id’s to -1 so that they will NOT be included in any merge operation. Nodes appearing in any JOIN list, are
marked for “merging” by the “modify,node,<n>,0” command issued after the include,elemements command, so
that they can be included in the merge nodes list. For BEAMER, any nodes on the JOIN card are also included
(through the respective template) in a “merge_labels” command, so that they are “merged” by their label and not
only by geometry.

The “merge_labels” command is issued by the parent that’s including the children. Modgen searches the element
list to see if one of the nodes connects to a 73 element type (SPRING, or RSPRING in Beamer), and if it does, then
moves this node so that any node connected to an element is not moved. This allows the user to use base nodes on
other pipe runs and NOT have to worry about the nodes being in the same place. If there is no other connectivity in
the model runs that creates a difference in the node locations, the nodes CAN be at the same location and the
SPRING and/or RSPRING inserted between the nodes that are at the same point in space without difficulty. THE
IMPORTANT THING TO REMEMBER HERE, IS THAT ANY LABELED NODE IN A PIPE RUN IS
INCLUDED IN THE JOIN LIST, AND is, by default also in the MERGE NODES LIST.

Paulin Research Group Houston, Texas 8

What this means, is that, any last node in a piping system that’s supposed to be coupled to another node in a system,
and will be right on top of that node (if the Cnode is the only connectivity that exists), then the end node should
NOT be included in the JOIN list, (otherwise it will be merged.)

Paulin Research Group Houston, Texas 9