Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-02-22T02:57:23Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1149interCondensatingEvaporatingFoam mishandles heat conduction2019-02-22T02:57:23ZAdmininterCondensatingEvaporatingFoam mishandles heat conductionHey all,
I've tested interCondensatingEvaporatingFoam and found a pretty significant issue. If one takes a stagnant container with an initial condition of separated vapor and liquid phases, it appears that a strong temperature sink appe...Hey all,
I've tested interCondensatingEvaporatingFoam and found a pretty significant issue. If one takes a stagnant container with an initial condition of separated vapor and liquid phases, it appears that a strong temperature sink appears at the liquid/vapor interface. I noticed that this is because heat conduction is treated as laplacian(k/cp,e), which is wrong since e is discontinuous across the boundary due to the latent heat difference, and taking its gradient gives weird results.
I believe I can fix this issue, do I just submit a PR once it works?https://develop.openfoam.com/Development/openfoam/-/issues/1150BUG: mismatch of coefficient names for BinghamPlastic2021-07-08T20:34:23ZMark OLESENBUG: mismatch of coefficient names for BinghamPlasticConstructor reads "BinghamExponent" etc. The read() method expects "yieldStressExponent"Constructor reads "BinghamExponent" etc. The read() method expects "yieldStressExponent"v2112Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1151Case diverges systematically after refining grid2019-01-07T00:31:03ZAdminCase diverges systematically after refining gridI'm experiencing another problem with the same case from which issue #1143 originated (@kuti).
After refining uniformly the grid generated by snappyHexMesh (by increasing the initial blockMesh resolution) and then extruding the mesh via...I'm experiencing another problem with the same case from which issue #1143 originated (@kuti).
After refining uniformly the grid generated by snappyHexMesh (by increasing the initial blockMesh resolution) and then extruding the mesh via extrudeMesh, the simulation runs fine in rhoPimpleFoam but diverges systematically in rhoSimpleFoam either in serial or parallel execution, whereas but solvers work fine with the coarser grid resolution.
Not sure if the issue belongs here as it might be a problem with the model setup, but given the former issue with the same case may be worth checking it?https://develop.openfoam.com/Development/openfoam/-/issues/1152wmakeBuildInfo bash3 compatibility2019-12-09T22:37:27ZAdminwmakeBuildInfo bash3 compatibilityThere is a problem with using declare -A in wmakeBuildInfo if your bash version is less than 4 as associative arrays aren't available until version 4.
The libraries will build, except the global.Cver, which will be wrong and cause proble...There is a problem with using declare -A in wmakeBuildInfo if your bash version is less than 4 as associative arrays aren't available until version 4.
The libraries will build, except the global.Cver, which will be wrong and cause problems when building the applications.
It would be nice if there was a check for this and fixed to work even for bash version 3.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1153intel mpi paths2019-12-09T22:37:28ZMark OLESENintel mpi pathsas noted by @Prashant - more recent versions of intel mpi may not have bin64/, lib64/ directories.
```
bin64 -> intel64/bin
etc64 -> intel64/etc
include64 -> intel64/include
lib64 -> intel64/lib
```
So it would be better to check for t...as noted by @Prashant - more recent versions of intel mpi may not have bin64/, lib64/ directories.
```
bin64 -> intel64/bin
etc64 -> intel64/etc
include64 -> intel64/include
lib64 -> intel64/lib
```
So it would be better to check for the `intel64/` directory first.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1155possible issues with conversion from gmsh2021-07-06T15:15:28ZMark 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.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1156No data array Fill() method in older VTK versions2019-12-09T22:37:27ZMark OLESENNo data array Fill() method in older VTK versions@Prashant@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1157refineMesh -overwrite writes to 0, not constant2019-01-07T12:21:05ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrefineMesh -overwrite writes to 0, not constantMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1158FOAM_API to replace WM_PROJECT_API2019-12-09T22:37:27ZMark OLESENFOAM_API to replace WM_PROJECT_APIand export from argList.C based on the current value of `foamVersion::api()` for proper consistency.
@Mattijsand export from argList.C based on the current value of `foamVersion::api()` for proper consistency.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1159META: How does the Developer upgrade guide get filled?2019-06-28T09:46:15ZAdminMETA: How does the Developer upgrade guide get filled?Hello!
So, the developer upgrade guide is currently lagging behind, with the guide for 1806 "coming soon". My guess is that the guide is being composed after the release, which needs going through the introduced changes after the fact. ...Hello!
So, the developer upgrade guide is currently lagging behind, with the guide for 1806 "coming soon". My guess is that the guide is being composed after the release, which needs going through the introduced changes after the fact. A more efficient system, also leading to a better and more complete guide, would be to make it a live document where breaking API changes are registered upon commit. For each braking change one could add something like
ClassName Short description of the breaking change <Link to commit>
This would *really* make things easy for people writing stand-alone libraries since they can immediately see if their code is affected and how to address it. Hopefully, the overhead for the devs is not that large since breaking changes should not happen too often. Releasing the guide would amount to freezing the document upon the release of a new version of the software, sorting the list after the class name and adding a more detailed discussion of the most important changes.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1160general cleanup items for containers2019-06-28T09:39:46ZMark OLESENgeneral cleanup items for containers- move some HashTable details into the Detail namespace
- avoid delete/new when calling HashSet::set()
- better handling of pointers in hashes (IO).
- FixedList output formatting influences pair/edge and thus we get things like `2{100}`...- move some HashTable details into the Detail namespace
- avoid delete/new when calling HashSet::set()
- better handling of pointers in hashes (IO).
- FixedList output formatting influences pair/edge and thus we get things like `2{100}` for a labelPair output. For these short lists it probably doesn't have much space saving. It would be nice to have the same output format for a Pair or a Tuple2 of the same content.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1161BUG: Memory leak when using runtime fieldExpression::grad(U) with cached grad(U)2022-04-26T16:11:08ZAdminBUG: Memory leak when using runtime fieldExpression::grad(U) with cached grad(U)This issue can be reproduced by running any tutorial where grad(U) is both cached in system/fvSolution (for example interFoam/RAS/DTChull) and computed using the fieldExpression:
test
{
functionObjectLibs ("libfieldFunctionObjec...This issue can be reproduced by running any tutorial where grad(U) is both cached in system/fvSolution (for example interFoam/RAS/DTChull) and computed using the fieldExpression:
test
{
functionObjectLibs ("libfieldFunctionObjects.so");
type grad;
field U;
outputControl writeTime;
}
The issue is likely related to line 42 and 51 in src/functionObjects/field/grad/gradTemplates.C
\## Reattaching the author to the issue ticket: @peltonp1 ##v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1162Error in "k" equation in Smagorinsky Turbulence LES Model2019-01-08T17:12:38ZAdminError in "k" equation in Smagorinsky Turbulence LES ModelAs i understand, the "k" value in Smagorinsky Turbulence LES Model is calculated by solving the quadratic equation ( a*sqr(k) + b*k + c = 0 ), so the solution of it is (-b+sqrt(sqr(b)-4*a*c))/(2*a), but what is published is (+) instead o...As i understand, the "k" value in Smagorinsky Turbulence LES Model is calculated by solving the quadratic equation ( a*sqr(k) + b*k + c = 0 ), so the solution of it is (-b+sqrt(sqr(b)-4*a*c))/(2*a), but what is published is (+) instead of (-) in the descriminent term.![received_308218969827643](/uploads/0e0c7a2adde220d27f029464afc10ef8/received_308218969827643.jpeg)https://develop.openfoam.com/Development/openfoam/-/issues/1163Compilation failed2019-07-03T19:35:56ZAdminCompilation failedCompilation failed while compiling celCellStencil : compiler can't find cellCellStencilTemplates.C file
```
g++ -std=c++11 -m64 -DOPENFOAM=1812 -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall -Wextra -Wold-style-cast -Wnon...Compilation failed while compiling celCellStencil : compiler can't find cellCellStencilTemplates.C file
```
g++ -std=c++11 -m64 -DOPENFOAM=1812 -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall -Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter -Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -O3 -DNoRepository -ftemplate-depth-100 -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/fileFormats/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/surfMesh/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/sampling/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/meshTools/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/dynamicMesh/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/finiteVolume/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/dynamicFvMesh/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/parallel/decompose/decompositionMethods/lnInclude -IlnInclude -I. -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/OpenFOAM/lnInclude -I/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/src/OSspecific/POSIX/lnInclude -fPIC -c oversetPolyPatch/oversetPolyPatch.C -o /home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/oversetPolyPatch/oversetPolyPatch.o
In file included from cellCellStencil/cellVolumeWeight/cellVolumeWeightCellCellStencil.H:39:0,
from cellCellStencil/cellVolumeWeight/cellVolumeWeightCellCellStencil.C:26:
lnInclude/cellCellStencil.H:229:13: fatal error: cellCellStencilTemplates.C: No such file or directory
# include "cellCellStencilTemplates.C"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from lnInclude/inverseDistanceCellCellStencil.H:45:0,
from cellCellStencil/leastSquares/leastSquaresCellCellStencil.H:43,
from cellCellStencil/leastSquares/leastSquaresCellCellStencil.C:26:
lnInclude/cellCellStencil.H:229:13: fatal error: cellCellStencilTemplates.C: No such file or directory
# include "cellCellStencilTemplates.C"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from cellCellStencil/inverseDistance/inverseDistanceCellCellStencil.H:45:0,
from cellCellStencil/inverseDistance/inverseDistanceCellCellStencil.C:26:
lnInclude/cellCellStencil.H:229:13: fatal error: cellCellStencilTemplates.C: No such file or directory
# include "cellCellStencilTemplates.C"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/wmake/rules/General/transform:34: recipe for target '/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/cellVolumeWeight/cellVolumeWeightCellCellStencil.o' failed
make: *** [/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/cellVolumeWeight/cellVolumeWeightCellCellStencil.o] Error 1
make: *** Waiting for unfinished jobs....
/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/wmake/rules/General/transform:34: recipe for target '/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/inverseDistance/inverseDistanceCellCellStencil.o' failed
make: *** [/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/inverseDistance/inverseDistanceCellCellStencil.o] Error 1
/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/wmake/rules/General/transform:34: recipe for target '/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/leastSquares/leastSquaresCellCellStencil.o' failed
make: *** [/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/leastSquares/leastSquaresCellCellStencil.o] Error 1
In file included from lnInclude/inverseDistanceCellCellStencil.H:45:0,
from cellCellStencil/trackingInverseDistance/trackingInverseDistanceCellCellStencil.H:38,
from cellCellStencil/trackingInverseDistance/trackingInverseDistanceCellCellStencil.C:26:
lnInclude/cellCellStencil.H:229:13: fatal error: cellCellStencilTemplates.C: No such file or directory
# include "cellCellStencilTemplates.C"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/wmake/rules/General/transform:34: recipe for target '/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/trackingInverseDistance/trackingInverseDistanceCellCellStencil.o' failed
make: *** [/home/mqnguyen/Code/OpenFOAM/OpenFOAM-plus/build/linux64GccDPInt32Opt/src/overset/cellCellStencil/trackingInverseDistance/trackingInverseDistanceCellCellStencil.o] Error 1
In file included from lnInclude/cellCellStencilObject.H:36:0,
from dynamicOversetFvMesh/dynamicOversetFvMeshTemplates.C:28,
from dynamicOversetFvMesh/dynamicOversetFvMesh.H:335,
from dynamicOversetFvMesh/dynamicOversetFvMesh.C:26:
lnInclude/cellCellStencil.H:229:13: fatal error: cellCellStencilTemplates.C: No such file or directory
# include "cellCellStencilTemplates.C"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
```https://develop.openfoam.com/Development/ThirdParty-common/-/issues/41ENH: Mesa- with - llvm2020-06-26T08:09:02ZPrashant SonakarENH: Mesa- with - llvmIn order to compile mesa with llvm (when using gcc), following works
[makeMesa.example](/uploads/f794bf098ab43f344363522d4e81122d/makeMesa.example)
we need
- [x] llvm config enviroment
- [x] mesa compilation in lib64 (presently seem ...In order to compile mesa with llvm (when using gcc), following works
[makeMesa.example](/uploads/f794bf098ab43f344363522d4e81122d/makeMesa.example)
we need
- [x] llvm config enviroment
- [x] mesa compilation in lib64 (presently seem to do in lib for centos7.1)
@markhttps://develop.openfoam.com/Development/openfoam/-/issues/1164ENH: llvm LD_LIBRARY_PATH2019-12-09T22:37:28ZPrashant SonakarENH: llvm LD_LIBRARY_PATHWhile using Mesa with LLVM as noted in
https://develop.openfoam.com/Development/ThirdParty-plus/issues/41
we need LLVM path in environment when using gcc compiler. Something in etc/config.*/vtk ??
@markWhile using Mesa with LLVM as noted in
https://develop.openfoam.com/Development/ThirdParty-plus/issues/41
we need LLVM path in environment when using gcc compiler. Something in etc/config.*/vtk ??
@markhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/42BUG: [to be re-confirmed] : empty directory when using ThirdParty within Open...2019-01-09T10:15:33ZPrashant SonakarBUG: [to be re-confirmed] : empty directory when using ThirdParty within OpenFOAM installation folderWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markhttps://develop.openfoam.com/Development/openfoam/-/issues/1165snappyHexMesh Warning2020-01-08T14:46:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh Warning```
--> FOAM Warning :
From function void Foam::HashTable<T, Key, Hash>::resize(Foam::label) [with T = int; Key = int; Hash = Foam::Hash<int>; Foam::label = int]
in file HashTable.C at line 570
HashTable contains 395 cannot ...```
--> FOAM Warning :
From function void Foam::HashTable<T, Key, Hash>::resize(Foam::label) [with T = int; Key = int; Hash = Foam::Hash<int>; Foam::label = int]
in file HashTable.C at line 570
HashTable contains 395 cannot resize(0)
```Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1166snappyHexMesh: positional smoothing modifies geometry2019-01-10T15:01:07ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh: positional smoothing modifies geometrypositional smoothing modifies boundary points. In below I set the 3D cursor on the mesh before positional smoothing (but after expansion ratio smoothing). The mesh after positional smoothing has changed the boundary
![after_positional_s...positional smoothing modifies boundary points. In below I set the 3D cursor on the mesh before positional smoothing (but after expansion ratio smoothing). The mesh after positional smoothing has changed the boundary
![after_positional_smoothing](/uploads/dcdc983f4c8c2307e93afe2c8eb8a3fd/after_positional_smoothing.png)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1167mapFields : zero values on processor interface2021-07-06T15:17:17ZPrashant SonakarmapFields : zero values on processor interfacecross reference: EP#814cross reference: EP#814AdminAdmin