Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-07-18T15:01:50Zhttps://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.comhttps://develop.openfoam.com/Development/openfoam/-/issues/425BUG: Noise utility overwrites data2017-04-18T13:40:34ZPrashant SonakarBUG: Noise utility overwrites dataRefer EP#338
E.g. if inputFiles ("location1/p" "location2/p")
the output for 2 is overwritten on 1.Refer EP#338
E.g. if inputFiles ("location1/p" "location2/p")
the output for 2 is overwritten on 1.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1182find in list with predicate2019-01-26T20:13:47ZMark OLESENfind in list with predicatecan currently use find/found for UList, or even with the older (deprecated) findIndex, but these search for a value. Would be useful to allow a predicate.
@Mattijscan currently use find/found for UList, or even with the older (deprecated) findIndex, but these search for a value. Would be useful to allow a predicate.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1200Function1::New input checking2020-01-08T14:49:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comFunction1::New input checking### Summary
Function1::New produces not very good error messages if the dictionary entry does not exist.### Summary
Function1::New produces not very good error messages if the dictionary entry does not exist.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/328Closed incompressible two-phase system: set pressure reference2021-07-06T10:50:53ZAdminClosed incompressible two-phase system: set pressure referenceI am testing the solver twoPhaseEulerFoam (version 3.0.x) in a closed system to see the visualize the settling process. In my case, I set that fluids are rigorously incompressible.
Since the system is closed, I set a no-slip b.c. for vel...I am testing the solver twoPhaseEulerFoam (version 3.0.x) in a closed system to see the visualize the settling process. In my case, I set that fluids are rigorously incompressible.
Since the system is closed, I set a no-slip b.c. for velocities (fixedValue (0 0 0)) in all patches and a fixedFluxPressure b.c. for p_rgh.
In the dictionary fvSolution, I set pRefCell and pRefValue equal to 0 and 1e5 (as in internalField), respectively. Using GAMG solver for the solution of the pressure-associated linear system, the simulation crashes after 1 time-step. Using PCG solver, the simulation goes on but with an important increase in the number of iterations. The only way that I have to use GAMG for the pressure linear system is to fix a pressure in a patch and avoid to specify pRefCell and pRefValue. But, of course, this is not rigorous since I am considering an incompressible closed system. I attached a case for testing. In the case test, I sett
In the userguide, it is written that "In a closed incompressible system, pressure is relative: it is the pressure range that matters not the absolute values. In these cases, the solver sets a reference level of pRefValue in cell pRefCell where p is the name of the pressure solution variable. Where the pressure is p_rgh, the names are p_rhgRefValue and p_rhgRefCell respectively". Nevertheless, "createSystem.H" requires a pRefCell and pRefValue, not a p_rghRefCell and p_rghRefValue.
I have tried to modify the "createSystem.H" but the case asks for a "pRefCell" and "pRefValue".
Thanks for your attention,
Nicolò[caseTest.tar.gz](/uploads/e4ecafef245b2d2acea06351515b1385/caseTest.tar.gz)
\#\# Reattaching the author to the issue ticket: @nic92 \#\#https://develop.openfoam.com/Development/openfoam/-/issues/713Field has no xfer()2018-03-26T20:14:18ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comField has no xfer()with
```
scalarField edgeWeight(...);
```
then the .xfer() returns a List<scalar> instead of a Field<scalar>
The workaround is
```
xferMoveTo<scalarField, scalarList>(edgeWeight)
```with
```
scalarField edgeWeight(...);
```
then the .xfer() returns a List<scalar> instead of a Field<scalar>
The workaround is
```
xferMoveTo<scalarField, scalarList>(edgeWeight)
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/994volumeType >> is not opposite of <<2018-09-11T12:17:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comvolumeType >> is not opposite of <<Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/483strange ordering for geometricSurfacePatch Istream constructor2020-03-13T14:23:53ZMark OLESENstrange ordering for geometricSurfacePatch Istream constructor`geometricSurfacePatch(Istream& is, const label index)` expects type,name but the `<<` and `>>` operators both have name,type
Could result in unexpected behaviour somewhere.`geometricSurfacePatch(Istream& is, const label index)` expects type,name but the `<<` and `>>` operators both have name,type
Could result in unexpected behaviour somewhere.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1191flattenMesh has to have flattish starting mesh2019-02-04T18:02:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comflattenMesh has to have flattish starting meshIt would be nice to be able to supply the plane normal instead of having twoDPointCorrector try to find it. This quite often fails due to the tight tolerance. Also maybe use the patch information?It would be nice to be able to supply the plane normal instead of having twoDPointCorrector try to find it. This quite often fails due to the tight tolerance. Also maybe use the patch information?https://develop.openfoam.com/Development/openfoam/-/issues/785verbatim string (inbetween #{ .. #} , for e.g. code sections) is limited to 8...2023-12-07T19:03:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comverbatim string (inbetween #{ .. #} , for e.g. code sections) is limited to 8000 chars.Larger code sections might not fit inside a single verbatim string. Since it is a static char array there is no real limit on its size.
- workaround: move sections of code into included file
- solution: increase size (but this permanentl...Larger code sections might not fit inside a single verbatim string. Since it is a static char array there is no real limit on its size.
- workaround: move sections of code into included file
- solution: increase size (but this permanently increases memory usage)
- or : assign to stringMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/277sed: -e expression #1, char 72: unknown option to `s' ( And some funky PATH e...2016-10-29T08:39:43ZAdminsed: -e expression #1, char 72: unknown option to `s' ( And some funky PATH errors )```
[ steven.walton ] [~] > lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
```
I am also on a domain controlled computer.
When sourcing `/opt/openfoa...```
[ steven.walton ] [~] > lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
```
I am also on a domain controlled computer.
When sourcing `/opt/openfoam4/etc/bashrc` and opening a new bash terminal I get the following error
```
sed: -e expression #1, char 72: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
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.org
Command 'sed' is available in '/bin/sed'
Command 'mpicc' is available in '/usr/bin/mpicc'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
The command could not be located because '/bin' is not included in the PATH environment variable.
mpicc: command not found
sed: command not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
/opt/openfoam4/bin/foamCleanPath: 110: /opt/openfoam4/bin/foamCleanPath: sed: not found
bash: sed: No such file or directory
/opt/openfoam4/bin/foamCleanPath: 129: /opt/openfoam4/bin/foamCleanPath: sed: not found
```
The worse part of this is that `PATH` gets completely overwritten!
I can fix some of this by getting rid of line 154 in `/opt/openfoam4/etc/bashrc`. That reduces to the following error
```
sed: -e expression #1, char 72: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
sed: -e expression #1, char 111: unknown option to `s'
```
If I am running in zsh (yes, I know it says bashrc) I get
```
sed: -e expression #1, char 72: unknown option to `s'
/opt/openfoam4/etc/config.sh/aliases:73: bad option: -t
```
If I enter bash and type `wmRefresh` it overwrites `PATH` and I now have no access to simple commands like `ls`. ( Removing the `-t` in that line reduces the last error in zsh but adds the line `bash: type: wmRefresh: not found` into the list of errors for bash.) Which is strange because the comment above line 73 in `/opt/openfoam4/etc/config.sh/aliases` says `For backward-compatibility unalias wmRefresh if it is defined as an alias`.
Working through this one I see that `which wmRefresh` and `alias wmRefresh` return nothing. So getting the same behaviour in both shells ( and a lack of care for backwards compatibility at this point ) I found that I could just remove lines 74-80 in `/opt/openfoam4/etc/config.sh/aliases`. Note that if I just removed line 73 bash would have `PATH` overwritten again ( **why ever modify `PATH` when we have other environment variables?** ).
So at this point I am only left with the sed errors ( 1 in zsh and 3 in bash ). I cannot tell that I am getting any errors* in using OpenFoam, but as you might imagine it is quite annoying seeing multiple errors every time I open a new shell. I have been attempting to resolve these issues by looking at where `sed` has been used, but I'm not seeing a problem. It doesn't appear to be a `sed` command within `/opt/openfoam4/etc`, and grepping a directory back results is quite a log of commands.
So I am wondering if anyone else has had this error and solved it.
*To check validity through modifications I am just run the cavity icoFoam case, checking for the known solution.https://develop.openfoam.com/Development/openfoam/-/issues/865rndGen.position<label>(0, XXX) is not evenly distributed2019-12-09T22:18:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrndGen.position<label>(0, XXX) is not evenly distributedWhen using the
```
rndGen.position<label>(0, nDomains - 1);
```
to determine random decomposition it seems the entries 0 and nDomains-1 have only half the number of entries.
Replicate: run randomDecomp on a scaled up cavity (e.g. 1000x...When using the
```
rndGen.position<label>(0, nDomains - 1);
```
to determine random decomposition it seems the entries 0 and nDomains-1 have only half the number of entries.
Replicate: run randomDecomp on a scaled up cavity (e.g. 1000x1000).Mark OLESENMark OLESENhttps://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/677Medium loop- failures - 21.12.20172018-06-12T04:01:04ZPrashant SonakarMedium loop- failures - 21.12.2017Cases in :
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/
- compressible/sonicFoam/RAS/nacaAirfoil - solver failed
- multiphase/reactingTwoPhaseEulerFoam/laminar/steamInjection - solver failed
- multiphase/compressibleInt...Cases in :
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/
- compressible/sonicFoam/RAS/nacaAirfoil - solver failed
- multiphase/reactingTwoPhaseEulerFoam/laminar/steamInjection - solver failed
- multiphase/compressibleInterDyMFoam/laminar/sphereDrop -solver failed
- multiphase/interFoam/laminar/vofToLagrangian/eulerianInjection -solver failed
@andy @Mattijs @Sergio @markhttps://develop.openfoam.com/Development/openfoam/-/issues/566setSet dumps wrong vtk files of sets2020-01-22T21:31:06ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsetSet dumps wrong vtk files of setssetSet writes vtk files of sets with 0 elements, even when set has non-zero elements.setSet writes vtk files of sets with 0 elements, even when set has non-zero elements.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com