Development issueshttps://develop.openfoam.com/groups/Development/-/issues2021-01-25T13:38:59Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1932wall distance calculation correction for point-connected faces2021-01-25T13:38:59ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwall distance calculation correction for point-connected faces<!--
*** 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
You can see how your report will be re...<!--
*** 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
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
On one user case (ep 1442) it was reported that applyBoundaryLayer crashes. This seems to be due to the wall distance calculation. Upon visual inspection the code was not checking for duplicate faces enough so could run out of work array in extreme cases.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Cannot reproduce
### What is the current *bug* behaviour?
<!-- What actually happens -->
Crash in applyBoundaryLayers, seemingly from wall distance calculation (and cellDistFuncs correction for point-connected faces)
### 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
### Possible fixes
<!--
If you can, link to the line of code that might be responsible for the
problem
The "/label ~bug" text is a gitlab flag that will add the "bug" label to this
issue
-->
- use dynamically resized lists
- use more duplicate face checkingMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1931foamMonitor: Adding possibility to specify the file using process substitution2023-12-14T10:25:02ZGhost UserfoamMonitor: Adding possibility to specify the file using process substitutionHello,
When running a simulation and it stops for some reason several times, one ends up with multiple time-named directories in `postProcessing` directory, e.g:
```
postProcessing/forceCoeffs1/0
postProcessing/forceCoeffs1/0.5
postPro...Hello,
When running a simulation and it stops for some reason several times, one ends up with multiple time-named directories in `postProcessing` directory, e.g:
```
postProcessing/forceCoeffs1/0
postProcessing/forceCoeffs1/0.5
postProcessing/forceCoeffs1/2.4
...etc
```
IMO, one solution is to use bash process substitution to plot multiple files at once (currently foamMonitor doesn't allow that, and it doesn't support process substitution), e.g:
```
cd postProcessing/foceCoeffs1/
foamMonitor <(cat 0/forceCoeffs.dat <(tail +10 0.5/forceCoeffs.dat ) <(tail +10 2.4/forceCoeffs.dat) )
```
* Is it possible to implement that in foamMonitor script, if I may ask?
Thank youhttps://develop.openfoam.com/Development/openfoam/-/issues/1928BUG: geometricVoF included twice in interIsoFoam/Make/options2020-11-18T21:44:09ZJohan RoenbyBUG: geometricVoF included twice in interIsoFoam/Make/options`-I$(LIB_SRC)/transportModels/geometricVoF/lnInclude`
appears twice under EXE_INC in:
[https://develop.openfoam.com/Development/openfoam/-/blob/master/applications/solvers/multiphase/interIsoFoam/Make/options](https://develop.openfoam....`-I$(LIB_SRC)/transportModels/geometricVoF/lnInclude`
appears twice under EXE_INC in:
[https://develop.openfoam.com/Development/openfoam/-/blob/master/applications/solvers/multiphase/interIsoFoam/Make/options](https://develop.openfoam.com/Development/openfoam/-/blob/master/applications/solvers/multiphase/interIsoFoam/Make/options)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1927Possible typo in solidProperties.C variable name definition2020-11-26T01:16:19ZRobin KnowlesPossible typo in solidProperties.C variable name definition<!--
*** 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
You can see how your report will be re...<!--
*** 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
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
Possible typo in the solidProperties.C in the `Hf` variable name
### 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 : v2006
### Possible fixes
```diff
.../solidProperties/solidProperties/solidProperties.C | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/thermophysicalModels/thermophysicalProperties/solidProperties/solidProperties/solidProperties.C b/src/thermophysicalModels/thermophysicalProperties/solidProperties/solidProperties/solidPr
operties.C
index 3c12e9733f..9ae8cd1bc9 100644
--- a/src/thermophysicalModels/thermophysicalProperties/solidProperties/solidProperties/solidProperties.C
+++ b/src/thermophysicalModels/thermophysicalProperties/solidProperties/solidProperties/solidProperties.C
@@ -77,7 +77,7 @@ void Foam::solidProperties::readIfPresent(const dictionary& dict)
dict.readIfPresent("rho", rho_);
dict.readIfPresent("Cp", Cp_);
dict.readIfPresentCompat("kappa", {{"K", 1612}}, kappa_);
- dict.readIfPresent("Hf_", Hf_);
+ dict.readIfPresent("Hf", Hf_);
dict.readIfPresent("emissivity", emissivity_);
dict.readIfPresent("W", W_);
}
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1926Paraview_plugins compilation error2020-11-19T03:22:19ZRamkumarParaview_plugins compilation errorHi,
recently i was trying to compile OpenFOAM v2006 with paraview. I am successful on compilation of OpenFOAM and Paraview on my machine.. now when i try to compile the paraview_plugins, i am getting following error
`
/usr/bin/ld: canno...Hi,
recently i was trying to compile OpenFOAM v2006 with paraview. I am successful on compilation of OpenFOAM and Paraview on my machine.. now when i try to compile the paraview_plugins, i am getting following error
`
/usr/bin/ld: cannot find -lvtkPVFoamCommon-pv5.6
/usr/bin/ld: cannot find -lvtkPVFoamReader-pv5.6
collect2: error: ld returned 1 exit status
CMakeFiles/ParaFoamReader.dir/build.make:452: recipe for target 'libParaFoamReader.so' failed
make[2]: *** [libParaFoamReader.so] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/ParaFoamReader.dir/all' failed
make[1]: *** [CMakeFiles/ParaFoamReader.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2
WARNING: incomplete build of ParaView plugin: foamReader
`
i tried many times but i am getting this error continuously..this occurs not only for foamReader, but also for all the plugins for paraview.. i tried many suggesstions online but nothing worked, hence i am posting in here.. i have attached the log of compilation of paraview_plugins here with.
thanks
[log.linux64GccDPInt32Opt](/uploads/e81cec764db5a0fbb8ec7c13fc708b8b/log.linux64GccDPInt32Opt)https://develop.openfoam.com/Development/openfoam/-/issues/1923snappyHexMesh does not inherit patch/zone info from remote patch faces2021-07-07T10:40:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh does not inherit patch/zone info from remote patch faces<!--
*** 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
You can see how your report will be re...<!--
*** 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
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
snappyHexMesh when adding layers checks the surrounding faces for patch/zone information. It does not check any remote-but-edge-connected faces. This occasionally shows up when patches stop at the processor interface.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Run attached case in v1912 and see the difference between non-parallel and parallel extrusion.
The case has been specifically set up to have the layer-extrusion end coincide with the processor interface.
### 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 : v1912Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1922User-coded BC for uniformFixedValue2021-12-03T15:42:55ZCarlos Peña-MonferrerUser-coded BC for uniformFixedValue`uniformFixedValue` allows options such as `table`, `tableFile`, `csvFile` or `polynomial`. Is there any supported way for accessing and manipulating these values from a user-coded BC like `codedFixedValue`?
Thank you.`uniformFixedValue` allows options such as `table`, `tableFile`, `csvFile` or `polynomial`. Is there any supported way for accessing and manipulating these values from a user-coded BC like `codedFixedValue`?
Thank you.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1921Use "names" for sampled items2020-11-19T15:13:26ZMark OLESENUse "names" for sampled itemsAs a comment raised on EP1415, if we support sampling on faceZones and patches we have a naming discrepancy between sampling and surfaceFieldValue.
In surfaceFieldValue we select the type (patch/zone/surface etc) and use "names" to spec...As a comment raised on EP1415, if we support sampling on faceZones and patches we have a naming discrepancy between sampling and surfaceFieldValue.
In surfaceFieldValue we select the type (patch/zone/surface etc) and use "names" to specify the selection. For sampledPatch, we specify the type (Eg, type patch), but there we use "patches" to specify the selection instead of "names". If we add faceZones into the mix, we then have "zones" as well.
@Prashant figured that going with "patches" and "zones" might be better. I'm not so sure at the moment.
Currently tending towards "names" for both with a silent compatibility handling of "patches".Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1920Issue with SRFSimpleFoam2020-12-18T15:52:52ZLorenzo CozziIssue with SRFSimpleFoamDear developers,
I am running a benchmark OpenFOAM case to compare its results with a reference run performed with Starccm+, adopting the same polyhedral mesh. The steady-state case involves the impeller of a centrifugal pump and the me...Dear developers,
I am running a benchmark OpenFOAM case to compare its results with a reference run performed with Starccm+, adopting the same polyhedral mesh. The steady-state case involves the impeller of a centrifugal pump and the mesh includes just one blade and conformal periodicity surfaces. Boundary conditions have been imposed to be coherent with the ones of Starccm+. The solver adopted is SRFSimpleFoam.
The problem is that the case seems to converge in less that 3000 steps, but the results that I get are totally surrealistic. Just to give you an idea, the pump is predicted to work as a turbine with static pressure reducing its value moving downstream in the meridional flow-path. Also the pressure field has a range spanning from really low to really high values.
I tried several settings in terms of fvSchemes and fvSolution without any improvement.
As I am not sure what is the exact issue afflicting the run (cyclicAMI, SRF model, etc.), I have uploaded all the case on Dropbox, you can find the link here: [link](https://www.dropbox.com/s/pb2vst6nvzolj10/impellerSRFSimpleFoam_SHARE.tar?dl=0)
I hope you can find a way to fix the solver behavior for this case,
thanks in advance.
Lorenzohttps://develop.openfoam.com/Development/openfoam/-/issues/1919gap refinement /proximity refinement: snappyHexMesh tutorial fails in windows2020-11-17T12:49:52ZPawan Ghildiyalgap refinement /proximity refinement: snappyHexMesh tutorial fails in windowsEP:1434EP:1434Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1916Testcases with Reacting Parcels Fail ('constantVolume' or 'volumeUpdateMethod...2020-11-10T17:34:34ZThorsten ZirwesTestcases with Reacting Parcels Fail ('constantVolume' or 'volumeUpdateMethod' must be provided)In the current develop branch (1d544540), many tutorial cases with reacting parcels fail. For example:
```
cd $FOAM_TUTORIALS/combustion/fireFoam/LES/smallPoolFire2D/
./Allrun
```
or
```
cd /work/fh2-project-devel/np4075/commit_Bilge...In the current develop branch (1d544540), many tutorial cases with reacting parcels fail. For example:
```
cd $FOAM_TUTORIALS/combustion/fireFoam/LES/smallPoolFire2D/
./Allrun
```
or
```
cd /work/fh2-project-devel/np4075/commit_Bilger_2006/openfoam-com/tutorials/lagrangian/reactingParcelFoam/counterFlowFlame2DLTS/
blockMesh
reactingParcelFoam
```
will both yield
```
--> FOAM FATAL ERROR: (openfoam-2010 patch=201012)
Either 'constantVolume' or 'volumeUpdateMethod'
must be provided.
The new keyword is 'volumeUpdateMethod'.
Available methods are :
constantRho, constantVolume or updateRhoAndVol.
'constantVolume' is either true/false
```
Adding the following entry in `constant/reactingCloud1Properties` fixes the problem.
```
constantProperties
{
constantVolume true;
}
```
In version v2006, the cases work fine. The problem seems to originate from commit 11d17fec5f, more specifically here:
https://develop.openfoam.com/Development/openfoam/-/blob/develop/src/lagrangian/intermediate/parcels/Templates/ReactingParcel/ReactingParcelI.H#L73
The constructor of constantProperties always requires a value to be specified, regardless if the particles are active or not.https://develop.openfoam.com/Development/openfoam/-/issues/1914Loading the OpenFOAM bashrc by default makes the Ubuntu 20.10 desktop unale t...2024-01-09T12:16:04ZGerasimos ChourdakisLoading the OpenFOAM bashrc by default makes the Ubuntu 20.10 desktop unale to load (X11-only)I stumbled upon a very weird issue that I can consistently reproduce on the same system. After installing OpenFOAM v2006 on Ubuntu 20.10 (see #1902) and adding `source "/usr/lib/openfoam/openfoam2006/etc/bashrc"` to my `~/.bashrc`, my de...I stumbled upon a very weird issue that I can consistently reproduce on the same system. After installing OpenFOAM v2006 on Ubuntu 20.10 (see #1902) and adding `source "/usr/lib/openfoam/openfoam2006/etc/bashrc"` to my `~/.bashrc`, my desktop fails to launch in X11, while it loads normally on Wayland.
There is no error, the system simply returns to the login screen after a few seconds. Removing this line from my `~/.bashrc` or making it an alias (so that I load it on demand) fixes the issue.
Any clue why this could happening? Can you reproduce it?https://develop.openfoam.com/Development/openfoam/-/issues/1913SolidificationMeltingSource acts different on 2D and 3D2020-11-13T10:41:39ZEren ColakSolidificationMeltingSource acts different on 2D and 3D<!--
*** Please read this first! ***
B[SolidMeltSource.7z](/uploads/dab9f2ec6ea41b67fd1a825073253679/SolidMeltSource.7z)
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summar...<!--
*** Please read this first! ***
B[SolidMeltSource.7z](/uploads/dab9f2ec6ea41b67fd1a825073253679/SolidMeltSource.7z)
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
SolidificationMeltingSource gives different results with 2D and 3D solutions. While 3D solution gives accurate results there is no change in the z direction(3rd direction). So it makes no sense and increases the computational time up to 10 times.
### Steps to reproduce
just run buoyantPimpleFoam for test cases I sent. Files also contains some of the results.
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
### What is the current *bug* behaviour?
Somehow "Benard Cells" appears in 2D case and it changes melting front drastically.
### What is the expected *correct* behavior?
There should be no "Benard Cells" so melting front will be like 3D case I attached.
### 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
- OpenFOAM version : v2002
- Operating system : ubuntu 18.04
- Hardware info : ryzen 5 3600
- Compiler : gcc
### Possible fixes
I have no idea about this.[SolidMeltSource.7z](/uploads/bcf207105fb5bded154a3552c4cb5fc8/SolidMeltSource.7z)https://develop.openfoam.com/Development/openfoam/-/issues/1912Compiling OpenFOAM v.20062020-11-10T12:10:41ZTasman Van LoonCompiling OpenFOAM v.2006Hi there, I'm trying to compile OpenFOAM v.2006 and have followed the instructions as per this webpage:
https://develop.openfoam.com/Development/openfoam/blob/develop/doc/Build.md
There are no issues with the foamSystemCheck. But when I...Hi there, I'm trying to compile OpenFOAM v.2006 and have followed the instructions as per this webpage:
https://develop.openfoam.com/Development/openfoam/blob/develop/doc/Build.md
There are no issues with the foamSystemCheck. But when I go to execute the ./Allwmake command, there is an error message (which I have attached).
Any advice would be appreciated!
Kind regards,
Tasman. ![Screen_Shot_2020-11-05_at_11.04.27_pm](/uploads/60136129f5c4821f4a97e5281f02c7b7/Screen_Shot_2020-11-05_at_11.04.27_pm.png)https://develop.openfoam.com/Development/openfoam/-/issues/1911update config for newer ADIOS2 library names2020-12-24T10:27:54ZMark OLESENupdate config for newer ADIOS2 library namesMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1907PDRsetFields fails with non-orthogonal outer region2020-11-17T12:06:53ZMark OLESENPDRsetFields fails with non-orthogonal outer regionnoticed while testing #1906noticed while testing #1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1904CentOS precompiled packages don't include scotch2024-01-10T11:27:31ZCristóbal TapiaCentOS precompiled packages don't include scotchHi,
I installed OpenFOAM v2006 with the instructions provided for CentOS in [1]. However, the `decomposePar` command is not working and gives the following error:
```
--> FOAM FATAL ERROR:
Attempted to use <scotch> without the scotchDe...Hi,
I installed OpenFOAM v2006 with the instructions provided for CentOS in [1]. However, the `decomposePar` command is not working and gives the following error:
```
--> FOAM FATAL ERROR:
Attempted to use <scotch> without the scotchDecomp library loaded.
This message is from the dummy scotchDecomp stub library instead.
Please install <scotch> and ensure libscotch.so is in LD_LIBRARY_PATH.
The scotchDecomp library can then be built from src/parallel/decompose/scotchDecomp.
Dynamically loading or linking this library will add <scotch> as a decomposition method.
```
Scotch is installed in the system, but I suppose that there is something else missing. Does this has to do with the "Third-Party" builds (not included in the packages?).
[1] https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/redhathttps://develop.openfoam.com/Development/openfoam/-/issues/1903orientation information in blockMesh VTK output2020-10-29T08:14:21ZMark OLESENorientation information in blockMesh VTK outputcomment raised via linkedIn, where the person seemed to have incorrectly oriented their blocks and was very confused that the three grid parameters did not correspond to global x/y/z.
Fairly easy to extract this information from the blo...comment raised via linkedIn, where the person seemed to have incorrectly oriented their blocks and was very confused that the three grid parameters did not correspond to global x/y/z.
Fairly easy to extract this information from the blocks and save as fields with `-write-vtk`.
![orientation](/uploads/759c7227a15fb40833040c5f0f2a00c5/orientation.png)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1902Missing Debian packages for Ubuntu 20.10 (groovy)2021-05-04T10:02:53ZGerasimos ChourdakisMissing Debian packages for Ubuntu 20.10 (groovy)### Functionality to add/problem to solve
Binary packages for Ubuntu 20.10 Groovy Gorilla (published on October 22, 2020), next to the current offers for the LTS versions.
### Target audience
Me (:sweat_smile:) and anyone else on the ...### Functionality to add/problem to solve
Binary packages for Ubuntu 20.10 Groovy Gorilla (published on October 22, 2020), next to the current offers for the LTS versions.
### Target audience
Me (:sweat_smile:) and anyone else on the non-LTS Ubuntu (& co.) cycle.
### Proposal
I guess there is a pipeline in place for this, so I though I would nudge the keyholder to trigger it. If there is a way I can help (with some guidance), I would be happy to.
This should be done ince every six months. Next expected dates: April 22, 2021 and October 14, 2021. It is perfectly fine to create the packages even earlier (e.g. with the first beta or RC), usually not much changes after these points.
### What does success look like, and how can we measure that?
A `dists/groovy` on the [official repositories](https://dl.openfoam.com/repos/deb/).
### Links / references
- [Ubuntu 20.10 release notes](https://discourse.ubuntu.com/t/groovy-gorilla-release-notes/15533)
- [Ubuntu releases schedule](https://wiki.ubuntu.com/Releases)
### Funding
None.https://develop.openfoam.com/Development/openfoam/-/issues/1901Add searchable spheroid2020-10-29T08:14:54ZMark OLESENAdd searchable spheroidThis is an idea that I discussed offline with @Mattijs. Having spheroid as a shape could be useful for external surroundings etc. Found some ideas, but equally importantly I have someone willing to implement it (@victorOle). The first ef...This is an idea that I discussed offline with @Mattijs. Having spheroid as a shape could be useful for external surroundings etc. Found some ideas, but equally importantly I have someone willing to implement it (@victorOle). The first efforts look good, but would likely make most sense to merge into searchableSphere and treat the uniform radii as a special optimized case.
Largely able to work from [Geometric Tools](https://www.geometrictools.com/Documentation/DistancePointEllipseEllipsoid.pdf) documentation (CC-BY 4.0), but needs rework for the OpenFOAM frameworkMark OLESENMark OLESEN