NPARC export supports 2D and 3D structured grids only. When you export BC data for NPARC you must first set several parameters specifying exactly how you would prefer the BC file to be formatted. You can choose from ASCII, Binary, and Unformatted formats and either Single or Double precision. You can also specify byte order at export using either the Native or Swap Bytes options. Native byte order is the default selection.
Boundary condition export style, version and Mach number can all be specified using the Set Solver Attributes command (Cae, Set solver attributes, Nparc). Fidelity Pointwise's formatting of the NPARC BC file includes:
A 2 line comment string.
An INPUTS name list containing NBLOCKS.
An empty TURBIN namelist.
For each block...
A one-line comment containing the block name.
A BLOCK namelist containing JMAX, KMAX, and LMAX
(if 3D blocks), NBCSEG, and NPSEG.
Either the BOUNDS namelists or formatted BC data.
INVISC and LAMIN namelist inputs.
Note that the PRESS and TEMP inputs required by some BCs are not set by Fidelity Pointwise. If namelist style is used for the BCs, then Fidelity Pointwise sets PRESS and TEMP equal to "?P" and "?T", respectively, when required by the BC. If formatted style is used for the BCs, then Fidelity Pointwise includes the strings (PRESS) and (TEMP) in the appropriate fields. It is up to you to supply the correct values for PRESS and TEMP.
Also note that for NPARC a block interface or connection must be a block max. face to a block min. face. Block connections not of this standard will be flagged as Type 3 (non-conformal) BCs.
NPARC's grid file actually contains both grid and flowfield data. Its' format is described in "Cooper, G.K., and Sirbaugh, J.R., "PARC Code: Theory and Usage", AEDC TR-89-15, United States Air Force Arnold Engineering and Development Center, 1989".
Note that more NPARC solver attributes are available in CAE, Solver Attributes, NPARC