Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T22:22:46Zhttps://develop.openfoam.com/Development/openfoam/-/issues/935Lagrangian tracking can hang for particle exactly on cell centre2019-12-09T22:22:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comLagrangian tracking can hang for particle exactly on cell centreIf a particle gets seeded on exactly the cell centre (e.g. in particle::locate) the tracking might get stuck in a loop since all constituent tets all say the particle is outside.If a particle gets seeded on exactly the cell centre (e.g. in particle::locate) the tracking might get stuck in a loop since all constituent tets all say the particle is outside.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/840BUG: ConeInjection/ConeNozzleInjection injectionPosition in parallel2019-12-09T22:18:11ZAdminBUG: ConeInjection/ConeNozzleInjection injectionPosition in parallelThe use of rndGen.sample01 instead of rndGen.globalSample01 for calculating the
tanVec1_, tanVec2_ and beta angle leads to every processor having a different reference frame and
thus the injection position will be different on every pro...The use of rndGen.sample01 instead of rndGen.globalSample01 for calculating the
tanVec1_, tanVec2_ and beta angle leads to every processor having a different reference frame and
thus the injection position will be different on every processor.
In the .C files, just change these snippets to using globalSample
===================
while(magTangent < SMALL)
{
vector v = rndGen.globalSample01<vector>();
tangent = v - (v & direction_)*direction_;
magTangent = mag(tangent);
}
===================
and
===================
scalar beta = mathematical::twoPi*rndGen.globalSample01<scalar>();
===================https://develop.openfoam.com/Development/openfoam/-/issues/1181DOCU: correct the angle input to deg2019-01-24T23:07:55ZPrashant SonakarDOCU: correct the angle input to degsrc/mesh/extrudeModel/sector/sector.H lists the angle in rad.
Please correct this to deg
@marksrc/mesh/extrudeModel/sector/sector.H lists the angle in rad.
Please correct this to deg
@markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/92BUG: foamToEnsight failed with epsilon field from applyBL2016-05-30T06:01:01ZPrashant SonakarBUG: foamToEnsight failed with epsilon field from applyBLAttached case replicating the behavior with new applyBoundaryLayer code from 92ae4fbe
Should the fields be written only corresponding to turbulence model being used?
[case_ofplus_foamToEnsight_failure.tgz](/uploads/dccead1228870cbd...Attached case replicating the behavior with new applyBoundaryLayer code from 92ae4fbe
Should the fields be written only corresponding to turbulence model being used?
[case_ofplus_foamToEnsight_failure.tgz](/uploads/dccead1228870cbdb91a557de5c6fe9f/case_ofplus_foamToEnsight_failure.tgz)
@Sergio AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1244no reconstruct script in Allrun (tut/multiphase/interIsoFoam/iobasin)2019-03-22T20:06:24ZAdminno reconstruct script in Allrun (tut/multiphase/interIsoFoam/iobasin)<!--
*** 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
In tut/multiphase/interIsoFoam/iobasin/Allrun, there is no script for reconstruct after mpi-run.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
### Example case
tut/multiphase/interIsoFoam/iobasin
### What is the current *bug* behaviour?
<!-- What actually happens -->
### What is the expected *correct* behavior?
<!-- What you should see instead -->
### Relevant logs and/or images
<!--
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
OpenFOAM version :v1812
Operating system :ubuntu18.04
Compiler :gcc-7.3.0
### Possible fixes
Add the following line to the last of Allrun.
runApplication reconstructParhttps://develop.openfoam.com/Development/openfoam/-/issues/302Possible documentation mismatch for IDDESdelta2016-11-17T16:42:25ZRoger AlmenarPossible documentation mismatch for IDDESdeltaIn the file OpenFOAM-plus/.../IDDESDelta/IDDESDelta.C , the IDDESdelta seems to be calculated based on face2face distance, in the direction normal to the wall.
However, in the H file it is mentioned: IDDESDelta used by the IDDES (im...In the file OpenFOAM-plus/.../IDDESDelta/IDDESDelta.C , the IDDESdelta seems to be calculated based on face2face distance, in the direction normal to the wall.
However, in the H file it is mentioned: IDDESDelta used by the IDDES (improved low Re Spalart-Allmaras DES model) The min and max delta are calculated using the double distance of the min or max from the face centre to the cell centre.
Could we check if there is a mismatch between the documentation and the code?https://develop.openfoam.com/Development/openfoam/-/issues/959noise detection of time step2024-01-05T17:09:20ZMattijs 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.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/264foamCleanPath performs strangely if username/path has @ and . characters2019-12-09T22:04:13ZAdminfoamCleanPath performs strangely if username/path has @ and . charactersDear all,
I'm trying to compile the v1606+ with standard GNU tools, on a CentOS 7 based cluster. When I source etc/bashrc, i receive a strange error, like
```
[lcarvalheiro@argus etc]$ source bashrc
sed: -e expressão #1, cará...Dear all,
I'm trying to compile the v1606+ with standard GNU tools, on a CentOS 7 based cluster. When I source etc/bashrc, i receive a strange error, like
```
[lcarvalheiro@argus etc]$ source bashrc
sed: -e expressão #1, carácter 43: opção desconhecida para 's'
sed: -e expressão #1, carácter 56: opção desconhecida para 's'
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: No such file or directory
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: No such file or directory
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: No such file or directory
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: No such file or directory
-bash: uname: No such file or directory
Your "" operating system is not supported by this release
of OpenFOAM. For further assistance, please contact www.OpenFOAM.com
-bash: sed: command not found
-bash: mpicc: command not found
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: command not found
/home/lcarvalheiro@UA.PT/OpenFOAM/OpenFOAM-v1606+/bin/foamCleanPath: line 110: sed: command not found
-bash: sed: No such file or directory
```
(obviously, I get an empty PATH and LD_PATH)
If I comment the if condition in lines 108-111 on the file foamCleanPath, sourcing etc/bashrc executes without errors, but Allwmake ends with
```
========================================
Done ThirdParty Allwmake
========================================
+ wmakePrintBuild -check
no git description found
+ wrmo OpenFOAM/global/global.o
wrmo error: could not find Make directory
[lcarvalheiro@argus OpenFOAM-v1606+]$
```
Is there any way to tackle this issue?
Thanks in advancehttps://develop.openfoam.com/Development/openfoam/-/issues/245uniform/time dictionary searched for in all time directories2021-07-06T10:45:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/time dictionary searched for in all time directoriesAll the IOdictionaries will be searched for in all previous time instances. This is fine for e.g. polyMesh files (points, faces, etc) but wrong for e.g. uniform/time. Also it is very expensive when there are lots of time directories.
At...All the IOdictionaries will be searched for in all previous time instances. This is fine for e.g. polyMesh files (points, faces, etc) but wrong for e.g. uniform/time. Also it is very expensive when there are lots of time directories.
Attached files add some debug printing to see when it is happening (e.g. with foamToEnsight)
[IOobject.C](/uploads/e181e7fb456c4690b208304dffe67704/IOobject.C)[log.foamToEnsight](/uploads/48c62a1d1845d236c894853038e83ef7/log.foamToEnsight)https://develop.openfoam.com/Development/openfoam/-/issues/142BUG: no geometry written for foamToEnsightParts with moving mesh2023-12-07T19:01:58ZMark OLESENBUG: no geometry written for foamToEnsightParts with moving meshMoving geometries should be written to data/NNNNNN/geometry but are not.Moving geometries should be written to data/NNNNNN/geometry but are not.Mark OLESENMark OLESENhttps://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/1003incorrect kahip resolution with absolute paths2019-12-09T22:22:46ZMark OLESENincorrect kahip resolution with absolute paths- affects installations using a central (non-ThirdParty) location for KAHIP.
- reported https://github.com/spack/spack/pull/8982- affects installations using a central (non-ThirdParty) location for KAHIP.
- reported https://github.com/spack/spack/pull/8982Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1040inconsistency in K/kappa reading for solidProperties2018-10-15T07:53:49ZMark OLESENinconsistency in K/kappa reading for solidPropertiesIf both `K` and `kappa` are present - on construct `K` will be used and `kappa` ignored.
For dictionary re-reading, both `K` and `kappa` are read if present. `kappa` is read second and will thus take effect.
- should use a Compat method...If both `K` and `kappa` are present - on construct `K` will be used and `kappa` ignored.
For dictionary re-reading, both `K` and `kappa` are read if present. `kappa` is read second and will thus take effect.
- should use a Compat method to handle this.https://develop.openfoam.com/Development/openfoam/-/issues/216runTimePostProcessing FO scalarBar label and picture numbering2017-03-16T05:40:18ZMatej FormanrunTimePostProcessing FO scalarBar label and picture numberingIn FO runTimePostProcessing the title for scalarBar in vertical position in not justified nicely to the scalar bar. There is a big gap between the title and the scalar bar.
Testing on $FOAM_TUTORIALS/multiphase/interFOAM/laminar/damBre...In FO runTimePostProcessing the title for scalarBar in vertical position in not justified nicely to the scalar bar. There is a big gap between the title and the scalar bar.
Testing on $FOAM_TUTORIALS/multiphase/interFOAM/laminar/damBreak, added FO to controlDict (attached) creates not nice description. Might be nice to allow user to control the justification of the text and other parameters of the label. Maybe possibility to allow vertical orientation (for longer names) of the text via vtk functions.
Other issue is, that all pictures has the same name in different directories which makes it difficult to create the movie or doing other post-processing unless the user is skilled with shell commands.
Attached the [controlDict](/uploads/1b327ef9625fcb38449a7148b10ddf09/controlDict) with the FO definition and produced picture ![image.0000](/uploads/be69a074a2fdd83a83253807bf12d543/image.0000.png). AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/514scale option for all geometry reading2017-12-18T23:20:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscale option for all geometry reading- snappyHexMesh, foamyHexMesh, blockMesh all support scaling geometry upon reading.
- of the surface utilities only:
```
surfaceConvert
surfaceFeatureConvert
surfaceMeshConvert
surfaceMeshConvertTesting
surfaceMeshExport
surfaceMeshImpor...- snappyHexMesh, foamyHexMesh, blockMesh all support scaling geometry upon reading.
- of the surface utilities only:
```
surfaceConvert
surfaceFeatureConvert
surfaceMeshConvert
surfaceMeshConvertTesting
surfaceMeshExport
surfaceMeshImport
surfaceMeshInfo
surfaceTransformPoints
```
support it.
- can we extend all others to support it as well? Especially surfaceFeatureExtract.
- also e.g. BCs (pointDisplacement ones), postprocessingMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/212"Current Release" links are broken in some of the side menus2016-08-18T10:16:53ZAdmin"Current Release" links are broken in some of the side menusThe following pages still refer to the v3.0+ on the side menu:
* http://openfoam.com/download/install-source.php
* http://openfoam.com/download/installation.php
* http://openfoam.com/download/install-binary.php
* http://ope...The following pages still refer to the v3.0+ on the side menu:
* http://openfoam.com/download/install-source.php
* http://openfoam.com/download/installation.php
* http://openfoam.com/download/install-binary.php
* http://openfoam.com/download/install-windows.php
* http://openfoam.com/download/release-history.php
* http://openfoam.com/download/index.php
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/832decomposePar does not clean up all2020-01-06T10:39:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar does not clean up allvalgrind --leak-check=full --show-reachable=yes decomposePar
This seems to be related to libgomp:
```
==12573==
==12573== HEAP SUMMARY:
==12573== in use at exit: 8 bytes in 1 blocks
==12573== total heap usage: 55,396 allocs, 5...valgrind --leak-check=full --show-reachable=yes decomposePar
This seems to be related to libgomp:
```
==12573==
==12573== HEAP SUMMARY:
==12573== in use at exit: 8 bytes in 1 blocks
==12573== total heap usage: 55,396 allocs, 55,395 frees, 7,128,433 bytes allocated
==12573==
==12573== 8 bytes in 1 blocks are still reachable in loss record 1 of 1
==12573== at 0x4C2A110: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==12573== by 0xB9DE858: ??? (in /usr/lib64/libgomp.so.1.0.0)
==12573== by 0xB9EDDE6: ??? (in /usr/lib64/libgomp.so.1.0.0)
==12573== by 0xB9DCF09: ??? (in /usr/lib64/libgomp.so.1.0.0)
==12573== by 0x400F1E9: call_init.part.0 (in /lib64/ld-2.22.so)
==12573== by 0x400F2D2: _dl_init (in /lib64/ld-2.22.so)
==12573== by 0x4001229: ??? (in /lib64/ld-2.22.so)
==12573== by 0x1: ???
==12573== by 0xFFEFFD5BA: ???
==12573== by 0xFFEFFD5C7: ???
==12573==
==12573== LEAK SUMMARY:
==12573== definitely lost: 0 bytes in 0 blocks
==12573== indirectly lost: 0 bytes in 0 blocks
==12573== possibly lost: 0 bytes in 0 blocks
==12573== still reachable: 8 bytes in 1 blocks
==12573== suppressed: 0 bytes in 0 blocks
==12573==
==12573== For counts of detected and suppressed errors, rerun with: -v
==12573== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
```https://develop.openfoam.com/Development/openfoam/-/issues/174src/Allwmake causes rebuild of globa.Cver when building outside git2016-12-23T12:44:51ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsrc/Allwmake causes rebuild of globa.Cver when building outside gitwmakePrintBuild -check
returns a 1 exit code in case of not building under git and this triggers recompilation of global.Cver every time
wmakePrintBuild -check
returns a 1 exit code in case of not building under git and this triggers recompilation of global.Cver every time
https://develop.openfoam.com/Development/openfoam/-/issues/919Ensight format for writing non-time based fields2019-07-11T22:15:57ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comEnsight format for writing non-time based fieldsSome surface utilities write ensight using the (sampled)surfaceWriters. These files do not have a time-directory in the name which upsets the extraction of the timename inside the ensightSurfaceWriterTemplates.CSome surface utilities write ensight using the (sampled)surfaceWriters. These files do not have a time-directory in the name which upsets the extraction of the timename inside the ensightSurfaceWriterTemplates.CMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1175snappyHexMesh occasionally hangs in parallel layer extrusion2019-12-09T22:37:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh occasionally hangs in parallel layer extrusion- case was hanging in parallel
- with one of the processors in an infinite loop (in addPatchCellLayer)
Problem:
- shm layer addition can get any mesh to add layers to.
- sometimes this mesh might have a baffle on the patch-to-extrude
(-...- case was hanging in parallel
- with one of the processors in an infinite loop (in addPatchCellLayer)
Problem:
- shm layer addition can get any mesh to add layers to.
- sometimes this mesh might have a baffle on the patch-to-extrude
(- a baffle is two back-to-back faces that share the same points)
- this is of course not possible to extrude so we disable this
However
- what if the baffle faces are on different processors
- each processor does not detect that the face is part of a baffle
- so might try to extrude
and this would lead to a hang since all the edges of the face connect to the same neighbour (admittedly on a different processor).Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com