openfoam merge requestshttps://develop.openfoam.com/Development/openfoam/-/merge_requests2019-06-04T19:18:03Zhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/263ENH: improved handling of regIOobject deletion (#1276)2019-06-04T19:18:03ZMark OLESENENH: improved handling of regIOobject deletion (#1276)- remove registration and ownership before deleting a regIOobject
from within objectRegistry to avoid possible recursion.
- regIOobject destructor now removes any registered object from
registry regardless if ownedByRegistry...- remove registration and ownership before deleting a regIOobject
from within objectRegistry to avoid possible recursion.
- regIOobject destructor now removes any registered object from
registry regardless if ownedByRegistry or not. It also removes
always removes the ownership flag to avoid possible recursion.
- the regIOobject::checkOut() now unconditionally clears file watches.
These will only be there if the object is registered (a no-op for an
unregistered object), but this additional safety is needed to manage
case where the registration has been modified elsewhere (eg, by the
objectRegistry).
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/264Feature complex cleanup2019-06-04T10:35:36ZKutalmış BerçinFeature complex cleanupMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/259Feature dictionary checking2019-05-22T09:29:42ZMark OLESENFeature dictionary checkingAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/258Feature porting mingw2019-05-08T13:43:39ZMark OLESENFeature porting mingwAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/255Feature dynamic code2019-05-07T16:33:33ZMark OLESENFeature dynamic codeMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/242Reacting heterogeneous cloud2019-05-02T18:40:27ZSergio FerrarisReacting heterogeneous cloud### Summary
New reacting heterogeneous cloud, solver and tutorial.
This cloud is formed of pure solid particles which reacts with the carrier phase.
It is derived from reacting cloud.
### Resolved bugs (If applicable)
(Links to issues...### Summary
New reacting heterogeneous cloud, solver and tutorial.
This cloud is formed of pure solid particles which reacts with the carrier phase.
It is derived from reacting cloud.
### Resolved bugs (If applicable)
(Links to issues)
### Details of new models (If applicable)
The only available reacting heterogeneous model is Heteregeneous noncatalytic reaction MUCS approach.
Reference:
D. Papanastassiou and G. Bitsianes, Modelling of Heterogeneous Gas-
Solid Reactions, Metallurgical Transsactions, 480. Volume 4. 1973
### Risks
(Possible regressions?)
(Changes to user inputs?)v1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/243Feature reflective solar load2019-05-02T09:45:46ZSergio FerrarisFeature reflective solar load### Summary
Adding reflecting fluxes to Solar load radiation model.
Adding functionality to the boundary radiation models and new
place holder for basic wall types such as transparent, opaqueDiffusive,
opaqueReflective. Radiation wall ...### Summary
Adding reflecting fluxes to Solar load radiation model.
Adding functionality to the boundary radiation models and new
place holder for basic wall types such as transparent, opaqueDiffusive,
opaqueReflective. Radiation wall models are now runtime selectable.
Adding multi-band capabilities to VF model and improving the set up
for using solar loads in VF and fvDOM radiation models.
### Details of new models (If applicable)
The new entry is useReflectedRays = true in the radiationProperties.
This calculates the reflected rays on reflective walls. It can handle first reflection
on surfaces. Not multiple reflection are considered.
The wall boundary type "opaqueReflective" handles specular reflection which a proportion
of diffusive heat flux
### Risks
(Possible regressions?)
The boundaryRadiationProperties entries key words are "type", not "mode". But a backward
compatibility reading was introduced.v1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/253Feature indirect lists2019-04-29T09:48:17ZMark OLESENFeature indirect listsgeneralizes and combines various methods of indirect addressing for lists.generalizes and combines various methods of indirect addressing for lists.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/merge_requests/254ENH: add simple profiling of MPI communications2019-04-29T09:08:31ZMark OLESENENH: add simple profiling of MPI communicationsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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.comhttps://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/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/232Feature object registry search2019-02-07T08:59:08ZMark OLESENFeature object registry searchMark OLESENMark OLESENhttps://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/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/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/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/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/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/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 foamConfigurePathsv1812AdminAdmin