updates for run-time post-processing

• add parallel rendering
• additional volume filters (eg, isosurface, cutting plane) and other direct simulation data
• avoid write/read file for exchanging information (hold in memory)

Cross-ref: EP719

added enhancement feature labels

changed milestone to %v1906

mentioned in commit ae7b732e7abb20ae824ea3b6fb16c592e42217e0

mentioned in commit b15e57c11ee159336785561c19a32ed7156591ea

mentioned in commit 04d02b59b30d4e37a35df6f8899733f3203ee7fd

mentioned in commit f8b215a697006c38c3b7b249e24b34fe21519276

mentioned in commit 4ab51a5d72bba1c251fca978ac2cfab44df4b99f

@Prashant - the branch feature-postpro (!236 (merged)) is ready for testing.

mentioned in commit 4541a27aba765b2f1882a9a252287edc35bb99a1

mentioned in commit a33be1e5e9bc4cfdfdecd1058c196bf7659bc828

mentioned in commit 837d5956fc6c1d885c9f4484e4ea5ec09545f260

mentioned in commit d2339b0bd29c91989defcdb95484b4f8b2b08aad

The following example shows

• the vectors on the ground show the nearCellValue taken directly from the patch and displayed at the faces centres. No file IO for this object.
• the wireframe of the ground is likewise taken directly from the nearCellValue of the ground patch. No file IO for this object.
• the buildings are the nearCellValue of the patch and use the new smooth display option to render as interpolated node values. No file IO for this object.
• the three cutting planes represent two rendering objects:
  1. The middle plane is a sampled cutting plane of face values rendered as smooth. Geometry and sampled values are cached internally and used for rendering. No file IO for this object.
  2. The two planes straddling the middle plane are generated in VTK from the OpenFOAM mesh. The planes are generated with a single plane definition with multiple offsets. No file IO for this object.
• the streamlines are generated in OpenFOAM using the streamline function object. The traditional IO-based data exchange is used.
• The title text generated with dictionary expansion (ie, the ${FOAM_API} input value is expanded).
• the watermark text (www.openfoam.com) with transparency and multiple positions (new option)
• the scalar bar using a VTK-native layout and with optional text properties (shadow, italic).

• the ellipse geometry is from the patch (nearCellValue) with smoothing. (No file IO).
• the upstream vectors are the face values on two sampled cutting planes, rendered at the face centres. (No file IO).
• the downstream vectors are generated using a VTK cutting plane with multiple offsets. (No file IO).
• streamlines from OpenFOAM streamlines function object. Uses file IO.

• streamlines from OpenFOAM (uses file IO).
• vectors on sampled cutting plane (no file IO).
• motorbike and driver from the geometry patches with nearCellValue and smoothing (no file IO).
• updated, full-length scalar bar. Fixing a change in behaviour of the VTK libraries, but still using the OpenFOAM layout.

• live rendering of cloud data (no file IO).
• geometry patches of the walls (no file IO).
• an iso-surface of k using a VTK operation (no file IO).

Similar to previous description, but with a VTK iso-surface (no file IO).

• Some gaps are evident at the processor boundaries, which will need to be updated in the future.
• The overlay of partially transparent text doesn't particular pretty.

For interest @Development @froesler @PeterUnterlechner

mentioned in commit 9e312617fcce47387ef1213f8465582d3d9aab94

mentioned in commit f69cde62535d88b8a30e9c9ae4b731b390994d7d

mentioned in commit 18fd843124feac1b3cd47a184a3f93c07333050e

mentioned in commit b1056e4f03d9ceb8157473467203324492f95d0c

mentioned in merge request !236 (merged)

closed

mentioned in commit b2feb6a8

mentioned in commit 47f757a7

mentioned in commit 93e673ea

mentioned in commit a056f544

mentioned in commit aa5db904

mentioned in commit c3e14ffd