Development issueshttps://develop.openfoam.com/groups/Development/-/issues2020-01-03T11:28:59Zhttps://develop.openfoam.com/Development/openfoam/-/issues/681Feature: Possibility for the concurrent usage of multiple subsetFeatures in s...2020-01-03T11:28:59ZKutalmış BerçinFeature: Possibility for the concurrent usage of multiple subsetFeatures in surfaceFeatureExtractDictConsider the OpenFOAM-v1706 tutorial: `/tutorials/mesh/foamyHexMesh/mixerVessel`
Therein, the feature lines of `shaftRotating.stl` were extracted and subsetted via the following group of entries in `surfaceFeatureExtractDict`:
```
subs...Consider the OpenFOAM-v1706 tutorial: `/tutorials/mesh/foamyHexMesh/mixerVessel`
Therein, the feature lines of `shaftRotating.stl` were extracted and subsetted via the following group of entries in `surfaceFeatureExtractDict`:
```
subsetFeatures
{
// Remove the top feature
insideBox (-0.1 -0.1 -0.1)(0.1 0.1 0.1);
}
```
Say, the user required not to remove (or remove) some other features in the same .stl file. To this end, IMHO, the user likely adds another `subsetFeatures` entry by intuition. Let add another box into the tutorial's entry, so that it can readily be reproduced:
```
subsetFeatures
{
// Remove all other features apart from the top and bottom features
insideBox (-0.1 -0.1 -0.1)(0.1 0.1 0.1);
insideBox (-0.1 -0.1 0.8)(0.1 0.1 1);
}
```
Yet the execution of `surfaceFeatureExtract` yields the consideration of **only** the latter box. The output stream is:
```
...
Subset edges inside box (-0.1 -0.1 0.8) (0.1 0.1 1)
...
```
In addition, the simultaneous usage of different entries seems also not possible. For example, when the user enters `insideBox` and `outsideBox` entries under the same `subsetFeatures`, the `insideBox` seems overriding the `outsideBox` entry irrespective of the order of entry sequence.
I found a workaround to subset features from several regions on the same surface mesh, yet this requires sequential command executions. For instance, if one wants to remove/add features from two different locations on the same surface mesh, the person can extract the first region through `surfaceFeatureExtract` with a single `subsetFeature`. Then, the resulted '.eMesh' files can be used to extract features in the second region through another `surfaceFeatureExtract`, however, this time using `extractionMethod extractFromFile;` with another `subsetFeature`, and so on.
IMHO, from a user perspective, a simultaneous surface feature extraction, which may need to consider multiple region restrictions for some reason, might be facilitative.
Kind regardshttps://develop.openfoam.com/Development/openfoam/-/issues/680decomposition fails with faMesh2017-12-22T11:54:11ZMark OLESENdecomposition fails with faMeshRunning the wolfsgrube avalanche tutorial. Decomposing with 4 proc OK.
Decomposing with hierarchical (4 4 1)
--> FOAM FATAL ERROR:
Impossible processor label 757738797for face 8
From function Finite area mesh decompositio...Running the wolfsgrube avalanche tutorial. Decomposing with 4 proc OK.
Decomposing with hierarchical (4 4 1)
--> FOAM FATAL ERROR:
Impossible processor label 757738797for face 8
From function Finite area mesh decomposition
in file faMeshDecomposition.C at line 223.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/679redistributePar fails for faMesh2020-01-07T16:32:23ZMark OLESENredistributePar fails for faMeshv1806Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/678fftw compile problem in single-precision2017-12-21T15:59:45ZMark OLESENfftw compile problem in single-precisionv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/677Medium loop- failures - 21.12.20172018-06-12T04:01:04ZPrashant SonakarMedium loop- failures - 21.12.2017Cases in :
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/
- compressible/sonicFoam/RAS/nacaAirfoil - solver failed
- multiphase/reactingTwoPhaseEulerFoam/laminar/steamInjection - solver failed
- multiphase/compressibleInt...Cases in :
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/
- compressible/sonicFoam/RAS/nacaAirfoil - solver failed
- multiphase/reactingTwoPhaseEulerFoam/laminar/steamInjection - solver failed
- multiphase/compressibleInterDyMFoam/laminar/sphereDrop -solver failed
- multiphase/interFoam/laminar/vofToLagrangian/eulerianInjection -solver failed
@andy @Mattijs @Sergio @markhttps://develop.openfoam.com/Development/openfoam/-/issues/676label64 with FULLDEBUG gives problems2018-01-17T13:27:15ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comlabel64 with FULLDEBUG gives problemsWhen doing WM_LABEL_SIZE=64 and WM_COMPILE_OPTION=Debug there is a problem in reading even the initial controlDict. This traces back to UIPstream::readStringFromBuffer where it tries to read zero bytes from the current pointer (&external...When doing WM_LABEL_SIZE=64 and WM_COMPILE_OPTION=Debug there is a problem in reading even the initial controlDict. This traces back to UIPstream::readStringFromBuffer where it tries to read zero bytes from the current pointer (&externalBuf_[externalBufPosition_]).
If that pointer points to one-beyond the end of the buffer the call will fail.
Workaround: do not use pointer in case of zero bytes. Note that it only affects the fulldebug checking; the library routine handles it ok.
E.g.
inline Foam::Istream& Foam::UIPstream::readStringFromBuffer(std::string& str)
{
// Use std::string::assign() to copy content, including '\0'.
// Stripping (when desired) is the responsibility of the sending side.
size_t len;
readFromBuffer(len);
if (len == 0)
{
str.assign(nullptr, len);
}
else
{
str.assign(&externalBuf_[externalBufPosition_], len);
}https://develop.openfoam.com/Development/ThirdParty-common/-/issues/29more stringency when exporting WM_ compiler settings2018-05-29T10:42:24ZMark OLESENmore stringency when exporting WM_ compiler settings- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env...- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env sets ThirdParty Clang (setting WM_CC in the process), but this is the component we are trying to build, so `makeLLVM` will have problems configuring for this non-existent compiler.
1. can avoid this by using `makeLLVM -gcc` to force use of gcc for making Clang. This seems to be an ok alternative, since this isn't part of the normal OpenFOAM process (we are building the toolchain for building OpenFOAM).
2. check within the ThirdParty scripts that the exported `CC` variable corresponds to a command. Eg,
if test -n "$WM_CC" && command -v "$WM_CC" >/dev/null
then
export CC="$WM_CC"
[ -n "$WM_CFLAGS" ] && export CFLAGS="$WM_CFLAGS"
fi
Probably the second one is OK to include too, but targeted for the next release.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/675Failures - collate fileHandler - 20.12.20172023-12-22T09:19:14ZPrashant SonakarFailures - collate fileHandler - 20.12.2017Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3line...Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3lines.txt)
- list of unconfirmed completions. [listOfUnconfirmedCompletion.txt](/uploads/4e87a9784b7354cd00da7cdc77cdfe83/listOfUnconfirmedCompletion.txt)
run with $FOAM_ETC/controlDict set to collated in
/hosts/punwor073/home/pss/OpenFOAM/compilations/ALPHA/centos6.6_compilation/OpenFOAM-plus.develop/tutorialsTest
@Mattijs @mark @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/674configuring 3rd party clang and mpfr2018-03-05T15:26:00ZMark OLESENconfiguring 3rd party clang and mpfr- When using third-party compilers, it is currently possible to build gcc with a system or third-party installation of gmp/mpfr. The clang installation does not normally need these. However CGAL does normally build using gmp/mpfr. If the...- When using third-party compilers, it is currently possible to build gcc with a system or third-party installation of gmp/mpfr. The clang installation does not normally need these. However CGAL does normally build using gmp/mpfr. If these are not available on the system, it is also possible to compile without. Eg,
./makeCGAL gmp-none mpfr-none
This mostly solves the problem, but only until the final link stage. The wmake rules for CGAL include `-lmpfr` explicitly. As a workaround, this can be removed, but a better solution may be to check the contents of the CGAL/compiler_config.h for this type of content:
#define CGAL_USE_GMP 1
#define CGAL_USE_MPFR 1
//#define CGAL_USE_GMPXX 1v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/673scalarRanges from string could be improved2018-01-23T15:54:43ZMark OLESENscalarRanges from string could be improvedAs noted discovered in #672 the creation of scalarRanges from a string uses an Istream for the intermediate tokens and parses through until it hits an error. This fails when the Istream is an ITstream since for that class the eof trig...As noted discovered in #672 the creation of scalarRanges from a string uses an Istream for the intermediate tokens and parses through until it hits an error. This fails when the Istream is an ITstream since for that class the eof triggers an error.
Would be cleanest to pass through the raw string directly create tokens and then walk through them in a normal loop.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/672regression on arglist handling2017-12-20T11:09:34ZMark OLESENregression on arglist handlingreported by @Sergio for reconstructPar - I'm on it
@andy @Prashantreported by @Sergio for reconstructPar - I'm on it
@andy @Prashantv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/671Failures- unitTest: 19.12.20172018-06-12T04:01:30ZPrashant SonakarFailures- unitTest: 19.12.2017```64bit LABEL_SIZE compilation```
Files accessible at /home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop.alex/tutorialsTest
- Error
```
Application decomposePar - case combustion/XiDyMFoam/annularCombustorTurbine: ** FOAM FATAL ERRO...```64bit LABEL_SIZE compilation```
Files accessible at /home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop.alex/tutorialsTest
- Error
```
Application decomposePar - case combustion/XiDyMFoam/annularCombustorTurbine: ** FOAM FATAL ERROR **
Application potentialFoam - case combustion/XiDyMFoam/annularCombustorTurbine: ** FOAM FATAL ERROR **
Application XiDyMFoam - case combustion/XiDyMFoam/annularCombustorTurbine: ** FOAM FATAL ERROR **
Application chtMultiRegionSimpleFoam - case heatTransfer/chtMultiRegionSimpleFoam/externalCoupledHeater: ** FOAM FATAL ERROR **
Application chtMultiRegionSimpleFoam - case heatTransfer/chtMultiRegionSimpleFoam/jouleHeatingSolid: ** FOAM FATAL ERROR **
Application snappyHexMesh - case incompressible/simpleFoam/motorBike: ** FOAM FATAL ERROR ** (32bit label size OK!)
Application decomposePar - case incompressible/pimpleFoam/LES/channel395: ** FOAM FATAL ERROR **
Application pimpleFoam - case incompressible/pimpleFoam/LES/channel395: ** FOAM FATAL ERROR **
Application reconstructPar - case incompressible/pimpleFoam/LES/channel395: ** FOAM FATAL ERROR **
Application decomposePar - case incompressible/pimpleFoam/LES/channel395DFSEM: ** FOAM FATAL ERROR **
Application pimpleFoam - case incompressible/pimpleFoam/LES/channel395DFSEM: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/verticalChannelLTS: ** FOAM FATAL ERROR **
Application interIsoFoam.postProcess - case multiphase/interIsoFoam/notchedDiscInSolidBodyRotation: ** FOAM FATAL ERROR **
```
- unconfirmed completion
```
Application rhoPimpleFoam - case compressible/rhoPimpleFoam/RAS/angledDuct
```
- Have a proper "End" or "Finalize" comment for logs
```
Application makeFaMesh - case finiteArea/liquidFilmFoam/cylinder
Application makeFaMesh - case finiteArea/sphereSurfactantFoam/sphereTransport
Application makeFaMesh - case finiteArea/surfactantFoam/planeTransport
- heatTransfer/chtMultiRegionFoam/multiRegionHeater/Allmesh called as runApplication
- mesh/stitchMesh/simple-cube1/Allmesh called as runApplication
```
@Sergio @mark @andy @Mattijshttps://develop.openfoam.com/Development/openfoam/-/issues/670bug : refineMesh fails with attached Allrun2018-07-02T16:18:50ZAdminbug : refineMesh fails with attached Allrunerror -
[0] --> FOAM FATAL ERROR:
[0] Cut (77039 18800) on face (9.5246807 -8.8045243 1.7253121) of coupled patch procBoundary0to1 is not consistent with coupled cut (1099 77039)
[0]
[0] From function void Foam::cellCuts::syncProc()...error -
[0] --> FOAM FATAL ERROR:
[0] Cut (77039 18800) on face (9.5246807 -8.8045243 1.7253121) of coupled patch procBoundary0to1 is not consistent with coupled cut (1099 77039)
[0]
[0] From function void Foam::cellCuts::syncProc()
[0] in file meshCut/cellCuts/cellCuts.C at line 256.
[0]
FOAM parallel run exiting
[Allrun](/uploads/cbcf69aba24b5d0f865b0a038e7b4f27/Allrun)
Case - $FOAM_TUTORIALS/mesh/refineMesh/refineFieldDirshttps://develop.openfoam.com/Development/openfoam/-/issues/669reduce verbosity for decomposition methods2021-07-06T11:41:56ZMark OLESENreduce verbosity for decomposition methodsAs reported by @Prashant, causes unnecessarily noisy output and can be confused with SHM imbalance.As reported by @Prashant, causes unnecessarily noisy output and can be confused with SHM imbalance.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/668"Cannot find triSurfaceMesh at...." error in Snappyhexmesh in parallel2021-07-06T11:35:22ZAdmin"Cannot find triSurfaceMesh at...." error in Snappyhexmesh in parallelSnappyhexmesh is looking for a stl file in process folders after decomposition and gives the following error:
Cannot find triSurfaceMesh at...
\## Reattaching the author to the issue ticket: @arionfard ##Snappyhexmesh is looking for a stl file in process folders after decomposition and gives the following error:
Cannot find triSurfaceMesh at...
\## Reattaching the author to the issue ticket: @arionfard ##https://develop.openfoam.com/Development/openfoam/-/issues/667yPlus utility does not work with twoPhaseEulerFoam/reactingTwoPhaseEulerFoam2018-11-29T23:02:22ZAdminyPlus utility does not work with twoPhaseEulerFoam/reactingTwoPhaseEulerFoamThe yPlus utility does not seem to work with twoPhaseEulerFoam or reactingTwoPhaseEulerFoam.
--> FOAM Warning :
From function virtual bool Foam::functionObjects::yPlus::execute()
in file yPlus/yPlus.C at line 178
Unable to ...The yPlus utility does not seem to work with twoPhaseEulerFoam or reactingTwoPhaseEulerFoam.
--> FOAM Warning :
From function virtual bool Foam::functionObjects::yPlus::execute()
in file yPlus/yPlus.C at line 178
Unable to find turbulence model in the database: yPlus will not be calculated
yPlus yPlus write:
writing field yPlus
patch walls y+ : min = 0, max = 0, average = 0
To reproduce the error:
twoPhaseEulerFoam -postProcess -func yPlus
in the RAS/bubbleColumn tutorial
I am using OpenFoam 1706 on Ubuntu 14.04https://develop.openfoam.com/Development/ThirdParty-common/-/issues/28no mpicc on cray2017-12-18T10:05:26ZMark OLESENno mpicc on cray- the cray `cc` handles mpi paths- the cray `cc` handles mpi pathsv1712Mark OLESENMark OLESEN2017-12-18https://develop.openfoam.com/Development/openfoam/-/issues/666Include additional packs in foamConfigurePaths2017-12-21T16:02:06ZRoger AlmenarInclude additional packs in foamConfigurePathsSome packages are missing:
-KaHIP
-gperftoolsSome packages are missing:
-KaHIP
-gperftoolsv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/665description to overset solvers needs update2021-07-06T11:29:29ZMatej Formandescription to overset solvers needs updateDescription to all overset solvers is not updated to mention overset mesh,
but features mesh refinement and topology changes to the mesh as it was copied from DyM version of solver.
Will result in misleading description in Doxygen.Description to all overset solvers is not updated to mention overset mesh,
but features mesh refinement and topology changes to the mesh as it was copied from DyM version of solver.
Will result in misleading description in Doxygen.v1712https://develop.openfoam.com/Development/openfoam/-/issues/664BUG: overset hole cutting not correct in parallel2021-07-08T21:46:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comBUG: overset hole cutting not correct in parallelincompressible/overPimpleDyMFoam/simpleRotor with attached controlDict and decomposePar produces incorrect hole cutting at time Time = 0.00478355:
```
calculated : 196
instead of say
calculated : 1281
```
[controlDict](/uplo...incompressible/overPimpleDyMFoam/simpleRotor with attached controlDict and decomposePar produces incorrect hole cutting at time Time = 0.00478355:
```
calculated : 196
instead of say
calculated : 1281
```
[controlDict](/uploads/770c830ac0284f22ea518396552b6e7e/controlDict)[decomposeParDict](/uploads/4c71bc99ad6b1c94eb7886c4f3f60778/decomposeParDict)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com