*Element Set

<< Click to Display Table of Contents >>

Navigation:  Flexcom > Data Inputs > $DATABASE POSTPROCESSING >

*Element Set

Previous pageNext page

Purpose

To group individual elements into element sets.

Theory

Refer to Database Postprocessing for further information on this feature.

Keyword Format

Blocks of lines that define a set repeated as often as necessary. Each block begins with a line defining the set name. This is followed by various types of lines that define the elements in the set. These lines can be mixed and repeated as often as necessary until every element in the set is defined.

Line to define set name:

SET=Set Name

Line containing a list of elements. This line can contain up to 20 elements (numbers or labels). Any further elements must be defined on a new line.

List of Elements (Numbers or Labels)

Line defining a sequence of elements:

GEN=Start Element (Number or Label), End Element (Number or Label) [, Element Increment]

Line referencing another set of elements:

SUBSET=Subset Set Name

The set ALL is predefined and cannot be redefined. Every element assigned to a set must be defined using *ELEMENT. Set names are up to 256 characters long, can include spaces and are case insensitive. If you specify an element label rather than an element number, it must be enclosed in {} brackets. Element Increment defaults to one.

Table Input

Input:

Description

Set Name:

A unique label for the element set. Set names are not case sensitive, so the set name ‘RISER’ is equivalent to ‘Riser’, which is in turn equivalent to ‘riser’.

Elements:

The elements comprising the set. These can be input in three ways, namely:

(i)A list of elements (numbers or labels), such as for example “1, 5, 7”.

(ii)A group of consecutive elements (numbers or labels), input using the format: “11 – 15”. This definition specifies Elements 11 to 15 inclusive. The specification “11 - 15 – 2” can be used to specify the Elements 11, 13 and 15 - that is, from Element 11 to Element 15 in steps of 2.

(iii)Another set name. For example you might define three sets named SET_1, SET_2 and SET_3, and then combine them in a further set, say ALLSETS, by inputting “SET_1, SET_2, SET_3”.

If you specify an element label rather than an element number, it must be enclosed in {} brackets.

All three specifications can be combined, as for example in “1, 7, 9, 12-15, 17, 20-50-10, RISER”. This set combines Elements 1, 7, and 9; elements 12 to 15 inclusive; Element 17; Elements 20, 30, 40 and 50; and the elements comprising the set RISER.

SubSets:

An additional element set or sets whose elements are to be added to the current set definition. If more than one set is referenced, use commas to separate out the set names.

Notes

(a)Use as many lines as you need to completely define the elements comprising a particular set. Simply leave the first column blank for second and subsequent lines.

(b)If a set name is included in the specification of another set, then obviously the elements comprising that set must be separately defined.

(c)There is one predefined element set in Flexcom, which is named All. Not surprisingly this comprises all of the elements of the finite element discretisation and is the default element set. Note that Flexcom will resist any attempt to redefine the make-up of the set All.

(d)The names and composition of element sets you define in a preceding section carry through to all dependent (restart) sections. For example, if you define an element set in the $MODEL section, it will automatically be available in a subsequent $DATABASE POSTPROCESSING section. So there is no need to repeat the specifications again – you can just use the set names directly. If you redefine the composition of a set previously defined in a preceding section, Flexcom will output a warning, but will continue with the most recent set definition.