ENH: bounding box clipping for ensightWrite function object (issue #973)

- for larger problems with a smaller region of interest, can apply a
  bounding to limit the size of the ensight geometry and fields created.

  Since the implementation uses a fvMeshSubset, there is an additional
  per-process memory overhead.

  A high output frequency should be avoided with moving meshes, since
  this indirectly forces a frequent update of the submesh.
This commit is contained in:
Mark Olesen
2018-08-14 11:50:53 +02:00
parent 62b83a76a4
commit 45f4a8b9c5
7 changed files with 164 additions and 14 deletions

View File

@ -4,6 +4,7 @@ EXE_INC = \
-I$(LIB_SRC)/fileFormats/lnInclude \
-I$(LIB_SRC)/conversion/lnInclude \
-I$(LIB_SRC)/sampling/lnInclude \
-I$(LIB_SRC)/dynamicMesh/lnInclude \
-I$(LIB_SRC)/ODE/lnInclude \
-I$(LIB_SRC)/thermophysicalModels/basic/lnInclude \
-I$(LIB_SRC)/transportModels/compressible/lnInclude
@ -13,6 +14,7 @@ LIB_LIBS = \
-lfiniteArea \
-lconversion \
-lsampling \
-ldynamicMesh \
-lfluidThermophysicalModels \
-lcompressibleTransportModels \
-lODE