OpenFOAM-plus issueshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues2019-07-14T11:10:38Zhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/230Various threads at CFD-Online that don't have an answer yet for the Docker-ba...2019-07-14T11:10:38ZBruno SantosVarious threads at CFD-Online that don't have an answer yet for the Docker-based installations@Pawan I've finally managed to make a first pass at the list of threads in the [OpenFOAM installation sub-forum](http://www.cfd-online.com/Forums/openfoam-installation/) since late April 2016 and here are the threads that I've found so f...@Pawan I've finally managed to make a first pass at the list of threads in the [OpenFOAM installation sub-forum](http://www.cfd-online.com/Forums/openfoam-installation/) since late April 2016 and here are the threads that I've found so far that didn't get an answer in the past few months:
* http://www.cfd-online.com/Forums/openfoam-installation/171197-openfoam-plus-not-even-starting-ubuntu-14-04-lts.html
* http://www.cfd-online.com/Forums/openfoam-installation/174194-openfoam-plus-v1606-not-running-windows.html#post608637 - the last post sort-of needs an answer or some possible feedback, not sure
* http://www.cfd-online.com/Forums/openfoam-installation/175116-openfoam-plus-v1606-installation-mac-os-el-captain-using-docker.html#post612446
* http://www.cfd-online.com/Forums/openfoam-installation/168799-openfoam-plus-error-running-parafoam.html#post592188
By the way, due to how the forum indexes words, the correct'ish way to search for the threads that have `[OpenFOAM plus]` on their titles is with this:
```
[OpenFOAM plus*
```
This is at least applicable for the threads that I've managed to find and edit their titles accordingly.Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1361createPatch does not update fields in v19062019-07-11T09:37:31ZAaroncreatePatch does not update fields in v1906when using createPatch to merge patches, the mesh is updated but the accompanying mesh fields are not. This causes crashes with running other utilities, which complain that patches are missing or that number of faces on patches do not ma...when using createPatch to merge patches, the mesh is updated but the accompanying mesh fields are not. This causes crashes with running other utilities, which complain that patches are missing or that number of faces on patches do not match. The field data also cannot be plotted, as it's missing/incomplete on the patches in question.
This is easy and quick to reproduce on the motorbike tutorial. Just put the attached createPatchDict in /system, and run the attached Allrun. snappyHexMesh write the layers fields, which createPatch doesn't update, and then redistributePar fails due to a missing patch.
[Allrun](/uploads/caae2587d08e5ceb8f99c3deacfbe3e1/Allrun)[createPatchDict](/uploads/acb1c63a321d3da71d448d90dcc0a216/createPatchDict)
EDIT: mapFields does not handle this either. command:
**mapFields -noFunctionObjects -parallelSource -parallelTarget -consistent .**https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1363surface uniformity returns vector instead of scalar.2019-07-09T07:40:33ZMark OLESENsurface uniformity returns vector instead of scalar.cross-ref EP1047
@Stefan @Prashantcross-ref EP1047
@Stefan @PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1358foamFormatConvert compresses boundary file in v1906 (all other utilities leav...2019-07-08T04:38:04ZAaronfoamFormatConvert compresses boundary file in v1906 (all other utilities leave it uncompressed)In order to take advantage of the SPDP solver precision, I am using ascii format. When using writeCompression on, snappyHexMesh, renumberMesh, insideCells, etc. compress/gzip all the files in processor*/constant/polyMesh/ EXCEPT boundary...In order to take advantage of the SPDP solver precision, I am using ascii format. When using writeCompression on, snappyHexMesh, renumberMesh, insideCells, etc. compress/gzip all the files in processor*/constant/polyMesh/ EXCEPT boundary, which is always left uncompressed. This is convenient as boundary can be parsed for scripted setup of cases.
foamFormatConvert however, compresses the boundary file. Testing is easy, in controlDict just set:
writeFormat ascii;
writeCompression on;
and run:
foamFormatConvert -constant
Obviously the workaround is simple and it's a minor issue. But consistency is always nice :-)https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/263Multiple paths pointing to the same main folder can lead to compilation problems2019-07-03T19:39:47ZBruno SantosMultiple paths pointing to the same main folder can lead to compilation problemsEssentially the following is a brief summary of this bug report: http://bugs.openfoam.org/view.php?id=2204
1. Have two similar paths, but one of them is a symbolic link:
```
/home/ofuser/OpenFOAM/OpenFOAM-4.x (symbolic li...Essentially the following is a brief summary of this bug report: http://bugs.openfoam.org/view.php?id=2204
1. Have two similar paths, but one of them is a symbolic link:
```
/home/ofuser/OpenFOAM/OpenFOAM-4.x (symbolic link to OpenFOAM-dev)
/home/ofuser/OpenFOAM/OpenFOAM-dev
```
2. Source the environment for the `OpenFOAM-4.x` path.
3. Then run the build commands from within the `OpenFOAM-4.x` path.
4. **Result**: messy builds, where the first hit was in the folder `src/Pstream`, when building `mpi`.
The solution should be to use `pwd -P` in both `Allwmake` and `wmake` scripts, to enforce the correct paths to be used, after sorting through the symbolic link map.
The only problem with this solution that I can remember at the moment is mostly related to user confusion when inspecting the build output... nonetheless, I expect that there are some other weird corner cases, such as having the symbolic links switched around and the source paths enforced on the symbolic paths, resulting in a larger build stack confusion.
----
Tagging @mark, since he asked for it to be cross-referenced here as well ;)https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1353topoSet: No warning when using inconsistent setup2019-07-03T04:56:26ZPrashant SonakartopoSet: No warning when using inconsistent setup### Functionality to add/problem to solve
When setup is inconsistent, e.g. type cellSet, while source e.g. boxToFace, there is no warning/ error.
The cellSet is created with faces as labels. This should be checked for consistency.
@mark### Functionality to add/problem to solve
When setup is inconsistent, e.g. type cellSet, while source e.g. boxToFace, there is no warning/ error.
The cellSet is created with faces as labels. This should be checked for consistency.
@markhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1180objectRegistry can leak memory2019-06-28T09:55:38ZMark OLESENobjectRegistry can leak memoryAs discussed with @Mattijs - since all HashTable operations are visible through objectRegistry, anything that removes entries using the HashTable methods can leak memory if the object is owned by the registry.As discussed with @Mattijs - since all HashTable operations are visible through objectRegistry, anything that removes entries using the HashTable methods can leak memory if the object is owned by the registry.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/959noise detection of time step2019-06-28T09:50:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comnoise detection of time stepnoise utility tries to detect uniform time step by comparing to previous time directories:
```At time 0.277259999999 previous time:0.277255 difference:4.999998999999367e-06 deltaT:5.000000000005e-06 relative difference:2.000011267710988...noise utility tries to detect uniform time step by comparing to previous time directories:
```At time 0.277259999999 previous time:0.277255 difference:4.999998999999367e-06 deltaT:5.000000000005e-06 relative difference:2.000011267710988e-07```
This goes wrong when there are not enough timePrecision or the start time is late so we loose precision.Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1343Bug2019-06-27T11:39:40ZRozie ZangenehBugI am trying to compile a new application on Ubuntu(new turbulence model), I get the following error:
In file included from /home/rozie/OpenFOAM/ThirdParty-v1812/platforms/linux64/gcc-6.3.0/include/c++/6.3.0/x86_64-pc-linux-gnu/bits/c++c...I am trying to compile a new application on Ubuntu(new turbulence model), I get the following error:
In file included from /home/rozie/OpenFOAM/ThirdParty-v1812/platforms/linux64/gcc-6.3.0/include/c++/6.3.0/x86_64-pc-linux-gnu/bits/c++config.h:507:0,
from /home/rozie/OpenFOAM/ThirdParty-v1812/platforms/linux64/gcc-6.3.0/include/c++/6.3.0/utility:68,
from /home/rozie/OpenFOAM/OpenFOAM-v1812/src/OpenFOAM/lnInclude/autoPtr.H:51,
from ../turbulenceModels/lnInclude/turbulenceModel.H:39,
from incompressibleTurbulenceModel.H:38,
from incompressibleTurbulenceModel.C:26:
/home/rozie/OpenFOAM/ThirdParty-v1812/platforms/linux64/gcc-6.3.0/include/c++/6.3.0/x86_64-pc-linux-gnu/bits/os_defines.h:39:22: fatal error: features.h: No such file or directory
#include <features.h>
^
compilation terminated.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1347rhoMax/rhoMin defined but not used in buoyantSimpleFoam2019-06-26T18:22:05ZBruno SantosrhoMax/rhoMin defined but not used in buoyantSimpleFoamIn the solver `applications/solvers/heatTransfer/buoyantSimpleFoam`, the `rhoMax` and `rhoMin` variables are defined in `createFields.H`, but never used in this solver.
I noticed this today with v1806, but have checked and this also occu...In the solver `applications/solvers/heatTransfer/buoyantSimpleFoam`, the `rhoMax` and `rhoMin` variables are defined in `createFields.H`, but never used in this solver.
I noticed this today with v1806, but have checked and this also occurs in v1812 and v1906-rc1.
According to `git blame`, the commit 1a701d9eac55a49f22b983683826d3ead8a8c85b is when this was added, but the min-max restriction was not imposed into this solver, the same way it was in chtMultiRegionSimpleFoam: https://develop.openfoam.com/Development/OpenFOAM-plus/blob/1a701d9eac55a49f22b983683826d3ead8a8c85b/applications/solvers/heatTransfer/chtMultiRegionFoam/chtMultiRegionSimpleFoam/fluid/pEqn.H#L91https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/576ENH: improving postChannel2019-06-26T12:05:26ZTimofey MukhaENH: improving postChannelHello!
postChannel is an old small utility that allows to collapse data from a turbulent channel flow LES or DNS into a single profile by averaging along x and z, which are statistically homogeneous directions. There is, however, a sign...Hello!
postChannel is an old small utility that allows to collapse data from a turbulent channel flow LES or DNS into a single profile by averaging along x and z, which are statistically homogeneous directions. There is, however, a significant downside: it is impossible to choose what fields are to be averaged. Instead, they are hardcoded, see
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/utilities/postProcessing/miscellaneous/postChannel/collapse.H
A couple of years ago I have developed my version of the utility which allows one to provide a list of fields to be averaged. Also, it allows you to specify the names of the patches corresponding to the top and bottom walls, and the outputted 1d profiles will include the data averaged on the patches. This is relevant in some situations, for instance in Wall-Modelled LES, where nu_t at the wall is an important quantity. Here is the repo with my code.
https://bitbucket.org/lesituu/postchannelflow
I would like to know if there is interest in incorporating my enhancemnts into the main code. From my side this seems like a nice small enhancemnt, which can be used to test getting through the process of contributing some code.
Kind regards,
Timofeyhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1101Stability issue in dynamicLagrangian model2019-06-24T10:26:39ZNing RenStability issue in dynamicLagrangian modelHi,
There is a stability issue in the dynamicLagrangian model, which is caused by flm_/fmm_. Some cells may have 0 value in fmm_. If replacing flm_/fmm_ with flm_/(fmm_+fmm0_), the model will be stable, where fmm0_ is a VSMALL defined i...Hi,
There is a stability issue in the dynamicLagrangian model, which is caused by flm_/fmm_. Some cells may have 0 value in fmm_. If replacing flm_/fmm_ with flm_/(fmm_+fmm0_), the model will be stable, where fmm0_ is a VSMALL defined in the model.
Attached is a patch file for this model.[V1806-Fix-stability-issue-in-dynamicLagrangian-model.patch](/uploads/706afdd4f55d19ebd6ab62394d7c6e61/V1806-Fix-stability-issue-in-dynamicLagrangian-model.patch)
Thanks,
Ning RenKutalmış BerçinKutalmış Berçin2019-01-13https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1340low limit of cut-off frequency ignored in surfaceNoise2019-06-18T07:27:17ZSon Volow limit of cut-off frequency ignored in surfaceNoisesurfaceNoise ignores the fl when writting the 1/3-data of SPL and PSD. That means the data of 1/3 SPL and PSDlower than fl are still written to files. The problem can be reproduced using the vortexShed tutorials.
Link to EP:
https://...surfaceNoise ignores the fl when writting the 1/3-data of SPL and PSD. That means the data of 1/3 SPL and PSDlower than fl are still written to files. The problem can be reproduced using the vortexShed tutorials.
Link to EP:
https://exchange.openfoam.com/node/1038
Son.v1912Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/517reduce the size of the environment2019-06-14T13:37:52ZMark OLESENreduce the size of the environmentMark OLESENMark OLESENhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/954cuttingPlane requires huge amount of RAM in single precision2019-06-12T10:10:08ZMarcocuttingPlane requires huge amount of RAM in single precisionDear All,
my transient simulation crashes when it tries to export cuttingPlanes VTK on the fly for lack of RAM memory, when running the solver (pisoFoam) in single precision. Everything runs fine if i run the double precision version.
I...Dear All,
my transient simulation crashes when it tries to export cuttingPlanes VTK on the fly for lack of RAM memory, when running the solver (pisoFoam) in single precision. Everything runs fine if i run the double precision version.
I couldn't explain this behaviour.
Thanks for your help
Marcohttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/947tracking does not handle cells with inverted pyramids (it does handle inverte...2019-06-11T09:59:40ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtracking does not handle cells with inverted pyramids (it does handle inverted cells with tets)This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.https://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1086single precision issues2019-06-05T13:34:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsingle precision issuesGeneric issue for single precision issuesGeneric issue for single precision issueshttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1312Suggestion to replace tensor J with symmTensor J in momentOfInertia class2019-05-29T09:48:51ZJohan RoenbySuggestion to replace tensor J with symmTensor J in momentOfInertia classThe moment of inertia tensor is always a symmetric 3x3 matrix.
I therefore suggest replacing all occurrences of "tensor J" with "symmTensor J" in:
https://develop.openfoam.com/Development/OpenFOAM-plus/tree/develop/src/meshTools/momentO...The moment of inertia tensor is always a symmetric 3x3 matrix.
I therefore suggest replacing all occurrences of "tensor J" with "symmTensor J" in:
https://develop.openfoam.com/Development/OpenFOAM-plus/tree/develop/src/meshTools/momentOfInertia
I have not encountered problems with the current implementation, but the change will make the code more mathematically consistent.Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1321overset incorrect addressing in parallel2019-05-20T12:44:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comoverset incorrect addressing in parallel<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
-->
<!--
All text between these marker...<!--
*** Please read this first! ***
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label and check to see if it has already been reported
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
Overset crashes if there are cells which have all donor cells remote. Part local/remote donors seems to be ok.
### What is the current *bug* behaviour?
<!-- What actually happens -->
Out-of-range index on PtrList/UListMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/OpenFOAM-plus/-/issues/1155possible issues with conversion from gmsh2019-05-20T12:44:37ZMark OLESENpossible issues with conversion from gmshMentioned in the cfd-online forum https://www.cfd-online.com/Forums/openfoam-meshing/213553-meshing-error-bad-token-could-not-get-word.html by user Dewi Madden.
- could be an OpenFOAM parsing issue,
- or a syntax change in gmsh format
-...Mentioned in the cfd-online forum https://www.cfd-online.com/Forums/openfoam-meshing/213553-meshing-error-bad-token-could-not-get-word.html by user Dewi Madden.
- could be an OpenFOAM parsing issue,
- or a syntax change in gmsh format
- bad input,
- other
Diagnosis awaiting a file or two...Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com