PARC Interface
| S |
The PARC interface writes an input file and a grid file for the modified PARC flow solver. The input file contains the following sections:
Block Parameters:
The block parameters can only be defined on domains (blocks). After selecting a domain, enter the different block parameters in the boundary condition menu:
MULCAD DDN-Mesher ------ ---------- 1.FLAG 1.string1 Enter the string: BLOCK 2.NR 3.integer Enter value of ivisc1 3.VALUE 4.real1 Enter value of ivisc2 4.X 5.real2 Enter value of ivisc3 5.Y 6.real3 Enter value of lamin1 6.Z 7.real4 Enter value of lamin2 7.SCALE 8.real5 Enter value of lamin3 8.A 9.real6 Enter value of ispect 9.B 10.real7 Enter value of ifiltr 10.C 11.real8 Enter value of splend 11.D 12.real9 Enter value of gamma 12.ATTRIB 2.string2 Enter value of dtblkAll block parameters have a default value of zero except gamma which equals 1.4 by default. The value of dtblk is written in a character field (ATTRIB) and is limited to 5 characters long.
Subblock Operators:
The subblock operators are used to define boundary conditions, geometry drivers, open-loop controls, sensors or close-loop controls. The subblock operators can be defined on domains, subfaces, edges or vertices. After selecting a topological entity, defined the subblock operator in the boundary condition menu. Each subblock operator is characterized by a type, a certain number of integer value(s) [0-3], floating point value(s) [0-6] and character strings [0-2]. These must be entered in the boundary condition menu in the following order:
MULCAD DDN-Mesher ------ ---------- 1.FLAG 1.string1 Enter first char. string if applicable 2.NR 3.integer Enter type 3. to 11. 4. to 12. Enter integer or real value(s) if applicable 12.ATTRIB 2.string2 Enter second char. string if applicableThe entries #3 to #11 in the MULCAD menu can take up to 9 numerical values. First enter as many integer(s) as needed, then as many real as needed. The order in which these numerical values are entered in the "Unspec. Bound. Cond." menu is going to be the order in which they will appear in the PARC input file.
Example:
To define a sensor type 3941 which requires 1 integer, 1 real and 1 character string, select the topological entity for the sensor then:
MULCAD DDN-Mesher ------ ---------- 1.FLAG 1.string1 Enter the char. string 2.NR 3.integer Enter the type 3.VALUE 4.real1 Enter the integer value 4.X 5.real2 Enter the floating point valueThe subblock operator types recognized by this interface are:
category type integer(s) real(s) char.string(s) _______________________________________________________________________ Boundary Conditions 2120 0 0 0 2125 0 3 0 2320 0 2 0 2321 0 0 1 2220 0 0 0 2310 0 2 0 2211 0 2 0 2212 0 2 0 2420 0 5 0 2421 0 2 0 2410 0 0 0 2510 0 0 0 52 0 0 0 2430 0 0 0 2431 0 1 0 70 0 0 0 1210 1 0 0 73 1 0 0 1217 1 0 0 2540 1 0 0 2330 1 2 0 1110 0 0 0 2530 0 0 0 _______________________________________________________________________ Geometry Drivers 3920 0 1 0 3924 3 4 0 _______________________________________________________________________ Open-loop Controls 3930 2 6 0 _______________________________________________________________________ Sensors 3940 2 0 1 3941 1 1 1 3942 1 0 1 3943 1 0 2 _______________________________________________________________________ Close-loop Controls 3950 2 0 1 _______________________________________________________________________Turbulence Model:
The turbulence operators are defined the same way as the subblock operators. The only difference is that the first character string must be TURBL.
Example:
To define a turbulence operator type 3515 which requires 2 integers, 2 reals and 1 character string, select the topological entity for which the operator applies then:
MULCAD DDN-Mesher ------ ---------- 1.FLAG 1.string1 Enter the string: TURBL 2.NR 3.integer Enter the type (here 3515) 3.VALUE 4.real1 Enter the first integer value 4.X 5.real2 Enter the second integer value 5.Y 6.real3 Enter the first floating point value 6.Z 7.real4 Enter the second floating point value 12.ATTRIB 2.string2 Enter the character stringThe subblock operator types recognized by this interface are:
type integer(s) real(s) char.string(s) _____________________________________________ 3510 6 1 0 3515 2 2 1 3520 0 1 0 3530 0 0 0 3540 0 0 0 3910 3 0 1 3915 2 0 0 _____________________________________________Note that the default value for all numerical data of all subblock and turbulence operators is zero.