ANSYS ICEM CFD™ Family_boco (Boundary Conditions) File Format

General Remarks

#: In first column, means that the line is a comment.

"FamName":  The family name always starts the line. It either sits alone, or is followed by a list of boundary conditions in family_boco, or a lost of topological entities in family_topo. The family name is always in double quotes and currently has a length limit of 200.

'\': Whenever the character '\' is encountered, this is interpreted as a line continuation.
'\n': Whenever the character '\n' is encountered, it is interpreted as the end of the line, i.e. end of the information for the particular family. However one can start a new line for the same family anywhere else in the file:

"FamName1" ...
"FamName2" .... \
...
"FamName1"

Special remarks for family_boco

-"string": Boundary condition string. Always in quotes, and current length limit of 200. The string may contain any type of characters: numbers, punctuation, letters (upper or lower case), etc...
- number: Boundary condition floating number. Never in quotes.
- The boco_strings and/or boco_numbers are separated by one or more spaces but not by any punctuation.
- There is no maximum limit on the number of strings and numerical values, nor is there any minimum limit. So all of the following are acceptable:

"FamName" 7 "s1" 1 "s2" "s3" 2 3 4 5 6 7 1 2 3 4 5 6 7
"FamName" 1
"FamName" "s1"
"FamName"

- The boco_strings and boco_nos can be entered in either order, but the order within the string vector and within the float vector are important. So

"FamName" 1 2 3 "s1" 4 "s2"

is equivalent to

"FamName" "s1" "s2" 1 2 3 4

but different from:

"FamName" "s2" "s1" 4 3 2 1

- Family boco ignores the lines where the 1st string is either - maxsize - width - ratio - height - members since these are not boundary conditions but rather mesher parameters.
 

Special remarks for the family_topo file

  - DOMx, SFx, ENx, VTXx, PTFx, PTCx, FSFx: Topological entities in family_topo. These are never in quotes. 'x' must indicate the entity number. All entities must be represented. Entities with no b.c. are all put in the orphan family.
- The order in which the topological entities are listed is not important.
- The family_topo file must only be created for a multi-block mesh.
 

GUI

When a GUI uses the old "General Boundary Condition Menu" string1 string2 Integer, Real1, ... Real9 whatever is entered by a user to the variables string1 and string2 are strings, and whatever is entered in the variables Integer to Real9 are numerical values. It is not necessary to write 2 strings and 10 numerical values to the family_boco file. It is however necessary to enter all the strings up to the last one defined, and all the numerical values up to the last one defined, in order to tranfer the rank information. Therefore, if only string1 is defined, it's ok to write:

"FamName" "s1"

However if only string2 is defined, it's necessary to include a blank string for string1, so that the rank of string2 (2nd string) can be understood by the boco library:

"FamName" "" "s2"

The same is true for the numbers. If only the 3rd numerical value is used, then 3 numerical values should show up. The undefined ones being set to zero:

"FamName" 0 0 1