Development issueshttps://develop.openfoam.com/groups/Development/-/issues2024-01-03T14:11:37Zhttps://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/2433issue with compiling runTimePostprocessing:2022-04-30T14:49:01ZPawan Ghildiyalissue with compiling runTimePostprocessing:Hi @mark
Operating system: Redhat7.9
I compiled VTK-9.2 from Paraview as shipped with ThirdParty/sources/Paraview-5.10.0.
with mesa+llvm successfully.
`./makeVTK -mpi=0 -osmesa -mesa-prefix /home/pawan/OpenFOAM/OpenFOAM-v2112/Thi...Hi @mark
Operating system: Redhat7.9
I compiled VTK-9.2 from Paraview as shipped with ThirdParty/sources/Paraview-5.10.0.
with mesa+llvm successfully.
`./makeVTK -mpi=0 -osmesa -mesa-prefix /home/pawan/OpenFOAM/OpenFOAM-v2112/ThirdParty/platforms/linux64Gcc/mesa-17.1.1`
However while compiling the runTimePostProcessing, it fail ![Untitled](/uploads/ec2ccd42f2c1139416de84e9f2a74646/Untitled.png)https://develop.openfoam.com/Development/openfoam/-/issues/2432Parallel simulation diverges always2022-03-31T19:14:05ZTamas EgeresiParallel simulation diverges alwaysDear Support,
All of my parallel cases diverges when running them on my workstation. I've tested all of the available OpenFOAM.com OpenFOAM versions, and all of them gives the same problem. Hovewer, when I run the OpenFOAM.org OpenFOAM ...Dear Support,
All of my parallel cases diverges when running them on my workstation. I've tested all of the available OpenFOAM.com OpenFOAM versions, and all of them gives the same problem. Hovewer, when I run the OpenFOAM.org OpenFOAM version 9, it goes without any problem.
My system is:
LSB Version: core-11.1.0ubuntu3-noarch:security-11.1.0ubuntu3-noarch
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish
I've attached my log file for the motorBike test case.
[log.simpleFoam](/uploads/be3b40d4632233e19212b1f61bab6a09/log.simpleFoam)https://develop.openfoam.com/Development/openfoam/-/issues/2430missing weights in Cuthill-McKee2022-04-01T09:11:39ZMark OLESENmissing weights in Cuthill-McKee- by inspection, and description. The neighbour order is not actually weighted by connectivity at all.
- partial duplicate of #1376- by inspection, and description. The neighbour order is not actually weighted by connectivity at all.
- partial duplicate of #1376Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2426lagrangian/reactingParcelFoam/verticalChannelLTS Failing in v21122022-05-06T10:03:42ZPrashant Sonakarlagrangian/reactingParcelFoam/verticalChannelLTS Failing in v2112Tutorial runs fine if we change:
- constant/thermo.incompressiblePoly -> Hf and Sf to 0 for H20
- constant/reactingCloud1Properties -> liquidEvaporationCoeffs -> enthalpyTransfer latentHeat;
@Sergio Could you please review if this is r...Tutorial runs fine if we change:
- constant/thermo.incompressiblePoly -> Hf and Sf to 0 for H20
- constant/reactingCloud1Properties -> liquidEvaporationCoeffs -> enthalpyTransfer latentHeat;
@Sergio Could you please review if this is required?https://develop.openfoam.com/Development/openfoam/-/issues/2425BUG: blendingFactor FO overwrites DEShybrid:Factor2022-05-06T10:00:44ZKutalmış BerçinBUG: blendingFactor FO overwrites DEShybrid:Factor### Summary
The `blendingFactor` FO overwrites the `DEShybrid:Factor` field, which was written by enabling the debug switch `blendedSchemeBase`.
### Example case
With the `periodicHill` tutorial, test the following with and without t...### Summary
The `blendingFactor` FO overwrites the `DEShybrid:Factor` field, which was written by enabling the debug switch `blendedSchemeBase`.
### Example case
With the `periodicHill` tutorial, test the following with and without the `blendingFactorFO`, and compare `DEShybrid:Factor` fields elementwise:
```
DebugSwitches
{
blendedSchemeBase 1;
}
functions
{
blendingFactorFO
{
// Mandatory entries
type blendingFactor;
libs (fieldFunctionObjects);
field U;
// Optional (inherited) entries
result blendingFactorField;
region region0;
enabled true;
log true;
writeControl writeTime;
}
...
}
### Environment information
HEAD: ea2bf041Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2424linking of twoPhaseProperties missing for windows version2022-04-01T09:12:47ZPrashant Sonakarlinking of twoPhaseProperties missing for windows versioncross reference: EP#1864
On Windows OpenFOAM 2112 version we get error as,
```
--> FOAM FATAL IO ERROR: (openfoam-2112)
Unknown patchField type constantAlphaContactAngle for patch type wall
Valid patchField types :
120
(
```
Could b...cross reference: EP#1864
On Windows OpenFOAM 2112 version we get error as,
```
--> FOAM FATAL IO ERROR: (openfoam-2112)
Unknown patchField type constantAlphaContactAngle for patch type wall
Valid patchField types :
120
(
```
Could be reproduced on tutorials/multiphase/interFoam/laminar/capillaryRise
Workaround:
- Load library by -lib twoPhaseProperties
- or via including it in controlDict
@markhttps://develop.openfoam.com/Development/openfoam/-/issues/2423The dummy Pstream library cannot be used in parallel mode2022-04-05T14:00:29ZSebastian Echeverri RestrepoThe dummy Pstream library cannot be used in parallel modeAfter installing openfoam 2112 on redhat 8.4 following issue https://develop.openfoam.com/Development/openfoam/-/issues/2418 , we get the following error when trying to run openfoam
--> FOAM FATAL ERROR: (openfoam-2112)
The dummy Pstrea...After installing openfoam 2112 on redhat 8.4 following issue https://develop.openfoam.com/Development/openfoam/-/issues/2418 , we get the following error when trying to run openfoam
--> FOAM FATAL ERROR: (openfoam-2112)
The dummy Pstream library cannot be used in parallel mode
From static bool Foam::UPstream::init(int&, char**&, bool)
in file UPstream.C at line 50.FOAM exiting
This fix did not work for us:
https://develop.openfoam.com/Development/openfoam/-/issues/1970
Any suggestions on how to fix the error
Here is the command that gives the error
`mpirun -np 8 snappyHexMesh -overwrite -parallel `
It seems to be related to running in parallel. The serial version works fine:
`snappyHexMesh -overwrite`https://develop.openfoam.com/Development/openfoam/-/issues/2422Something wrong in humidityTemperatureCoupledMixed Boundary2022-05-06T10:12:05ZGonglin LiSomething wrong in humidityTemperatureCoupledMixed Boundary@Sergio
Dear Prof. Sergio,
Recently, I am using humidityTemperatureCoupledMixed Boundary and try to make some modification with different condensation model. However, some part of the code was confusion.
1. The default drop-wise type o...@Sergio
Dear Prof. Sergio,
Recently, I am using humidityTemperatureCoupledMixed Boundary and try to make some modification with different condensation model. However, some part of the code was confusion.
1. The default drop-wise type of condensation was modeled, but the units in the formula should be Celsius and not Kelvin. The attachment is provided in the email for confirmation.
[BERGMAN T L, LAVINE A S. Fundamentals of Heat and Mass Transfer, 8th Edition, 2017,page 632]
![Drop_Cond_Model_in_reference](/uploads/a6ee6cf571c55fd2a09e8ba389a814f3/Drop_Cond_Model_in_reference.png)
2. In lately .C file in [site, ](https://develop.openfoam.com/Development/openfoam/-/blob/OpenFOAM-v2112/src/thermophysicalModels/thermophysicalPropertiesFvPatchFields/liquidProperties/humidityTemperatureCoupledMixed/humidityTemperatureCoupledMixedFvPatchScalarField.C)
the "alpha" in line 740, the "valueFraction" in line 742 and the "refValue" in line 744 are hard to understand. May I get the physical meaning of these variables?
I try to use E-mail to connect the Prof. Sergio, but the email(s.ferraris@opencfd.co.uk) on website was not able to receive. I deeply appreciate your time and consideration for these issues, and any kind of information or instructions can help me a lot.Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2421processorLOD does not handle zero local elements2022-06-28T10:56:15ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprocessorLOD does not handle zero local elements<!--
*** 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 -->
processorLOD does not handle zero local elements. E.g. if processorLODs::faceBox is used to pre-filter patches and the local number of patch faces is zero there is a division by zero.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Attached test case and code.
[processorLOD.tgz](/uploads/caee1abff1305c43fe732fdcdbada890/processorLOD.tgz)
### What is the current *bug* behaviour?
<!-- What actually happens -->
Division by zero
### 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 : v2112Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2419BUG: DEShybrid yields blending-factor fields different than blendingFactor FO2022-05-06T10:03:56ZKutalmış BerçinBUG: DEShybrid yields blending-factor fields different than blendingFactor FO### Summary
Found and explained by @Chiara.
The blending factor fields produced by `DESHybrid` scheme and other schemes + `blendingFactor` function object are opposite to each other. e.g.:
![image](/uploads/c91127f491ed84332852a91963b...### Summary
Found and explained by @Chiara.
The blending factor fields produced by `DESHybrid` scheme and other schemes + `blendingFactor` function object are opposite to each other. e.g.:
![image](/uploads/c91127f491ed84332852a91963b1ad51/image.png)
### Example case
The figure was created from the `periodicHill` tutorial, adding the following to the `controlDict`:
```
DebugSwitches
{
blendedSchemeBase 1;
}
functions
{
blendingFactorFO
{
// Mandatory entries
type blendingFactor;
libs (fieldFunctionObjects);
field U;
// Optional (inherited) entries
result blendingFactorField;
region region0;
enabled true;
log true;
writeControl writeTime;
}
...
}
```
### Environment information
HEAD: ea2bf0414dKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2418Can't install openfoam on redhat 8.42022-03-30T19:34:16ZSebastian Echeverri RestrepoCan't install openfoam on redhat 8.4The installation of openfoam fails on Redhat 8.4. We are following the instructions found here:
https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/redhat
Here is the output
yum -y install dnf-plugins-core
Updating S...The installation of openfoam fails on Redhat 8.4. We are following the instructions found here:
https://develop.openfoam.com/Development/openfoam/-/wikis/precompiled/redhat
Here is the output
yum -y install dnf-plugins-core
Updating Subscription Management repositories.
Last metadata expiration check: 3:33:39 ago on Tue 22 Mar 2022 04:43:37 AM UTC.
Package dnf-plugins-core-4.0.21-4.el8_5.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
yum -y config-manager --set-enabled PowerTools
Updating Subscription Management repositories.
Error: No matching repo to modify: PowerTools.
yum -y install epel-release
Updating Subscription Management repositories.
Last metadata expiration check: 3:34:58 ago on Tue 22 Mar 2022 04:43:37 AM UTC.
Package epel-release-8-14.el8.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
dnf -y copr enable openfoam/openfoam
Updating Subscription Management repositories.
Enabling a Copr repository. Please note that this repository is not part
of the main distribution, and quality may vary.
The Fedora Project does not exercise any power over the contents of
this repository beyond the rules outlined in the Copr FAQ at
<https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr>,
and packages are not held to any quality or security level.
Please do not file bug reports about these packages in Fedora
Bugzilla. In case of problems, contact the owner of this repository.
Repository successfully enabled.
yum -y install openfoam2106 --installroot=/shared/apps/openfoam/yum
Unable to detect release version (use '--releasever' to specify release version)
Updating Subscription Management repositories.
Unable to read consumer identity
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Copr repo for openfoam owned by openfoam 7.0 kB/s | 3.3 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 5.6 B/s | 10 B 00:01
Errors during downloading metadata for repository 'rhel-8-for-x86_64-appstream-rpms':
- Status code: 404 for https://cdn.redhat.com/content/dist/rhel8/$releasever/x86_64/appstream/os/repodata/repomd.xml (IP: 95.101.56.251)
Error: Failed to download metadata for repo 'rhel-8-for-x86_64-appstream-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were triedhttps://develop.openfoam.com/Development/openfoam/-/issues/2417Compile error with mingw on OpenSUSE2022-08-16T09:08:40ZJK KimCompile error with mingw on OpenSUSEHello, I ran into a problem while compiling OpenFOAM for Windows.
I could not find anything about "mpi.h" except "export WM_MPLIB=MSMPI" in your [cross compile mingw](https://develop.openfoam.com/Development/openfoam/-/wikis/building/cr...Hello, I ran into a problem while compiling OpenFOAM for Windows.
I could not find anything about "mpi.h" except "export WM_MPLIB=MSMPI" in your [cross compile mingw](https://develop.openfoam.com/Development/openfoam/-/wikis/building/cross-compile-mingw).
Please have a look at the following log and help me.
Thank you in advance.
```
kimjk@localhost:~/OpenFOAM/OpenFOAM-v2112> foam
kimjk@localhost:~/OpenFOAM/OpenFOAM-v2112> ./Allwmake -s -l
Logging wmake -all output to 'log.linux64MingwDPInt32Opt'
gcc=/usr/bin/gcc
clang=
mpirun=
make=/usr/bin/make
cmake=
wmake=/home/kimjk/OpenFOAM/OpenFOAM-v2112/wmake/wmake
m4=/usr/bin/m4
flex=/usr/bin/flex
compiler=/usr/bin/x86_64-w64-mingw32-g++
x86_64-w64-mingw32-g++ (SUSE Linux) 10.3.0
========================================
2022-03-21 18:17:47 +0900
Starting compile OpenFOAM-v2112 Allwmake
Mingw system compiler
linux64MingwDPInt32Opt, with MSMPI msmpi
========================================
built wmake-bin (linux64Mingw) with linux64Gcc
built wmake-bin (win64Mingw) with linux64Mingw
Skip ThirdParty (no directory)
========================================
Compile OpenFOAM libraries
========================================
ln: OpenFOAM/lnInclude
ln: OSspecific/MSwindows/lnInclude
wmake libo (MSwindows)
wmake libo
wmake libo dummy (mpi=dummy)
wmake libo dummy
wmake OpenFOAM
wmake dummy (mpi=MSMPI)
wmake dummy
wmake mpi (mpi=MSMPI:msmpi)
wmake mpi
Ctoo: UOPwrite.C
In file included from UOPwrite.C:33:
PstreamGlobals.H:42:10: fatal error: mpi.h: No such file or directory
42 | #include <mpi.h>
| ^~~~~~~
compilation terminated.
make: *** [/home/kimjk/OpenFOAM/OpenFOAM-v2112/wmake/rules/General/transform:35: /home/kimjk/OpenFOAM/OpenFOAM-v2112/build/linux64MingwDPInt32OptMSMPI/src/Pstream/mpi/UOPwrite.o] Error 1
Done logging to 'log.linux64MingwDPInt32Opt'
kimjk@localhost:~/OpenFOAM/OpenFOAM-v2112>
```https://develop.openfoam.com/Development/openfoam/-/issues/2415solidFoam does not allow changing time steps2022-05-06T11:06:56ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsolidFoam does not allow changing time steps### Functionality to add/problem to solve
solidFoam does not support e.g. setTimeStep FO.
### Proposal
Define a 'Courant' number and include time-step changing. The problem is that `time.setDeltaT(..)` is not called so there is no ca...### Functionality to add/problem to solve
solidFoam does not support e.g. setTimeStep FO.
### Proposal
Define a 'Courant' number and include time-step changing. The problem is that `time.setDeltaT(..)` is not called so there is no call to `functionObjects_.adjustTimeStep()`.
### What does success look like, and how can we measure that?
Run with `setTimeStep` FOhttps://develop.openfoam.com/Development/openfoam/-/issues/2414report number of cells/faces capped by limitVelocity2022-04-25T11:49:45ZMark OLESENreport number of cells/faces capped by limitVelocitycf. EP1841
Also report relative (%) of cells/faces affected.cf. EP1841
Also report relative (%) of cells/faces affected.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2413Adjoint Smooth Sensitivities fails under WM_LABEL_SIZE=642024-01-11T18:58:45ZDiego PardoAdjoint Smooth Sensitivities fails under WM_LABEL_SIZE=64### Summary
Running the tutorial: $FOAM_TUTORIALS/incompressible/adjointOptimisationFoam/sensitivityMaps/motorBike
With OpenFOAM compiled with **label size 64** (instead of the default 32) leads to an MPI error.
The only modification ...### Summary
Running the tutorial: $FOAM_TUTORIALS/incompressible/adjointOptimisationFoam/sensitivityMaps/motorBike
With OpenFOAM compiled with **label size 64** (instead of the default 32) leads to an MPI error.
The only modification to the tutorial is running in 2 processors rather than 20.
### Steps to reproduce
Using OpenFOAM compiled with label size 64 (`export WM_LABEL_SIZE=64`), run the following tutorial:
$FOAM_TUTORIALS/incompressible/adjointOptimisationFoam/sensitivityMaps/motorBike
I used only a 2 processor hierarchical decomposition:
```
numberOfSubdomains 2;
method hierarchical;
coeffs
{
n (2 1 1);
}
```
### What is the current *bug* behaviour?
MPI Error. The job does not finish.
### What is the expected *correct* behavior?
Successful job with 64 label size
### Relevant logs and/or images
I have attached the full log file: [log.adjointOptimisationFoam](/uploads/f44e8d6d1a5a494482f28f41b4b4bf49/log.adjointOptimisationFoam)
### Environment information
- OpenFOAM version : v2112
- Operating system : centos 8
- Compiler : gcc 8.4.0
### Possible fixes
The issue is somehow related to the inter-processor communication happening in the processorFaPatch.C
By changing the sender call
```
void Foam::processorFaPatch::initGeometry()
{
if (Pstream::parRun())
{
OPstream toNeighbProc
(
Pstream::commsTypes::blocking,
neighbProcNo() // ,
// 3*(sizeof(label) + size()*sizeof(vector)) <- Use automatically computed message size
);
...
...
}
```
And changing the recipient call
```
void Foam::processorFaPatch::calcGeometry()
{
if (Pstream::parRun())
{
{
IPstream fromNeighbProc
(
Pstream::commsTypes::blocking,
neighbProcNo() //,
// 3*(sizeof(label) + size()*sizeof(vector)) <- Use automatically computed message size
);
...
...
}
```
Appears to fix the issue. However I think this is only hiding the issue.https://develop.openfoam.com/Development/openfoam/-/issues/2407label nBufferLayers in dynamicRefineFvMesh produce no diffence2022-03-24T11:11:38ZAlberto ceschinlabel nBufferLayers in dynamicRefineFvMesh produce no diffence<!--
*** 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
There is no working option to increase buffer layers between refinement levels.
### Steps to reproduce
In tutorial multiphase/interFoam/RAS/motorBike , that is using dynamicRefineFvMesh, increasing label nBufferLayers from 1 to 2 or more does not bring any difference.
### 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
-->
With
`nBufferLayers 3;`
![Screenshot_from_2022-03-11_15-18-09](/uploads/300931c9ad400cafc513eca3e430af2b/Screenshot_from_2022-03-11_15-18-09.png)
### 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
- Operating system : Ubuntu 18https://develop.openfoam.com/Development/openfoam/-/issues/2406$:dict.entry in fvOptions-file2022-03-15T09:32:07ZJürgen Abraham$:dict.entry in fvOptions-fileI am using a caseSetupDict to store parameters for boundary conditions etc.
Now i wanted to extend this to my fvOptions files but noticed, that it is not working.
[fvOptions](/uploads/7a01947a3fb9115ff8934d6dfae58170/fvOptions)
[caseSet...I am using a caseSetupDict to store parameters for boundary conditions etc.
Now i wanted to extend this to my fvOptions files but noticed, that it is not working.
[fvOptions](/uploads/7a01947a3fb9115ff8934d6dfae58170/fvOptions)
[caseSetupDict](/uploads/c35542b3f2a89d17aa2d6f401029c742/caseSetupDict)https://develop.openfoam.com/Development/openfoam/-/issues/2405distributedTriSurfaceMesh used for refinement shell not consistent flipped2022-06-28T10:58:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdistributedTriSurfaceMesh used for refinement shell not consistent flipped<!--
*** 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 snappyHexMesh a distributedTriSurfaceMesh can be used as a closed refinement shell. This can lead to problems if it decides to orient the geometry and that decision is not the same on all processors.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Original geometry is too big. But have an STL shell surfaces and change its type from 'triSurfaceMesh' to 'distributedTriSurfaceMesh'. Change the decomposition method to a nonsense one (only 'hierarchical' really makes sense for meshing).
Depending on the case some of the processors (if they have zero faces of it) might decide not to orient it whereas others might. This can cause an inconsistent orientation.
### 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 -->
Error inside snappyHexMesh at startup (on some processors only) when it is orienting the shell surfaces.
### 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
### 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
-->
Take consistent decision (flip/not-flip) on all processors, not just looking at own processor.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2404ENH: snappyHexMesh multi-pass layer addition2022-12-23T14:58:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comENH: snappyHexMesh multi-pass layer addition### Functionality to add/problem to solve
Add layers in snappyHexMesh one-by-one.
### Target audience
Multi-layer generation on smooth surfaces
### Proposal
Calculate the wanted amount of layers and distribution of thickness. Add l...### Functionality to add/problem to solve
Add layers in snappyHexMesh one-by-one.
### Target audience
Multi-layer generation on smooth surfaces
### Proposal
Calculate the wanted amount of layers and distribution of thickness. Add layers one-by-one (still growing out from the bulk)
### What does success look like, and how can we measure that?
Optionally add layers one-by-one. Compare to adding layers in one go (the default).Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com