Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T22:22:46Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1006foamNewSource missing libraries in Make/options2019-12-09T22:22:46ZAdminfoamNewSource missing libraries in Make/optionsThe following will fail:
```
cd $WM_PROJECT_USER_DIR
mkdir -p applications/solvers/electromagnetics/rodFoam
cd applications/solvers/electromagnetics/rodFoam
foamNewSource App rodFoam
sed -i s/FOAM_APPBIN/FOAM_USER_APPBIN/g Make/files
wma...The following will fail:
```
cd $WM_PROJECT_USER_DIR
mkdir -p applications/solvers/electromagnetics/rodFoam
cd applications/solvers/electromagnetics/rodFoam
foamNewSource App rodFoam
sed -i s/FOAM_APPBIN/FOAM_USER_APPBIN/g Make/files
wmake
```
Error message:
```
$FOAM_SRC/finiteVolume/lnInclude/cyclicAMIFvPatch.H:39:10: fatal error: cyclicAMILduInterface.H: No such file or directory
#include "cyclicAMILduInterface.H"
^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```
It will compile if I manually add meshTools in Make/options. However, I think it would be nice of the template is at a state that allows it to be compiled without manual modifications.https://develop.openfoam.com/Development/openfoam/-/issues/880cannot pass additional arguments to foamEtcFile2019-12-09T22:18:11ZMark OLESENcannot pass additional arguments to foamEtcFileWith the foamEtcFile `-sh` argument, it is possible to generate statements for direct evaluation. However, it does not allow for passing of additional arguments. Eg,
```
eval $(foamEtcFile -sh file -- args)
```With the foamEtcFile `-sh` argument, it is possible to generate statements for direct evaluation. However, it does not allow for passing of additional arguments. Eg,
```
eval $(foamEtcFile -sh file -- args)
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/274BUG: single locationInMesh behavior now broken when compared with the foundat...2016-10-18T05:05:13ZAdminBUG: single locationInMesh behavior now broken when compared with the foundation codeThe single locationInMesh behavior is now broken when there is a geometry based cellZone defined when compared to the foundation code.
I've attached 3 pics and the model. The geometry pic is a pipe with a cellZone geometry defined in t...The single locationInMesh behavior is now broken when there is a geometry based cellZone defined when compared to the foundation code.
I've attached 3 pics and the model. The geometry pic is a pipe with a cellZone geometry defined in the middle.
![geometry](/uploads/80450e9dd316c13340de821bbaf3fd13/geometry.PNG)
The "3.0.x_mesh_with_cellZone.png" pic is what foundation version 3.0.x produces when a single locationInMesh is defined to one side of the cellZone. 3.0.x correctly sets the middle to one cellZone and the rest of the pipe to defaultFaces.
![3.0.x_mesh_with_cellZone](/uploads/91dace921e83fe4d3c8fc443c9663e92/3.0.x_mesh_with_cellZone.PNG)
The "v1606_mesh_with_cellZone_broken.PNG" shows what v1606 produces using the same model. It cuts off half the pipe and then leaks out into the background mesh. Not cool.
![v1606_mesh_with_cellZone_broken](/uploads/2e937dd4d15eebf0371ec383085e0347/v1606_mesh_with_cellZone_broken.PNG)
I know there has been a lot of changes so if I'm missing something let me know. I have tested the locationsInMesh functionality and that works OK for this model, but the single locationInMesh fails. I've attached the model.
[mesh_issue.tar.gz](/uploads/3f1f0af8bf58b7d1b42746861e3892d9/mesh_issue.tar.gz)https://develop.openfoam.com/Development/openfoam/-/issues/800sphereSurfactantFoam and $(FOAM_USER_APPBIN )2018-04-15T20:13:00ZAdminsphereSurfactantFoam and $(FOAM_USER_APPBIN )Hi all,
Inside the Make/files of sphereSurfactantFoam the binary location seems to be set to $(FOAM_USER_APPBIN), not sure if this is really a bug
EXE = $(FOAM_USER_APPBIN)/sphereSurfactantFoam
Cheers
AndreaHi all,
Inside the Make/files of sphereSurfactantFoam the binary location seems to be set to $(FOAM_USER_APPBIN), not sure if this is really a bug
EXE = $(FOAM_USER_APPBIN)/sphereSurfactantFoam
Cheers
Andreahttps://develop.openfoam.com/Development/openfoam/-/issues/1218Missing information in the section for RPM installation2023-12-07T19:00:15ZAdminMissing information in the section for RPM installationIn this page: https://www.openfoam.com/download/install-binary-linux.php - in the very first section "RPM Installation", it's missing the instructions on how to activate the OpenFOAM-v1812 shell environment...
I only spotted this becaus...In this page: https://www.openfoam.com/download/install-binary-linux.php - in the very first section "RPM Installation", it's missing the instructions on how to activate the OpenFOAM-v1812 shell environment...
I only spotted this because of this post: https://www.cfd-online.com/Forums/openfoam-installation/215231-rpm-installation-openfoam-v1812-opensuse-15-0-a.html#post726007
\#\# Reattaching the author to the issue ticket: @wyldckat \#\#https://develop.openfoam.com/Development/openfoam/-/issues/640pRefValue not preserved in closed-domain simulation2017-11-16T05:08:53ZPrashant SonakarpRefValue not preserved in closed-domain simulationEP#474EP#474Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/558need settings for cray compilers and cray-mpich2017-12-18T23:18:22ZMark OLESENneed settings for cray compilers and cray-mpichMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1060improvements for topoSet2020-11-17T13:16:45ZMark OLESENimprovements for topoSet- need to distinguish between topoSetSource (CELL, FACE, POINT)
- support multiple zones, multiple patches
- keyword consistency (eg, centre vs origin)- need to distinguish between topoSetSource (CELL, FACE, POINT)
- support multiple zones, multiple patches
- keyword consistency (eg, centre vs origin)v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/147tutorials/heatTransfer/chtMultiRegionFoam/snappyMultiRegionHeater slow2019-09-20T13:24:55ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtutorials/heatTransfer/chtMultiRegionFoam/snappyMultiRegionHeater slowTutorial seems to spend forever in "GAMG: Solving for p_rgh"
GAMG: Solving for p_rgh, Initial residual = 0.03162479, Final residual = 1.431729e-07, No Iterations 1000
Tutorial seems to spend forever in "GAMG: Solving for p_rgh"
GAMG: Solving for p_rgh, Initial residual = 0.03162479, Final residual = 1.431729e-07, No Iterations 1000
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/944aborted sourcing of etc/bashrc causes problems2018-07-20T13:15:11ZMark OLESENaborted sourcing of etc/bashrc causes problemsIf the sourcing of the etc/bashrc is somehow aborted part way through, the `WM_SHELL_FUNCTIONS` can be left set.
This causes subsequent sourcing to fail, since it undefines the functions prior to use!If the sourcing of the etc/bashrc is somehow aborted part way through, the `WM_SHELL_FUNCTIONS` can be left set.
This causes subsequent sourcing to fail, since it undefines the functions prior to use!Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/784wmkdep runs out of open file descriptors2023-12-07T19:03:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwmkdep runs out of open file descriptorswmkdep.l runs out of open file descriptors, especially when using the -q option on wmake.wmkdep.l runs out of open file descriptors, especially when using the -q option on wmake.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1189decomposePar faMesh fails2019-02-02T15:47:08ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar faMesh failsTry to decompose e.g. tutorials/finiteArea/surfactantFoam/planeTransport
@sergio @andyTry to decompose e.g. tutorials/finiteArea/surfactantFoam/planeTransport
@sergio @andyMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/654postprocessing surface fields gives warnings about 'unexpected type volScalar...2020-01-03T11:23:59ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.compostprocessing surface fields gives warnings about 'unexpected type volScalarField' etcMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/936coded functionObject ignores codeInclude and localCode sections2018-07-12T13:34:19ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcoded functionObject ignores codeInclude and localCode sectionsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/534OStringStream rewind probably not behaving as expected2017-07-18T15:01:50ZMark OLESENOStringStream rewind probably not behaving as expectedThe rewind only repositions the output pointer, but does not truncate the output buffer.
Eg,
OStringStream os;
os << "1234567890";
os.rewind();
os << "abc";
produces "abc4567890" as output, not "abc" as may be expected....The rewind only repositions the output pointer, but does not truncate the output buffer.
Eg,
OStringStream os;
os << "1234567890";
os.rewind();
os << "abc";
produces "abc4567890" as output, not "abc" as may be expected.
Suggested recourse, provide explicit `reset()` method to reposition output pointer and buffer.
@andyv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/918inconsistency in defining turbulence field "R"2018-10-09T08:55:44ZAdmininconsistency in defining turbulence field "R"Hello,
There is inconsistency in defining turbulence field "R". Webpage https://www.openfoam.com/documentation/cpp-guide/html/guide-fos-field-turbulence-fields.html#sec-fos-field-turbulence-fields-usage shows Fields stored on the mesh d...Hello,
There is inconsistency in defining turbulence field "R". Webpage https://www.openfoam.com/documentation/cpp-guide/html/guide-fos-field-turbulence-fields.html#sec-fos-field-turbulence-fields-usage shows Fields stored on the mesh database with the prefix ***turbulenceModel*** whereas it is stored with ***turbulenceProperties***
@Pawan @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/853points file created by "surfacesSampling" is in disorder2018-06-15T08:32:01ZAdminpoints file created by "surfacesSampling" is in disorderHello,
I used the surfaceSampling utility to creat the velocity surface data for timeVaringMappedFixedValue boundary condition. I chose a faceCentres file in one of time-series surfaceSamping folders, then renamed it as "points" for the...Hello,
I used the surfaceSampling utility to creat the velocity surface data for timeVaringMappedFixedValue boundary condition. I chose a faceCentres file in one of time-series surfaceSamping folders, then renamed it as "points" for the input.
I confirmed that I have the same point number in my points file and my velocity surface data file.
But it is strange that they are numbered differently. Normally, my inlet should be:
![image](/uploads/d24db80fa969a766f39b7b2e23e62797/image.png)
But, now it looks like:
![image](/uploads/8ac76c2d679e879df1b7dfaa2b55906c/image.png)
I have this problem when I used a HPC cluster with 18 processors. I double checked it in my own PC with 18 processors. The two files match. I cannot understand.
I attach the points file and the velocity file. Hope you can give a help.
[points.txt](/uploads/d5a26f7d4f40e82cff7c7103518b761b/points.txt)[U.txt](/uploads/bd51684a503115cd2e3fe1c8397242c8/U.txt)
Best Regards,Prashant SonakarPrashant Sonakarhttps://develop.openfoam.com/Development/openfoam/-/issues/544Intel compiler issues with operator "" _deg2021-03-30T17:34:18ZMark OLESENIntel compiler issues with operator "" _degicc version 17.0.4 (gcc version 4.8.5 compatibility)
AMIMethod.C(304): internal error: assertion failed at: "shared/cfe/edgcpfe/symbol_tbl.c", line 16334
if (cosI > Foam::cos(89.0_deg))
@andyicc version 17.0.4 (gcc version 4.8.5 compatibility)
AMIMethod.C(304): internal error: assertion failed at: "shared/cfe/edgcpfe/symbol_tbl.c", line 16334
if (cosI > Foam::cos(89.0_deg))
@andyMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/553argList should forgive/ignore lone dash.2017-08-01T11:12:01ZMark OLESENargList should forgive/ignore lone dash.A lone dash can inadvertently arise from TAB-completion (issue #551). Since an option without a name doesn't make much sense, we could/should trap this and either emit a warning or just silently ignore it.
@froesler, @Prashant, @andyA lone dash can inadvertently arise from TAB-completion (issue #551). Since an option without a name doesn't make much sense, we could/should trap this and either emit a warning or just silently ignore it.
@froesler, @Prashant, @andyMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1207scotch, ptscotch input checking2020-01-08T14:37:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch, ptscotch input checking<!--
*** 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
scotch, ptscotch do not check processorWeights inputMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com