- May 17, 2019
-
-
Mark OLESEN authored
-
- May 21, 2019
-
-
Mark OLESEN authored
BUG: The ok_ flag was not being updated in the regExpCxx::set() method
-
mattijs authored
-
mattijs authored
-
mattijs authored
-
- May 20, 2019
-
-
Mark OLESEN authored
-
Mark OLESEN authored
-
- May 17, 2019
-
-
Mark OLESEN authored
-
Mark OLESEN authored
-
- May 16, 2019
-
-
Mark OLESEN authored
-
mattijs authored
This is to avoid overset interpolation in the calculation of the stencil itself since this triggers a loop.
-
- May 15, 2019
-
-
Mark OLESEN authored
- records execution and wallclock times to postProcessing/ which can be more convenient than parsing a log file.
-
mattijs authored
-
mattijs authored
-
mattijs authored
-
- May 08, 2019
-
-
mattijs authored
This will use a random-number generator to select for each cell the processor. Useful for testing parallel/non-parallel consistent behaviour.
-
- May 10, 2019
-
-
Mark OLESEN authored
- simplify faceZone selection in surfaceMeshExtract
-
Mark OLESEN authored
- uniformFixedValue was relocated from lib OpenFOAM
-
Mark OLESEN authored
- adjust naming of quaternion 'rotationSequence' to be 'eulerOrder' to reflect its purpose. - provide rotation matrices directly for these rotation orders in coordinateRotations::euler for case in which the rotation tensor is required but not a quaternion.
-
- May 08, 2019
-
-
Mark OLESEN authored
Modified revert of commit 6c6f777b. - The "alphaContactAngleFvPatchScalarField" occurs in several places in the code base: - as abstract class for two-phase properties - in various multiphase solvers To resolve potential linking conflicts, renamed the abstract class as "alphaContactAngleTwoPhaseFvPatchScalarField" instead. This permits potential linking of two-phase and multi-phase libraries without symbol conflicts and has no effect on concrete uses of two-phase alphaContactAngle boudary conditions.
-
Mark OLESEN authored
-
Andrew Heather authored
Feature porting mingw See merge request OpenFOAM-plus!258
-
Mark OLESEN authored
-
- May 06, 2019
-
-
Mark OLESEN authored
- support move insert/set and emplace insertion. These adjustments can be used for improved memory efficiency, and allow hash tables of non-copyable objects (eg, std::unique_ptr). - extend special HashTable output treatment to include pointer-like objects such as autoPtr and unique_ptr. ENH: HashTable::at() method with checking. Fatal if entry does not exist.
-
- May 07, 2019
-
-
Mark OLESEN authored
-
Mark OLESEN authored
Feature dynamic code See merge request OpenFOAM-plus!255
-
- May 06, 2019
-
-
Mark OLESEN authored
- can be used for outputing sampled surfaces in x3d format for direct import in other rendering tools.
-
- May 03, 2019
-
-
Mark OLESEN authored
-
Mark OLESEN authored
-
Mark OLESEN authored
-
- May 02, 2019
-
-
Mark OLESEN authored
Reacting heterogeneous cloud See merge request OpenFOAM-plus!242
-
mattijs authored
All remote contributions to interpolation stencils now get added as 'processor' type lduInterfaces. This guarantees a consistent matrix, e.g. initial residual is normalised to 1. Second change is the normalisation of the interpolation discretisation which uses the diagonal from the unmodified equation. This helps GAMG.
-
mattijs authored
-
Mark OLESEN authored
- this corresponds more closely to the expected behaviour of a patch-average value being independent of the local face discretization
-
Andrew Heather authored
Feature reflective solar load See merge request OpenFOAM-plus!243
-
Andrew Heather authored
-
- May 01, 2019
-
-
Mark OLESEN authored
- for codedFunctionObject and CodedSource the main code snippets were not included in the SHA1 calculation, which meant that many changes would not be noticed and no new library would be compiled. As a workaround, a dummy 'code' entry could be used solely for the purposes of generating a SHA1, but this is easily forgotten. We now allow tracking of the dynamicCodeContext for the coded objects and append to the SHA1 hasher with specific entries. This should solve the previous misbehaviour. We additionally add information about the ordering of the code sections. Suppose we have a coded function object (all code segments are optional) with the following: codeExecute ""; codeWrite #{ Info<< "Called\n"; #}; which we subsequently change to this: codeExecute #{ Info<< "Called\n"; #}; codeWrite ""; If the code strings are simply concatenated together, the SHA1 hashes will be identical. We thus 'salt' with their semantic locations, choosing tags that are unlikely to occur within the code strings themselves. - simplify the coded templates with constexpr for the SHA1sum information. - Correct the CodedSource to use 'codeConstrain' instead of 'codeSetValue' for consistency with the underlying functions.
-
Mark OLESEN authored
- localize some functionality, std::array for digest internals. Additional append sub-string methods, pass-through write of digest etc.
-
Mark OLESEN authored
- only apply component-wise transformCoupleField for non-scalar types
-
Mark OLESEN authored
-