Development issueshttps://develop.openfoam.com/groups/Development/-/issues2024-01-05T17:05:08Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1567searchableExtrudedCircle / extrudedCircle uses wrong search sphere2024-01-05T17:05:08ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsearchableExtrudedCircle / extrudedCircle uses wrong search sphere<!--
*** 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 ...<!--
*** 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 -->
The analytical shape 'extrudedCircle' does not interpret the search distance correctly. It is taken as the distance to the centre line instead of the distance to the cylinder itself.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Use in e.g. a snappyHexMeshDict. Set the snapping distance (`snapTol`) to e.g. 1. Make sure that the centre line is more than 1 edge distance away from the geometry. Now it will not be attracted to the extrusion, even when the extrusion itself might intersect the geometry.
### 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?
<!-- What actually happens -->
### What is the expected *correct* behavior?
<!-- What you should see instead -->
Re-work the search distance into distance-to-extrusion
@PrashantMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1772snappyHexMesh creates disconnected regions2024-01-05T17:03:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh creates disconnected regions### Functionality to add/problem to solve
snappyHexMesh is sometimes used to create multiple regions which later on get 'connected' through e.g. cyclicAMI. This does make it impossible to detect what is a properly resolved region and wh...### Functionality to add/problem to solve
snappyHexMesh is sometimes used to create multiple regions which later on get 'connected' through e.g. cyclicAMI. This does make it impossible to detect what is a properly resolved region and what is just a dangling few cells.
### Target audience
Cases with faceZones that are intersecting the geometry.
### Proposal
For now have option to remove small regions. This should be expressed as a fraction of 'main' region for a given zone.
@PrashantMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1836snappyHexMesh does not handle nBufferCellsNoExtrude -12024-01-05T17:00:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh does not handle nBufferCellsNoExtrude -1<!--
*** 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 does not handle nBufferCellsNoExtrude -1 correctly. It only handles the case if completely truncating the layers i.e. going to 0.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Run attached case.
### What is the current *bug* behaviour?
Code crashes. Number of extruded cells per face should be <= number of extruded points per point
### 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 : develop and older
[block.tgz](/uploads/05ddbb5d78e231947bd35bec9c8ddaad/block.tgz)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1937redistributePar produces illogical warning message2024-01-05T16:59:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar produces illogical warning message<!--
*** 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 -->
redistributePar uses internally fvMeshSubset to subset mesh+fields to send to other processors. Exposed internal faces will produce a warning for any boundary condition holding per-face information (e.g. fixedValue v.s. uniformFixedValue).
Since the bits will get stitched later on there is actually no use for the warning message - it is just due to the current implementation.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Eg in `tutorials/incompressible/simpleFoam/pitzDaily` :
```
mpirun -np 2 redistributePar -decompose -parallel
```
This will give a warning:
```
--> FOAM Warning :
From Foam::fixedValueFvPatchField<Type>::fixedValueFvPatchField(const Foam::fixedValueFvPatchField<Type>&, const Foam::fvPatch&, const Foam::DimensionedField<Type, Foam::volMesh>&, const Foam::fvPatchFieldMapper&) [with Type = double]
in file src/finiteVolume/lnInclude/fixedValueFvPatchField.C at line 81
On field subsetepsilon patch lowerWall patchField fixedValue : mapper does not map all values.
To avoid this warning fully specify the mapping in derived patch fields.
```
### 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 : <= v2006Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2032faMesh does not have own registry2024-01-05T16:57:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfaMesh does not have own registry### Functionality to add/problem to solve
faMesh does not have its own objectRegistry but uses the polyMesh one. This means e.g. that its data() conflicts with that of a fvMesh.
### What does success look like, and how can we measure t...### Functionality to add/problem to solve
faMesh does not have its own objectRegistry but uses the polyMesh one. This means e.g. that its data() conflicts with that of a fvMesh.
### What does success look like, and how can we measure that?
Successfully run any finiteArea case with
```
DebugSwitches
{
regIOobject 2;
}
```
(this debugswitch will trigger aborting upon double registration)https://develop.openfoam.com/Development/openfoam/-/issues/2072checkMesh does not handle -allRegions2024-01-05T16:57:07ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh does not handle -allRegions### Functionality to add/problem to solve
decomposePar has a `-allRegions` argument. Nice to have on e.g. `checkMesh`.### Functionality to add/problem to solve
decomposePar has a `-allRegions` argument. Nice to have on e.g. `checkMesh`.https://develop.openfoam.com/Development/openfoam/-/issues/2092redistributePar does not always detect whether reconstruction is needed2024-01-05T16:55:06ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar does not always detect whether reconstruction is needed### Functionality to add/problem to solve
redistributePar does not always decide to reconstruct mesh correctly
- run `redistributePar` with -decompose (or decomposePar)
- remove constant/polyMesh (but not processorXXX/constant/polyMesh...### Functionality to add/problem to solve
redistributePar does not always decide to reconstruct mesh correctly
- run `redistributePar` with -decompose (or decomposePar)
- remove constant/polyMesh (but not processorXXX/constant/polyMesh/*addressing)
- now redistributePar still thinks it has an undecomposed mesh (since above *addressing still exists)
### Target audience
Cleanup scripts that don't delete addressing
### Proposal
Add some more checks
(EP 1573) @Prashant @markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2583viewFactorsGen S2S radiation can cause divide by zero2024-01-05T16:47:48ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comviewFactorsGen S2S radiation can cause divide by zero<!--
*** 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 -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
### 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?
<!-- 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 : v2206|v2112|v2106|v2012|v2006 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2212
- Operating system :
- Hardware info :
- Compiler :
### 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
-->https://develop.openfoam.com/Development/openfoam/-/issues/3000Missing support for postProcess mode2024-01-05T15:58:54ZPrashant SonakarMissing support for postProcess modeadjointOptimisationFoam is missing support for -postProcess mode
Cross ref : EP#2249
@andyadjointOptimisationFoam is missing support for -postProcess mode
Cross ref : EP#2249
@andyhttps://develop.openfoam.com/Development/openfoam/-/issues/2985cellVolumeWeight incorrect debug info2024-01-05T15:55:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcellVolumeWeight incorrect debug info<!--
*** 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 -->
Switching on debug information for cellVolumeWeight causes out-of-bounds on cell-type counting
### What is the current *bug* behaviour?
<!-- What actually happens -->
cellTypes are 5 possible options since v2212.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2306|v2212|v2206|v2112|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2306
### 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
-->
Correct sizing.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2732An error occurred with the reconstructPar command2024-01-04T10:57:34Zliu haoAn error occurred with the reconstructPar command<!--
*** 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
An error occurred when executing the reconstructPar command with parallel computation
### Steps to reproduce
Run the example case
### 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
-->
Use Case From [https://turbmodels.larc.nasa.gov/naca0012_val.html](url) and https://github.com/tomrobin-teschner/OpenFOAMCaseGenerator [](url)
[Naca0012_number_of_processors_2_number_of_corrector_steps_3.zip](/uploads/174a417be398fc0c7f7af5d1ac8084fb/Naca0012_number_of_processors_2_number_of_corrector_steps_3.zip)
### 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.
-->
```
Reconstructing fields
region=region0
Time = 0.01
Reconstructing FV fields
Reconstructing volScalarFields
cp
--> FOAM FATAL IO ERROR: (openfoam-2206)
size 110 is not equal to the expected length 64
file: processor0/0.01/cp.boundaryField.farfield at line 7214 to 7215.
From Foam::Field<Type>::Field(const Foam::word&, const Foam::dictionary&, Foam::label) [with Type = double; Foam::label = int]
in file ./src/OpenFOAM/lnInclude/Field.C at line 218.
FOAM exiting
```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version :v2206
- Operating system :windows
- Hardware info :N/A
- Compiler :gcc(Ubuntu on WSL)https://develop.openfoam.com/Development/openfoam/-/issues/2736dynamicMesh failure restarting using CrankNicholson2024-01-04T10:56:23ZJamie MacLeoddynamicMesh failure restarting using CrankNicholson<!--
*** 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 -->
When restarting a case using dynamic meshing the first step fails with an error:
```
--> FOAM FATAL IO ERROR: (openfoam-2212 patch=230110)
size 77961 is not equal to the expected length 78325
file: 0.002/ddt0(rho,U).internalField at line 21.
From void Foam::Field<Type>::assign(const Foam::entry&, Foam::label) [with Type = Foam::Vector<double>; Foam::label = int]
in file ./src/OpenFOAM/lnInclude/Field.C at line 241.
FOAM exiting
```
This occurs regardless of whether dynamicMeshDict is altered or not (it may work sometimes if it is set to not refine every step, and happens to not align with the restart step, as previous tests have found that it works this way).
Almost certainly this associated with the 2nd order time scheme (which I would certainly strongly prefer to use), as Euler has no issues with the restart vs CN.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Run attached case until a new time, in this instance 0.002, and then try to restart.
### 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
-->
[dynMfail.zip](/uploads/384f0ef04572001fa268baf4d8ffcea3/dynMfail.zip)
### What is the current *bug* behaviour?
<!-- What actually happens -->
Restarting when using dynamic meshing fails with size error when using Crank Nicholson timeScheme.
### What is the expected *correct* behavior?
<!-- What you should see instead -->
The simulation restarts as a normal timestep would.
### 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 : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
```
Build : _c9081d5d-20230220 OPENFOAM=2212 patch=230110 version=2212
Arch : "LSB;label=32;scalar=64"
Exec : interFoam1
```
- Operating system : WSL Ubuntu 22.04
- Hardware info : Tested on Ryzen 5 2600 and Intel X chip
- Compiler : gcc?https://develop.openfoam.com/Development/openfoam/-/issues/2733XiFoam tutorial moriyoshiHomogeneous fails with sigfpe2024-01-04T10:07:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comXiFoam tutorial moriyoshiHomogeneous fails with sigfpe<!--
*** 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 -->
combustion/XiFoam/RAS/moriyoshiHomogeneous tutorial does not run
### Steps to reproduce
cd combustion/XiFoam/RAS/moriyoshiHomogeneous
foamRunTutorials
### 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
-->
See above
### What is the current *bug* behaviour?
<!-- What actually happens -->
sigfpe when obtaining `psiu()` in the first iteration.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2212https://develop.openfoam.com/Development/openfoam/-/issues/2700coincidentBaffleInteraction missing from the source code (but present in the ...2024-01-04T09:46:28ZFranz DcoincidentBaffleInteraction missing from the source code (but present in the documentation?)In the files multiInteraction.C and multiInteraction.H, there is some reference to a feature / keyword "coincidentBaffleInteraction". While it is documented, it seems that the feature has not been implemented and the keyword is not worki...In the files multiInteraction.C and multiInteraction.H, there is some reference to a feature / keyword "coincidentBaffleInteraction". While it is documented, it seems that the feature has not been implemented and the keyword is not working.
Seems to be a long-standing issue:
https://bugs.openfoam.org/view.php?id=2939
https://www.cfd-online.com/Forums/openfoam-solving/141571-cyclic-boundary-conditions-particles.htmlAndrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/2938bash: cannot set terminal process group (-1): Inappropriate ioctl for device2024-01-04T07:29:53ZGeon-Hongbash: cannot set terminal process group (-1): Inappropriate ioctl for deviceHi,
I'm not sure if it is appropriate to raise docker issue here, but I need your help.
Recently I tried to run OpenFOAM on Windows by following the instruction described here: https://develop.openfoam.com/Development/openfoam/-/wikis/...Hi,
I'm not sure if it is appropriate to raise docker issue here, but I need your help.
Recently I tried to run OpenFOAM on Windows by following the instruction described here: https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/windows
I installed WSL and docker on a Windows system and run the OpenFOAM-default image on it.
But when I run the image, I faced the following error message and the status of the container turned to exited.
```
---------------------------------------------------------------------------
========= |
\\ / F ield | OpenFOAM in a container [from OpenCFD Ltd.]
\\ / O peration |
\\ / A nd | www.openfoam.com
\\/ M anipulation |
---------------------------------------------------------------------------
Release notes: https://www.openfoam.com/news/main-news/openfoam-v2306
Documentation: https://www.openfoam.com/documentation/
Issue Tracker: https://develop.openfoam.com/Development/openfoam/issues/
Local Help: more /openfoam/README
---------------------------------------------------------------------------
System : Ubuntu 22.04.2 LTS (admin user: sudofoam)
OpenFOAM : /usr/lib/openfoam/openfoam2306
Build : _fbf00d6b-20230626 OPENFOAM=2306 patch=0
Note
Different OpenFOAM components and modules may be present (or missing)
on any particular container installation.
Eg, source code, tutorials, in-situ visualization, paraview plugins,
external linear-solver interfaces etc.
---------------------------------------------------------------------------
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
root@399e74dd484f:~# exit
```
I set the WSL distro to be Ubuntu but it doesn't help for me.
How can I handle this problem?
Many thanks in advance.
Regards,
Geon-Hong.https://develop.openfoam.com/Development/openfoam/-/issues/3073coincidentBaffleInteraction2024-01-03T17:13:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcoincidentBaffleInteractionhttps://develop.openfoam.com/Development/openfoam/-/issues/3006Cannot run analysis parallel by using MinGW with OpenFOAM v23062024-01-03T14:52:43ZQuang NguyenCannot run analysis parallel by using MinGW with OpenFOAM v2306When I try to run analysis by using MinGW OpenFOAM v2306 with parallel option, I got this error. I don't know if anyone has the same error and if there is any way to solve it?
I run with command: mpirun -np 2 rhoSimpleFoam -parallel.
T...When I try to run analysis by using MinGW OpenFOAM v2306 with parallel option, I got this error. I don't know if anyone has the same error and if there is any way to solve it?
I run with command: mpirun -np 2 rhoSimpleFoam -parallel.
Thank you very much for any support.
![analysis_parallel_error](/uploads/38496cabb95551473c1178279aa59dd2/analysis_parallel_error.png)Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/2468potentialFoam creates unphysical velocity field in motorBike tutorial2024-01-03T14:12:44ZAaron EndrespotentialFoam creates unphysical velocity field in motorBike tutorial<!--
*** 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 -->
In OpenFOAM v2112, potentialFoam creates an unphysical velocity field.
This ultimately leads to the crash of the simulation.
In OpenFOAM v2012, this issue was not present.
Tested in serial as well as in parallel execution, on different Linux versions and on different hardware.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Copy the motorBike tutorial case, execute the Allrun script, look at the 0/U field in paraview.
### 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
-->
motorBike tutorial
### What is the current *bug* behaviour?
<!-- What actually happens -->
in v2112:
![OFv2112](/uploads/83f9006c88e31921c62fb20a6c6f39a8/OFv2112.png)
### What is the expected *correct* behavior?
<!-- What you should see instead -->
in v2012:
![OFv2012](/uploads/039e4b8f08c31fb2cb2423be6f4713a1/OFv2012.png)
### 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 : v2112|v2106|v2012|v2006|v1912|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2112: latest stable release and dev version 'patch = 220310, build = f8dc192941-20220507'
- Operating system : ArchLinux and OpenSUSE Tumbleweed
- Hardware info : AMD EPYC 7452 and Intel Xeon CPU E5-2650
- Compiler : gcc
### 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
-->Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2434Issue when Executing Simulation in Parallel2024-01-03T14:11:37ZTamas EgeresiIssue when Executing Simulation in Parallel### Summary
Recently I updated my system to Ubuntu 21.10. Then I installed the pre-compiled OpenFOAM v2112 based on the information on the webpage. When I started any case from the tutorials in parallel mode, it diverged rapidly. I've a...### Summary
Recently I updated my system to Ubuntu 21.10. Then I installed the pre-compiled OpenFOAM v2112 based on the information on the webpage. When I started any case from the tutorials in parallel mode, it diverged rapidly. I've attached the log.simpleFoam from the motorBike case.
In order to overcome of this problem, I changed maxThreadFileBufferSize from 0 to 1e9 in the global controlDict. The motorBike case went smoothly after this.
However, the more complex solvers such as compressibleInterDyMFoam in the sphereDrop setup or the DTCHullMoving setup diverged immediately no matter how I set maxThreadFileBufferSize. I also attached those 2 log files (log.compressibleInterDyMFoam and log.interFoam).
To reproduce this behavior, use Ubuntu 21.10 with motorBike or sphereDrop tutorial. You can check that maxThreadFileBufferSize is set to 0 in $FOAM_ETC/controlDict initially.
### Relevant logs and/or images
[log.simpleFoam](/uploads/c1c36b5cf2e8bb78743226b28302f2ea/log.simpleFoam)
[log.compressibleInterDyMFoam](/uploads/728a1b88dc28519ba6b8aafae4bf5f3c/log.compressibleInterDyMFoam)
[log.interFoam](/uploads/e456021e437ad5f5c1f5d27c8de5dcfd/log.interFoam)
### Environment information
OpenFOAM version : v2112
Operating system : ubuntu 21.10
Hardware info : Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz
Compiler : gcc
- OpenFOAM version : v2112
- Operating system : ubuntu 21.10
- Hardware info : Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz
- Compiler : gcc
### Possible fixes
Partially fixing: I changed maxThreadFileBufferSize from 0 to 1e9 which fixed 1 of the 3 cases.https://develop.openfoam.com/Development/openfoam/-/issues/2812GAMG with cyclicAMI and mergeLevels > 1 crashes in parallel2024-01-03T13:43:58ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comGAMG with cyclicAMI and mergeLevels > 1 crashes in parallel<!--
*** 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 -->
With merging multiple levels of pairwise agglomeration crashes when using cyclicAMI.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
In incompressible `mixerVesselAMI2D` tutorial add `mergeLevels` to `fvSolution`
```
"pcorr.*"
{
solver GAMG;
smoother GaussSeidel;
..
mergeLevels 2;
..
}
```
### 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.
-->
on above tutorial on 4 procs:
```
[2] #1 Foam::sigSegv::sigHandler(int)[1] #1 Foam::sigSegv::sigHandler(int) in ~/OpenFOAM/OpenFOAM-plus/work/develop/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so
[2] #2 ? in ~/OpenFOAM/OpenFOAM-plus/work/develop/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so
[1] #2 ? in /lib64/libpthread.so.0
[2] #3 virtual thunk to Foam::cyclicAMIGAMGInterface::neighbPatchID() const in /lib64/libpthread.so.0
[1] #3 virtual thunk to Foam::cyclicAMIGAMGInterface::neighbPatchID() const in ~/OpenFOAM/OpenFOAM-plus/work/develop/platforms/linux64GccDPInt32Opt/lib/libmeshTools.so
[2] #4 Foam::cyclicAMIGAMGInterface::internalFieldTransfer(Foam::UPstream::commsTypes, Foam::UList<int> const&) const in ~/OpenFOAM/OpenFOAM-plus/work/develop/platforms/linux64GccDPInt32Opt/lib/libmeshTools.so
[1] #4 Foam::cyclicAMIGAMGInterface::internalFieldTransfer(Foam::UPstream::commsTypes, Foam::UList<int> const&) const in ~/OpenFOAM/OpenFOAM-plus/work/develop/platforms/linux64GccDPInt32Opt/lib/libmeshTools.so
```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2212
- Operating system :
- Hardware info :
- Compiler :
### 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
-->Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com