This module reads in a PHOENICS results file (sequential access) and creates a 3D lattice from the information contained therein. If the PHOENICS results are from a BFC calculation, the user must also supply the name of the (sequential access) XYZ file containing the grid coordinates.

PHOENICS evaluates scalar data (like pressure) at cell centres. and vector data (like velocity) at cell faces. This module interpolates both types of data to cell corners, using the facial areas and volumes of the cells. Before interpolating the vectors, it generates values for them on the high x, y and z planes using linear interpolation. If flow is wrapped in the x direction, the u component of the velocity for the high x plane is copied from the u component for the low x plane.


Port: PHI Filename
Type: Text
Input PHOENICS data (phi) file. This is also accessible via the browser on the PHI file item on the File pull-down menu.

Port: XYZ Filename
Type: Text
Input PHOENICS xyz file, if required. If the phi file is from a cartesian or cylindrical grid, this widget is hidden. This is also accessible via the browser on the XYZ file item on the File pull-down menu. The module will check the dimensions of the grid specified in this file against those specified in the phi file, and will exit if they are incompatible.


Port: Output Lattice
Type: Lattice
Constraints: 3-D
Constraints: float
Constraints: perimeter..curvilinear
Output lattice containing the PHOENICS data. Each component of the data (P1, P2, U1, etc) is put into a separate channel. After reading the data file, the module outputs a message identifying which channel contains each component. The numbering of the channels in this message is 1-based, which is the same convention used by the MultiChannelSelect(1EXP) module to select channels from a multichannel lattice.

A perimeter lattice is generated if the grid is cartesian and a curvilinear lattice is generated if the grid is cylindrical or BFC.


The error checking on the read is only rudimentary. Thus, a corrupted or badly formatted input file could cause the module to exit obscurely.


[Documentation Home]
© The Numerical Algorithms Group Ltd, Oxford UK. 2000