Development issueshttps://develop.openfoam.com/groups/Development/-/issues2024-01-11T15:06:56Zhttps://develop.openfoam.com/Development/openfoam/-/issues/2240FPE handling for OSX arm642024-01-11T15:06:56ZMark OLESENFPE handling for OSX arm64Mentioned in cfd-online and refers to this gitrepo :
https://github.com/ttsyshmz/howtoFoam/blob/main/codes/feexceptErsatz-v2106/feexceptErsatz.HMentioned in cfd-online and refers to this gitrepo :
https://github.com/ttsyshmz/howtoFoam/blob/main/codes/feexceptErsatz-v2106/feexceptErsatz.Hv2306Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2241Cannot create valid tet decomposition for wegde mesh2021-10-26T15:18:53ZJan GärtnerCannot create valid tet decomposition for wegde mesh### Summary
A wedge mesh generated with blockMesh in OpenFOAM v2012 cannot be decomposed into tets with `polyMeshTetDecomposition::cellTetIndices()` and the `tetIndices::faceTriIs()` function.
A possible reason might be that four poin...### Summary
A wedge mesh generated with blockMesh in OpenFOAM v2012 cannot be decomposed into tets with `polyMeshTetDecomposition::cellTetIndices()` and the `tetIndices::faceTriIs()` function.
A possible reason might be that four points of the tet face are reported, e.g. for the sketch below it writes face (A B C A)
```c++
// A general wege
C
+
/|
/ |
/ 1|
+---+ B
^
A
```
If the mesh is generated with blockMesh of OpenFOAM 5.x the error does not occur. Note, only the mesh is generated with 5.x decomposition into tets is then done with v2012.
### Steps to reproduce
* Generate a wedge domain with blockMesh
* Use cellTetIndices to get the tets for all cells and try to find the `faceTriIs`. An example `main()` function could be:
```c++
int main()
{
#include "setRootCase.H"
#include "createTime.H"
#include "createMesh.H"
forAll(mesh,cellI)
{
List<tetIndices> cellTets =
polyMeshTetDecomposition::cellTetIndices(mesh, cellI);
triFaceList triFaces(cellTets.size());
forAll(cellTets, cTI)
{
triFaces[cTI] = cellTets[cTI].faceTriIs(mesh);
}
}
return 0;
};
```
* This will return the warning:
> --> FOAM Warning :
> From Foam::triFace Foam::tetIndices::faceTriIs(const Foam::polyMesh&, bool) const
> in file <FILEPATH>
> No base point for face 1620, 4(0 1 442 441), produces a valid tet decomposition.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906|v1912|v2006|v2012|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2012
- Operating system : ubuntu 18.04 LTS
- Hardware info : amd ryzen 7
- Compiler : g++ 7.5.0Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2242decomposePar preservePatches does not handle cyclicA(C)MI2021-11-02T12:19:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar preservePatches does not handle cyclicA(C)MI### Functionality to add/problem to solve
Currently preservePatches only works for cyclics, not for cyclicAMI. Also it will not handle cells having faces on multiple cyclics since it does not loop.
### Target audience
E.g. implicit A...### Functionality to add/problem to solve
Currently preservePatches only works for cyclics, not for cyclicAMI. Also it will not handle cells having faces on multiple cyclics since it does not loop.
### Target audience
E.g. implicit AMI handling requires the faces on both sides to be on the same processor. This ideally would be done by preservePatches constraint.
### Proposal
Attached version.
[preservePatchesConstraint.C](/uploads/90d1229d7e3e24351f4658f4cac609d4/preservePatchesConstraint.C)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2244foamDebugSwitches script is still mentioned in programmer's guide2021-10-27T11:38:37Zs1291foamDebugSwitches script is still mentioned in programmer's guideHi,
In OpenFOAM Programmer's guide (Page 21), the foamDebugSwitches script is still there.
![image](/uploads/03f9c0483f16328a90fa46d87dd1735d/image.png)
RegardsHi,
In OpenFOAM Programmer's guide (Page 21), the foamDebugSwitches script is still there.
![image](/uploads/03f9c0483f16328a90fa46d87dd1735d/image.png)
Regardshttps://develop.openfoam.com/Development/openfoam/-/issues/2245Sign up for newsletter is not available2021-10-29T04:24:12Zs1291Sign up for newsletter is not availableHi,
In the website openfoam.com, there is a header at the page footer, "Sign up for our newsletter". In fact it is a header without any link to sign up. I do not know if this is just a placeholder from the website template or someone fo...Hi,
In the website openfoam.com, there is a header at the page footer, "Sign up for our newsletter". In fact it is a header without any link to sign up. I do not know if this is just a placeholder from the website template or someone forgot to add the link to subscribe to the newsletter (does it exist?). See the screenshot below.
Regards
![image](/uploads/93ad4b58c75a580ff1afaea0f52c9a81/image.png)https://develop.openfoam.com/Development/openfoam/-/issues/2246chtMultiRegionFoam looses heat due to explicit coupling2021-10-27T17:02:48ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comchtMultiRegionFoam looses heat due to explicit coupling### Functionality to add/problem to solve
chtMultiRegionFoam looses heat when evaluating 'mapped' type bcs (e.g. `compressible::turbulentTemperatureRadCoupledMixed`). This is because the owner side evaluates with 'old' neighbour side va...### Functionality to add/problem to solve
chtMultiRegionFoam looses heat when evaluating 'mapped' type bcs (e.g. `compressible::turbulentTemperatureRadCoupledMixed`). This is because the owner side evaluates with 'old' neighbour side values but the neighbour side evaluates with the 'new'
owner side values.
This should instead use a scheme where the owner side also updates the neighbour side patch.
### Target audience
cht on closed domains. See e.g. https://develop.openfoam.com/Development/openfoam/-/blob/develop/applications/test/multiWorld/solidFoam/solid1_solid2 testcase.
Switch off the kappaLayers, switch to transient, switch on the debug flag for the BC so it prints the heat flux for both sides.https://develop.openfoam.com/Development/openfoam/-/issues/2247OpenFOAM2106 overInterDyMFoam issue2021-10-27T11:32:44ZAbhishek MukherjeeOpenFOAM2106 overInterDyMFoam issue<!--
*** 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
Unable to run the tutorial case of overInterDyMFoam floatingBody
### Steps to reproduce
In the tutorial case just execute Allrun (./Allrun)
### 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?
(```/home/abhishek/Desktop/dam_break_test/openfoma_fsi_test/overInterDyMFoam/floatingBody/background/consta\
nt/dynamicMeshDict.sixDoFRigidBodyMotionCoeffs.#codeStream: In function ‘void Foam::codeStream_a63eab21\
7afa7dd34ef7da3a82ee21fc2b054ce0(Foam::Ostream&, const Foam::dictionary&)’:
/home/abhishek/Desktop/dam_break_test/openfoma_fsi_test/overInterDyMFoam/floatingBody/background/consta\
nt/dynamicMeshDict.sixDoFRigidBodyMotionCoeffs.#codeStream:58:17: error: ‘diagTensor’ was not declared \
in this scope; did you mean ‘DiagTensor’?
make: *** [/media/abhishek/WD-phd/OpenFOAM/OpenFoam-2106/OpenFOAM-v2106/wmake/rules/General/transform:3\
5: Make/linux64GccDPInt32Opt/codeStreamTemplate.o] Error 1
--> FOAM FATAL IO ERROR: (openfoam-2106)
Failed wmake "dynamicCode/_a63eab217afa7dd34ef7da3a82ee21fc2b054ce0/platforms/linux64GccDPInt32Opt/lib/\
libcodeStream_a63eab217afa7dd34ef7da3a82ee21fc2b054ce0.so"```)
### 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 : v2106
Operating system : ubuntu
Hardware info : any info that may help?
Compiler : gcc
-->
- OpenFOAM version : v2106
- Operating system : ubuntu
- Hardware info :
- 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
-->https://develop.openfoam.com/Development/openfoam/-/issues/2248Packages for Ubuntu 21.10 "impish" not available2023-01-02T14:54:40ZGerasimos ChourdakisPackages for Ubuntu 21.10 "impish" not availableI guess you probably already have it at the radar, I am just not sure if you know that the Ubuntu 21.10 is out already since last week (I also expected it this week).
Happy to test it in any case! (just waiting for it before I upgrade)I guess you probably already have it at the radar, I am just not sure if you know that the Ubuntu 21.10 is out already since last week (I also expected it this week).
Happy to test it in any case! (just waiting for it before I upgrade)https://develop.openfoam.com/Development/openfoam/-/issues/2249fluentMeshToFoam and fluent3DMeshToFoam cannot handle semicolon2021-11-02T15:30:28ZGuanyang XuefluentMeshToFoam and fluent3DMeshToFoam cannot handle semicolon
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
fluentMeshToFoam and fluent3DMeshToFoam cannot handle semicolon
### Steps to reproduce
Import a .cas file from a recent versi...
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
fluentMeshToFoam and fluent3DMeshToFoam cannot handle semicolon
### Steps to reproduce
Import a .cas file from a recent version of Fluent
### 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?
```
--> FOAM FATAL ERROR: (openfoam-2012)
Do not understand characters: ;
on line 7134
From virtual int yyFlexLexer::yylex()
in file fluent3DMeshToFoam.L at line 762.
FOAM exiting
```
### 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 : v1806|v1812|v1906|v1912|v2006|v2012|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : All .com versions
- Operating system :
- Hardware info :
- Compiler :
### Possible fixes
The fixes are already in .org version https://github.com/OpenFOAM/OpenFOAM-dev/commit/c61a66fc0021a11fe4f71178c737b7e5bb352b38#diff-c32e87834be41beeef44f747867f67e6d2988b2e6c4f11f8c8b3525195a24088Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2250Support for time-varying coordinate system in forces function object2021-10-27T18:28:19Zs1291Support for time-varying coordinate system in forces function objectOLD TITLE: ~~Object time does not exist or wrong type when using expressions~~
Hi,
I am following the documentation about Expressions syntax here: https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-expression-synta...OLD TITLE: ~~Object time does not exist or wrong type when using expressions~~
Hi,
I am following the documentation about Expressions syntax here: https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-expression-syntax.html
Under the **constants** section, it is mentioned that `time()` is available and has access to the current simulation time. Here is an example:
```
forces_local
{
type forces;
libs ("libforces.so");
enabled true;
patches (cylinder);
//CofR (0 0 0.02);
writeControl timeStep;
writeInterval 1;
rho rhoInf;
rhoInf 1.225;
p p;
U U;
log true;
coordinateSystem
{
type cartesian;
origin (0 0 0.02);
coordinateRotation
{
type axesRotation; // local Cartesian co-ordinates
//e1 (0.7071067811865 -0.7071067811865 0);
//e2 (0.7071067811865 0.7071067811865 0);
e1 #eval "vector(cos(pi()*pi()/4.0),-sin(pi()*time()/4.0),0.0)";
e2 #eval "vector(sin(pi()*pi()/4.0),cos(pi()*pi()/4.0),0.0)";
}
}
```
I get the following error when I run pimpleFoam:
```
--> FOAM FATAL IO ERROR: (openfoam-2106)
Object time does not exist or wrong type in expression at position:36
<<<<
vector(cos(pi()*pi()/4.0),-sin(pi()*time()/4.0/time()),0.0)
^^^^ near here
```
Is it a bug? or I am missing something?
Thank youhttps://develop.openfoam.com/Development/openfoam/-/issues/2251splitMeshRegions: automatic repatching2023-05-31T11:15:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsplitMeshRegions: automatic repatching### Functionality to add/problem to solve
cht cases can be tricky to mesh and set-up for large numbers of regions. One improvement would be to add support inside splitMeshRegions to automatically detect which regions/faces are close tog...### Functionality to add/problem to solve
cht cases can be tricky to mesh and set-up for large numbers of regions. One improvement would be to add support inside splitMeshRegions to automatically detect which regions/faces are close together and auto-generate patches for these.
### Target audience
cht without correct patching
### Proposal
Using the AMI algorithm see what produces a valid match and pick up these faces.
### What does success look like, and how can we measure that?
On a reasonable mesh see whether the patching is done correctly.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2253Usage by the postProcess utility is not available.2021-11-01T09:42:56Zs1291Usage by the postProcess utility is not available.Hello,
Skimming through the doxygen documentation, one can find the following sentence for some function objects:
> Usage by the postProcess utility is not available.
It is not clear what does that mean (at least it is confusing). For...Hello,
Skimming through the doxygen documentation, one can find the following sentence for some function objects:
> Usage by the postProcess utility is not available.
It is not clear what does that mean (at least it is confusing). For example, for the `fieldMinMax` [function object](https://www.openfoam.com/documentation/guides/latest/doc/guide-fos-field-fieldMinMax.html) we can find that statement. But it's possible to use that FO from the `postProcess` utility, e.g:
```
postProcess -fields "(k nut U)" -func "fieldMinMax(fields=(k nut U),writeToFile=false)"
```
What I am missing?
Thank you,
(If you think this is not related, feel free to close this issue).https://develop.openfoam.com/Development/openfoam/-/issues/2254update of third-party packages for v21122022-06-27T09:34:39ZMark OLESENupdate of third-party packages for v2112Currently:
- ADIOS2-2.6.0
- CGAL-4.12.2
- ParaView-v5.9.1
- boost_1_66_0
- fftw-3.3.7
- openmpi-4.0.3
- scotch_6.1.0
- kahip-2.12
My thoughts:
- ADIOS: could probably bump to 2.7.1 (Jan 2021)
- CGAL: @andy is conservative there (been b...Currently:
- ADIOS2-2.6.0
- CGAL-4.12.2
- ParaView-v5.9.1
- boost_1_66_0
- fftw-3.3.7
- openmpi-4.0.3
- scotch_6.1.0
- kahip-2.12
My thoughts:
- ADIOS: could probably bump to 2.7.1 (Jan 2021)
- CGAL: @andy is conservative there (been bitten badly in the past), but can try moving to the latest bugfix 4.x version (4.14.2 - Nov 2019). Cannot/should not move to 5.x since this requires c++14 and thus breaks installation on centos7, SUSE 12 etc.
- ParaView: definitely want paraview 5.10 which has our various changes in it. Currently in a release candidate stage and should be finished in time.
- boost: no opinion. openSUSE still ships with 1_66_0 as well
- fftw: 3.3.10 bugfix version
- openmpi: either 4.0.6 as bugfix for the 4.0.x or try with 4.1.1 (latest stable)
- scotch: no change
- kahip: currently at 3.11 - need to see what has improved.
@Development : Wanted to get people's opinions about updating what we bundle as _ThirdParty_.
Do we drop shipping paraview sources anytime soon?
EDITS:
- paraview now at 5.10.0-RC2 (22 Nov)v2112https://develop.openfoam.com/Development/openfoam/-/issues/2255LH2 boiling: EP16972022-03-30T11:03:59ZPawan GhildiyalLH2 boiling: EP1697This model is not committed to "feature-sub-cooling-ext"
i) **CHFSubCoolModels **
type Tatsumoto;
ii)For nucleate boiling : Eq [8] and Eq [10]. (Kutadeladze and exponential respectively)
exponential model is not there...This model is not committed to "feature-sub-cooling-ext"
i) **CHFSubCoolModels **
type Tatsumoto;
ii)For nucleate boiling : Eq [8] and Eq [10]. (Kutadeladze and exponential respectively)
exponential model is not there in this branch.Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/2256Bug in sutherlandTransport2021-11-03T20:28:33ZKevinBug in sutherlandTransport### Summary
Code bug in template function sutherlandTransport::operator+ (not used in standard solvers) which prevents compilation when attempting to compile code that uses simple addition of thermo models.
### Steps to reproduce
Atte...### Summary
Code bug in template function sutherlandTransport::operator+ (not used in standard solvers) which prevents compilation when attempting to compile code that uses simple addition of thermo models.
### Steps to reproduce
Attempt to compile a code using form
```
sutherlandTransport<Thermo> A, B;
sutherlandTransport<Thermo> C = A + B;
```
### What is the current *bug* behaviour?
Code will not compile due to malformed [constructor call](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/thermophysicalModels/specie/transport/sutherland/sutherlandTransportI.H#L196)
### Environment information
- OpenFOAM version : v2106 and master
### Possible fixes
Remove extra (invalid) argument to constructor in [sutherlandTransportI.H](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/thermophysicalModels/specie/transport/sutherland/sutherlandTransportI.H#L199)https://develop.openfoam.com/Development/openfoam/-/issues/2257threaded collated writing (maxThreadFileBufferSize) fails at end of run2021-11-02T14:42:23ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comthreaded collated writing (maxThreadFileBufferSize) fails at end of run<!--
*** 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 -->
Sometimes (slow disks) at the end of a run with collated+threaded it fails with sigsegv.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Take case (e.g. cavity), make mesh bigger and time step smaller. Change to write every timestep. Switch on threaded writing and collated. On machines with slow IO the processor0 will finish with an error (sigsegv).
### 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. All depends on how slow the IO is.
### What is the current *bug* behaviour?
<!-- What actually happens -->
See above.
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906|v1912|v2006|v2012|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2106
- Operating system : linux
- Hardware info :
- Compiler :
### Possible fixes
Threaded writing uses a write thread. This gets passed all the data to write and it is now responsible for deleting the data after writing. This means that even e.g. header information cannot get passed in by reference since it might be out of scope when the writer is still writing.
<!--
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
-->
@markMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2258createBaffles/mergeOrSplitBaffles does not duplicate points correctly2021-11-04T15:20:34ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcreateBaffles/mergeOrSplitBaffles does not duplicate points correctly<!--
*** 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 -->
mergeOrSplitBaffles can duplicate points. It uses the underlying `localPointRegion` class to determine which faces should use what duplicate of the point. This class does not correctly mark points if a cell is fully surrounded by baffles.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Tested this only with a hacked version of extrudeMesh that does extrusion of a faceZone with internal and boundary faces. Not sure if the createBaffles/mergeOrSlitBaffles route has the same effect.
### Example case
[corner_blocked_2D.tgz](/uploads/a3acc10b5999552185cfa8726a79439d/corner_blocked_2D.tgz)
<!--
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 -->
Incorrect topology since face which is point connected to a duplicated point does not get renumbered to use the new duplicated point.
### What is the expected *correct* behavior?
<!-- What you should see instead -->
2x2x1 cells with bottom left cell (cell 0) having cells on its two internal faces and one boundary face.
### 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 : v1806|v1812|v1906|v1912|v2006|v2012|v2106 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
-->
Problem is in the localPointRegion class where it walks out the per-region point connectivity. Its set of 'candidate faces' does not include the faces that become blockages so if another face only uses points from those it will not be detected as needing to use a duplicate.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2259Decomposition method issue2021-12-09T16:44:05ZAshutosh MauryaDecomposition method issueI don't know whether it is a issue or limitation of hierarchical method. I ran the simulation on 12 processors to calculate force on a airfoil. The issue is with hierarchical decomposition method gives wrong result while scotch gives cor...I don't know whether it is a issue or limitation of hierarchical method. I ran the simulation on 12 processors to calculate force on a airfoil. The issue is with hierarchical decomposition method gives wrong result while scotch gives correct result.https://develop.openfoam.com/Development/openfoam/-/issues/2260forceCoeffs FO: pitchAxis keyword has no effect2021-11-08T08:35:56Zs1291forceCoeffs FO: pitchAxis keyword has no effectWhen using the `forceCoeffs` function object, it seems that the `pitchAxis` keyword has no effect. It is always set to `coordSys_.e2()`
**How to reproduce**
* Example 1: Run the tutorial: `$FOAM_TUTORIALS/incompressible/simpleFoam/simpl...When using the `forceCoeffs` function object, it seems that the `pitchAxis` keyword has no effect. It is always set to `coordSys_.e2()`
**How to reproduce**
* Example 1: Run the tutorial: `$FOAM_TUTORIALS/incompressible/simpleFoam/simpleCar`
* Example 2: Run the tutorial: `$FOAM_TUTORIALS/compressible/sonicFoam/RAS/nacaAirfoil`
Set the `pitchAxis` to some vector , the output in `postProcessing` directory will ignore that and prints the `e2` vector instead.
Checking the source code of the FO, it appears that `pitchAxis` keyword is not read. So, the presence of this keyword in the tutorials dir is _misleading_.
Running:
```
grep -r 'pitchAxis' $FOAM_TUTORIALS
```
Returns 7 tutorials using that keyword.
**OpenFOAM version**
* OpenFOAM v2106 on Ubuntu 20.04https://develop.openfoam.com/Development/openfoam/-/issues/2261Openfoam v2106 built with debug does not include scotch2021-11-17T15:17:52ZBushra RasheedOpenfoam v2106 built with debug does not include scotchHi!
I have been using parallel processing on several openfoam versions. Recently, I built openfoam v2106 from source with debug turned on in etc/bashrc file. All other tutorials are running fine as well but when I try to use scotch deco...Hi!
I have been using parallel processing on several openfoam versions. Recently, I built openfoam v2106 from source with debug turned on in etc/bashrc file. All other tutorials are running fine as well but when I try to use scotch decomposition, it gives me the following error:
```
Decomposition method scotch [4] (region region0)
--> FOAM FATAL ERROR: (openfoam-2106)
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.
```
Please help resolve this.
Thanks!