openfoam merge requestshttps://develop.openfoam.com/Development/openfoam/-/merge_requests2018-11-01T11:12:13Zhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/216Feature topo set improvements (issue #1060)2018-11-01T11:12:13ZMark OLESENFeature topo set improvements (issue #1060)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/217Work-package-09 geometric constraint2018-11-08T20:50:48ZMark OLESENWork-package-09 geometric constraintThe geometric decomposition constraint (issue #921) may be used to restrict the mesh decomposition on a geometrical basis.
For example, to avoid splitting of a sensitive feature across processor boundaries.
The geometry constraints are...The geometric decomposition constraint (issue #921) may be used to restrict the mesh decomposition on a geometrical basis.
For example, to avoid splitting of a sensitive feature across processor boundaries.
The geometry constraints are described by topoSet face sources, which can include basic geometrically entities (sphere, box, cylinder), mesh entities (eg, faces associated with a cellSet) or an arbitrary closed surface (stl, obj, etc). The support for arbitrary closed surfaces uses a triSurfaceMesh topoSetFaceSource.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/219uniformFixedValue: avoid re-evaluation on reading or mapping2018-11-12T10:49:29ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniformFixedValue: avoid re-evaluation on reading or mappingv1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/218Feature ioobjectlist registry2018-11-12T11:39:01ZMark OLESENFeature ioobjectlist registryAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/220Mapping injected faces through interpolation2018-11-15T14:58:57ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMapping injected faces through interpolationImproved mapping of newly generated internal faces.
- these now get created (hexRef8) without supplying a master face/edge or point
- these get a mapped value by interpolating old surrounding faces
Code supplied by Daniel Rettenmaier <r...Improved mapping of newly generated internal faces.
- these now get created (hexRef8) without supplying a master face/edge or point
- these get a mapped value by interpolating old surrounding faces
Code supplied by Daniel Rettenmaier <rettenmaier@gsc.tu-darmstadt.de>
Date: Mon Mar 6 17:17:06 2017 +0100
Fix mapping for non-flux surfaceVectorFields and fix mapping of newly created internal faces
A more generalized approach should be consideredMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/212Issue 9112018-11-20T14:40:44ZJohan RoenbyIssue 911A typo in interIsoFoam/alphaEqn.H makes interIsoFoam crash when nOuterCorrectors > 1.
Could this bugfix be applied also to v1806 or are you keeping v1806 frozen?A typo in interIsoFoam/alphaEqn.H makes interIsoFoam crash when nOuterCorrectors > 1.
Could this bugfix be applied also to v1806 or are you keeping v1806 frozen?AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/213Feature vtm/vtk2018-11-26T10:30:41ZMark OLESENFeature vtm/vtkIncludes numerous modifications to the VTK-related infrastructure. Notably it adds parallel output for foamToVTK and for the vtkWrite function object. Multi-region, multi-block VTM output with associated time-series files. TimeValue time...Includes numerous modifications to the VTK-related infrastructure. Notably it adds parallel output for foamToVTK and for the vtkWrite function object. Multi-region, multi-block VTM output with associated time-series files. TimeValue time-stamps within all the generated files. Improvements to the vtkCloud and vtkWrite function objects to allow selection of regions of interest.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/223ENH: momentum field function (issue #1105)2018-12-04T14:26:43ZMark OLESENENH: momentum field function (issue #1105)Calculates linear/angular momentum, reporting integral values
and optionally writing the fields.
Example
```
momentum1
{
type momentum;
libs ("libfieldFunctionObjects.so");
...
...Calculates linear/angular momentum, reporting integral values
and optionally writing the fields.
Example
```
momentum1
{
type momentum;
libs ("libfieldFunctionObjects.so");
...
selectionMode all;
writeMomentum yes;
writeVelocity no;
cylindrical true;
origin (0 0 0);
e1 (1 0 0);
e3 (0 0 1);
}
```AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/222ENH: update handling of versioning and make control (issue #1010)2018-12-08T21:57:46ZMark OLESENENH: update handling of versioning and make control (issue #1010)- Use the OPENFOAM define (eg, 1806, 1812), which normally corresponds
to a major release, to define an API level. This remains consistent
within a release cycle and means that it is possible to manage
several sub-versions and c...- Use the OPENFOAM define (eg, 1806, 1812), which normally corresponds
to a major release, to define an API level. This remains consistent
within a release cycle and means that it is possible to manage
several sub-versions and continue to have a consistent lookup.
The current API value is updated automatically during the build
and cached as meta data for later use, even when the wmake/ directory
is missing or OpenFOAM has not yet be initialized.
The version information reported on program start or with -help
usage adjusted to reflect this. The build tag from git now also
carries the date as being more meaningful to trace than a hash
value.
- Update etc/bashrc and etc/cshrc to obtain the project directory
directly instead of via its prefix directory. The value obtained
corresponds to an absolute path, from which the prefix directory
can be obtained.
The combination of these changes removes the reliance on any
particular directory naming convention.
For example,
With an 1812 version (API level):
WM_PROJECT_VERSION=myVersion
installed as /some/path/somewhere/openfoam-mySandbox
This makes the -prefix, -foamInstall, -projectVersion, -version
values of foamEtcFiles, and similar entries for foamConfigurePaths
superfluous.
WM_PROJECT_INST_DIR is no longer required or used
CONFIG: relocate WM_PROJECT_SITE default
- was <prefix>/site, now <project>/site
This avoids several issues when installing OpenFOAM in clusters
without an intermediate OpenFOAM-specific installation prefix.
The 'site' directory may have a reserved meaning in these situations
and it is undesirable to 'leak' upwards into the parent directory to
look for configuration files.
Placing the default within the project directory avoids this.
Alternative locations can be given via the WM_PROJECT_SITE variable.
- removed foamExec, which was previously used when switching versions
and before the bash/csh discovery logic was used
ENH: add csh support to foamConfigurePathsv1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/224ENH: isoSurfaceTopo: replacement for isoSurfaceCell.2018-12-06T15:56:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comENH: isoSurfaceTopo: replacement for isoSurfaceCell.isoSurface: Improved iso-surface algorithm
Includes topological point generation and optional removal of all points (and
triangles) that do not originate from mesh edges. This generates
polygons rather than triangles providing smoother...isoSurface: Improved iso-surface algorithm
Includes topological point generation and optional removal of all points (and
triangles) that do not originate from mesh edges. This generates
polygons rather than triangles providing smoother surfaces and significantly
small files (~ factor of 3-4 smaller).AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/225ENH: Added new AMIWeights function object2018-12-10T09:55:04ZAdminENH: Added new AMIWeights function objectReports the min|max|average AMI weights to text file and optionally
writes VTK surfaces of the sum of the weights, and mask field for
ACMI patches.
Example usage:
AMIWeights
{
type AMIWeights;
libs ...Reports the min|max|average AMI weights to text file and optionally
writes VTK surfaces of the sum of the weights, and mask field for
ACMI patches.
Example usage:
AMIWeights
{
type AMIWeights;
libs ("libfieldFunctionObjects.so");
writeControl writeTime;
writeFields yes;
}v1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/226Feature merge OpenFOAM.org2019-01-10T10:10:07ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comFeature merge OpenFOAM.orgAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/228Feature run time control triggers2019-01-24T05:50:29ZAdminFeature run time control triggersExtends the `runTimeControl` function object to set 'trigger' values, that can be used to start other function objects. For example, to run for 100 steps after the average drag coefficient converges (reported by a `forceCoeffs` function...Extends the `runTimeControl` function object to set 'trigger' values, that can be used to start other function objects. For example, to run for 100 steps after the average drag coefficient converges (reported by a `forceCoeffs` function object) the following could be used:
```
runTimeControl1
{
type runTimeControl;
libs ("libutilityFunctionObjects.so");
conditions
{
condition1
{
type average;
functionObject forceCoeffs1;
fields (Cd);
tolerance 1e-3;
window 20;
windowType exact;
}
}
satisfiedAction setTrigger;
trigger 1;
}
runTimeControl2
{
type runTimeControl;
libs ("libutilityFunctionObjects.so");
controlMode trigger;
triggerStart 1;
conditions
{
condition1
{
type maxDuration;
duration 100;
}
}
satisfiedAction end;
}
```
See the `$FOAM_TUTORIALS/incompressible/simpleFoam/simpleCar tutorial`v1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/229Feature snappy hex mesh check2019-01-28T08:57:47ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comFeature snappy hex mesh checkThis adds -dry-run to snappyHexMesh to perform various checks on initial mesh and dictionaries.This adds -dry-run to snappyHexMesh to perform various checks on initial mesh and dictionaries.https://develop.openfoam.com/Development/openfoam/-/merge_requests/231Function object updates2019-01-31T17:00:02ZAdminFunction object updatesRenamed the `residuals` function object to `solverInfo` since it now generates:
* residual fields
* solver type
* initial residual
* final residual
* number of solver iterations
* convergecnce flag
Added new `continuityError` function ...Renamed the `residuals` function object to `solverInfo` since it now generates:
* residual fields
* solver type
* initial residual
* final residual
* number of solver iterations
* convergecnce flag
Added new `continuityError` function object. Example usage:
continuityError1
{
type continuityError;
libs ("libfieldFunctionObjects.so");
...
writeToFile yes;
log yes;
phi phi;
}
\endverbatimv1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/230Add minMax and clip field functions2019-02-01T16:54:37ZMark OLESENAdd minMax and clip field functionsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/232Feature object registry search2019-02-07T08:59:08ZMark OLESENFeature object registry searchMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/236Feature postpro2019-02-20T19:43:43ZMark OLESENFeature postpro### Summary
Extension of insitu visualization (runTimePostProcessing):
- parallel rendering
- direct use of VTK cutting plane and iso-surface filters
- *live* access to simulation data such as lagrangian clouds and geometry patches...### Summary
Extension of insitu visualization (runTimePostProcessing):
- parallel rendering
- direct use of VTK cutting plane and iso-surface filters
- *live* access to simulation data such as lagrangian clouds and geometry patches
- the ability to use stored surfaces and fields originating from another function object (eg, sampledSurfaces)
Significant cleanup and reimplementation of the surface sampling function object and all the surface writers to allow per-surface format specification. Added support for `.vtp` output of sampled surface with multiple fields in a single file.
Stored surface information can now be used for other field calculations (eg, `surfaceFieldValue`)
Images and description of the new functionality are attached to issue #1206v1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/249Snappy hex mesh proximity check2019-03-25T16:49:51ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comSnappy hex mesh proximity checkAdds snappyHexMesh functionality to remove cells in small gaps (instead of refining them).
See mesh/snappyHexMesh/opposite_walls tutorial.Adds snappyHexMesh functionality to remove cells in small gaps (instead of refining them).
See mesh/snappyHexMesh/opposite_walls tutorial.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/252better cooperation with external MPI initialize / finalize2019-04-10T13:42:12ZMark OLESENbetter cooperation with external MPI initialize / finalizeMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com