Development issueshttps://develop.openfoam.com/groups/Development/-/issues2024-01-05T17:09:20Zhttps://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/781Change default flag for lagrangian post-processing in paraview2018-05-15T10:22:04ZRoger AlmenarChange default flag for lagrangian post-processing in paraviewRequest to change the default flag under $FOAM_ETC/controlDict
```
// Write lagrangian "positions" file in v1706 format (at earlier)
writeLagrangianPositions 0;
```
from 0 to 1. Otherwise it is not possible to post-process lagrangian...Request to change the default flag under $FOAM_ETC/controlDict
```
// Write lagrangian "positions" file in v1706 format (at earlier)
writeLagrangianPositions 0;
```
from 0 to 1. Otherwise it is not possible to post-process lagrangian cases in Paraview, loading directly the OpenFOAM case.v1806Mark OLESENMark OLESENhttps://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/903ensight case with multiple clouds2021-07-06T13:18:34ZMark OLESENensight case with multiple cloudsensight only supports a single set of measured values. Outputting multiple clouds for a case is an error.
Could remedy by only emitting the first cloud and either ignore any others or creating separate case files for each of them.
The ...ensight only supports a single set of measured values. Outputting multiple clouds for a case is an error.
Could remedy by only emitting the first cloud and either ignore any others or creating separate case files for each of them.
The only problem with this approach is that we still need a `model:` entry in the case. The mesh bounding box would be a reasonable thing to generate.
@graupsv1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/460odd sizing for hash tables.2017-06-29T20:38:04ZMark OLESENodd sizing for hash tables.Came across a few odd things, especially when copy/copy-constructing from other hash tables.
* HashPtrTable copy from HashPtrTable: uses default size, not related to what it is copying
* HashTable from initializer_list uses list size, n...Came across a few odd things, especially when copy/copy-constructing from other hash tables.
* HashPtrTable copy from HashPtrTable: uses default size, not related to what it is copying
* HashTable from initializer_list uses list size, not 2*list size for its table
* HashSet from HashTable uses number of keys, not the table size.Version v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/922Add searchableSurface single point getVolumeType2018-07-10T16:07:40ZMark OLESENAdd searchableSurface single point getVolumeTypeFor #921 we need to cycle over potentially several surfaces and faces.
It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.For #921 we need to cycle over potentially several surfaces and faces.
It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/226When using a custom GCC stack with binutils included, sometimes CMake will fa...2019-12-09T22:04:11ZMark OLESENWhen using a custom GCC stack with binutils included, sometimes CMake will fail to configure the PV*Readersreported by @wyldckat as http://bugs.openfoam.org/view.php?id=2233reported by @wyldckat as http://bugs.openfoam.org/view.php?id=2233Version v1612Mark OLESENMark OLESENhttps://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/183ENH: extend coverage for wmUNSET2016-10-24T21:19:11ZPrashant SonakarENH: extend coverage for wmUNSETCertain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Certain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Version v1612Mark OLESENMark OLESENhttps://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/200maxDeltaxyz changes missed in turbulence model upgrade2019-12-09T22:04:10ZAdminmaxDeltaxyz changes missed in turbulence model upgradeThe maxDeltaxyz LES delta behaviour was updated in version 2.3.x to correct excessive lengths being calculated at changes in mesh refinement, e.g. the 2:1 levels generated by snappyHexMesh. These changes were not included when moving to...The maxDeltaxyz LES delta behaviour was updated in version 2.3.x to correct excessive lengths being calculated at changes in mesh refinement, e.g. the 2:1 levels generated by snappyHexMesh. These changes were not included when moving to the templated turbulence structureVersion v1612AdminAdminhttps://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.com