openfoam/applications/utilities/mesh/conversion/fluentMeshToFoam
Mark Olesen a32a915d2e BUG: polyMesh removeFiles side-effect for blockMesh viewer (issue #346)
- polyMesh constructor from cell shapes invoked 'removeFiles'.
  This may or may not be what the caller wants or expects.
  With the ParaView blockMesh viewer, this behaviour causes deletion of
  all mesh data (points, faces, etc) when the viewer is refreshed.

  Triggered even when just building the blockMesh topology.

- only a few places that construct a polyMesh from cell shapes
  (mostly mesh conversion utilities).
  Ensure that the file removal (if any) occurs in the application
  and *not* as a side-effect of calling the polyMesh constructor.

--

  blockMesh (application)
    - The placement of the removeFiles seems to also remove freshly
      generated sets (Bug or feature to remove sets?)

  +-----------------------+---------------+------------------+
  | Application           | Constructor   | removeFiles      |
  |                       | (patch info)  | new / existing   |
  +-----------------------+---------------+------------------+
  | blockMesh             | dictionary    | existing         |
  | ansysToFoam           | names         | new              |
  | cfx4ToFoam            | dictionary    | new              |
  | fluentMeshToFoam      | names         | new              |
  | gambitToFoam          | dictionary    | new              |
  | gmshToFoam            | names         | new              |
  | ideasUnvToFoam        | names         | new              |
  | kivaToFoam            | dictionary    | new              |
  | mshToFoam             | names         | new              |
  | netgenNeutralToFoam   | names         | new              |
  | plot3dToFoam          | names         | new              |
  | tetgenToFoam          | names         | new              |
  | vtkUnstructuredToFoam | names         | new              |
  +-----------------------+---------------+------------------+
2016-12-15 19:07:05 +01:00
..
Make Creation of OpenFOAM-dev repository 15/04/2008 2008-04-15 18:56:58 +01:00
cellShapeRecognition.H Copyright transfered to the OpenFOAM Foundation 2011-08-14 12:17:30 +01:00
create3DCellShape.C Further standardization of loop index naming: pointI -> pointi, patchI -> patchi 2016-05-18 21:20:42 +01:00
extrudedQuadCellShape.C C++11: Replaced the C NULL with the safer C++11 nullptr 2016-08-05 17:19:38 +01:00
extrudedTriangleCellShape.C C++11: Replaced the C NULL with the safer C++11 nullptr 2016-08-05 17:19:38 +01:00
fluentMeshToFoam.L BUG: polyMesh removeFiles side-effect for blockMesh viewer (issue #346) 2016-12-15 19:07:05 +01:00
README.txt ENH: add operator[](const word&) as "find-by-name" to some classes 2010-04-29 10:12:35 +02:00

Notes for fluentMeshToFoam with zone preservation
#################################################

1. New option added:
    - writeSets:
    Writes all Fluent boundaries faceSets preserving Fluent names
    Writes all Fluent regions to cellSets preserving Fluent names
    lines: 1375 - 1393 & 1673 - 1741
    sets are useful for post-processing using foamToVTK with the "-faceSet
    <name>" and "-cellSet <name>" options.

    - writeZones:
    Writes all regions to cellZones preserving Fluent names
    Writes all region internal face to faceZones preserving Fluent names
    lines: 1545 - 1667
    Zones are usefull for porous media and MRF calculations

2. Zone Access
    - Zones are simple lists of label lists that can be accessed from polyMesh
    with the cellZones(), faceZones() and pointZones() member functions

    - Example (Members from polyMesh.H and ZoneMesh.H):
    const labelList& thisCellZone = mesh.cellZones()["thisZoneName"];

    - Zone integrity is preserved during mesh modification and decompomposition.

    - Once created via addZones, zones allow modification through non-const
    access

3. Fluent boundary types.
    - All internal and baffle elements are ignored during conversion

    - Boundary faces labelled as internal (i.e. interior, interface, internal,
    solid, fan, radiator, porous-jump) but that are in fact external boundaries
    will be added to a default wall boundary.