Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-11-21T15:40:58Zhttps://develop.openfoam.com/Development/openfoam/-/issues/627wcleanPlatform -c does not work2017-11-21T15:40:58ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwcleanPlatform -c does not work```
wcleanPlatform -c
1 platform(s) to clean
/home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/wmake/wcleanPlatform: line 124: [: too many arguments
'linux64GccDPInt32Opt' - not built
``````
wcleanPlatform -c
1 platform(s) to clean
/home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/wmake/wcleanPlatform: line 124: [: too many arguments
'linux64GccDPInt32Opt' - not built
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/626restart snappyHexMesh not possible after snapping2017-12-18T05:15:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrestart snappyHexMesh not possible after snappingshm insists on running at least one iteration of e.g. interface refinement so if you are running shm with patch-face merging (= changes hexes into other shapes) it might crash if this triggers refinement of those cells.shm insists on running at least one iteration of e.g. interface refinement so if you are running shm with patch-face merging (= changes hexes into other shapes) it might crash if this triggers refinement of those cells.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/625single precision reading does not handle 1e-39 or lower2017-12-18T23:14:30ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsingle precision reading does not handle 1e-39 or lowerin v1706 this does work - it underflows and truncates to 0.
This is used when generating meshes in double precision but then running with single precision.
Replicate: change on e.g. cavity one of the points in constant/polyMesh/points ...in v1706 this does work - it underflows and truncates to 0.
This is used when generating meshes in double precision but then running with single precision.
Replicate: change on e.g. cavity one of the points in constant/polyMesh/points to
(0.01 1e-39 0)
and run e.g. checkMesh. Will produce error
```
--> FOAM FATAL IO ERROR:
Attempt to get back from bad stream
file: /home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/tutorials/incompressible/icoFoam/cavity/cavity/constant/polyMesh/points at line 23.
From function bool Foam::Istream::getBack(Foam::token&)
in file db/IOstreams/IOstreams/Istream.C at line 56.
FOAM aborting (FOAM_ABORT set)
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/624redistributePar -decompose with constraint2017-10-26T08:11:58ZvilfayeauredistributePar -decompose with constraintHallo,
redistributePar -decompose doesn't work with constraint (see log.redistributePar.cosntraint). I have run incompressible/pimpleDyMFoam/mixerVesselAMI2D with
singleProcessorFaceSets ((AMI -1));
without the constraint, it works (l...Hallo,
redistributePar -decompose doesn't work with constraint (see log.redistributePar.cosntraint). I have run incompressible/pimpleDyMFoam/mixerVesselAMI2D with
singleProcessorFaceSets ((AMI -1));
without the constraint, it works (log.redistributePar) and with decomposePar (log.decomposePAR) as well.
[log.redistributePar](/uploads/ad946e316e6163d61763f9efe35edf92/log.redistributePar)
[log.decomposePar](/uploads/685c9b10211d119170a0ad489a11222b/log.decomposePar)
[log.redistributePar.constraint](/uploads/bbd09943dce20616581eee277db9a92a/log.redistributePar.constraint)
Best,
Sebastienhttps://develop.openfoam.com/Development/openfoam/-/issues/623paraview/parafoam not running in docker container2019-01-08T16:25:01ZAdminparaview/parafoam not running in docker containerI am trying to use the version of openFoam supplied to run in a docker container.
In my hands, paraFoam/paraview stops with the following message:
```
bash-4.2$ paraview
This application failed to start because it could not find or lo...I am trying to use the version of openFoam supplied to run in a docker container.
In my hands, paraFoam/paraview stops with the following message:
```
bash-4.2$ paraview
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".
Reinstalling the application may fix this problem.
Aborted (core dumped)
```
But reinstalling did not solve the problem.
My versions are:
```
Ubuntu: 1604 LTS
openFoam: v_1706
docker: Docker version 1.12.6, build 78d1802
```
And from inside the Docker container
```
bash-4.2$: qmake -v
QMake version 3.1
Using Qt version 5.9.0 in /home/buzz2/pawan/OpenFOAM/ThirdParty-1706-docker/platforms/linux64Gcc/qt-5.9.0/lib
```
Some docs say that with QT5 the "platforms" directory should be put next to the executable.
How do I make this ? Tank-you and sorry if this is not the right place to ask.https://develop.openfoam.com/Development/openfoam/-/issues/620multiLevelCoeffs entry should not be optional2019-12-09T22:11:26ZMark OLESENmultiLevelCoeffs entry should not be optionalif the `multiLevelCoeffs` entry is missing, using `optionalSubDict()` results in it using the top-level dictionary, which will immediately fail (eg, trying to interpret `numberOfSubdomains` as a sub-dictionary entry).
Bug introduced by ...if the `multiLevelCoeffs` entry is missing, using `optionalSubDict()` results in it using the top-level dictionary, which will immediately fail (eg, trying to interpret `numberOfSubdomains` as a sub-dictionary entry).
Bug introduced by 9801c2578Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/619multilevel decomposition fails2019-12-09T22:11:26ZMark OLESENmultilevel decomposition fails@Mattijs@Mattijsv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/618Error in calculation of tensor eigenvalues2018-11-27T13:36:32ZAdminError in calculation of tensor eigenvaluesUsing OpenFOAM 1706, with pimpleFoam, and the turbulentDFSEMInlet boundary condition, defined for velocity as below.
inlet
{
type turbulentDFSEMInlet;
value uniform (0 18 0);
delta ...Using OpenFOAM 1706, with pimpleFoam, and the turbulentDFSEMInlet boundary condition, defined for velocity as below.
inlet
{
type turbulentDFSEMInlet;
value uniform (0 18 0);
delta 1;
R uniform (3.2 0.1 0.1 3.2 0.1 3.2);
L uniform 10;
U uniform (0 10 0);
mapMethod nearestCell;
}
Results in warning:
--> FOAM Warning :
From function Foam::vector Foam::eigenValues(const tensor&)
in file primitives/Tensor/tensor/tensor.C at line 100
Complex eigenvalues detected for tensor: (3.2 0.1 0.1 0.1 3.2 0.1 0.1 0.1 3.2)
However, eigenvalues of this tensor are real (3.1, 3.1, 3.4).
The code in tensor.C appears correct, so I suspect the problem may lie in the cubicEqn code, which is significantly more opaque.Kutalmış BerçinKutalmış Berçin2018-12-31https://develop.openfoam.com/Development/openfoam/-/issues/617label overflow in checkMesh2020-01-03T11:18:24ZMark OLESENlabel overflow in checkMeshIn checkMesh:
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/applications/utilities/mesh/manipulation/checkMesh/checkTools.C#L107
I don't see why we have `scalar(nFaces + nIntFaces)` instead of just `scalar(nFaces)...In checkMesh:
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/applications/utilities/mesh/manipulation/checkMesh/checkTools.C#L107
I don't see why we have `scalar(nFaces + nIntFaces)` instead of just `scalar(nFaces)`. However, it this is intended, it should probably be formulated as `(scalar(nFaces) + scalar(nIntFaces))` to avoid label overflow.
partial reference from EP#482
@PrashantMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/616surfaceFeatureExtract crashes on zero-length edges2020-03-16T20:32:24ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsurfaceFeatureExtract crashes on zero-length edges[bjoern.obj](/uploads/61e9e5663b25d0a97bccd9cd41092430/bjoern.obj)[bjoern.obj](/uploads/61e9e5663b25d0a97bccd9cd41092430/bjoern.obj)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/615rhoCentralDyMFoam with Tadmor scheme crashes on orientedType2018-07-02T16:19:42ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrhoCentralDyMFoam with Tadmor scheme crashes on orientedTypecompressible/rhoCentralFoam/obliqueShock with Tadmor flux scheme crashes.compressible/rhoCentralFoam/obliqueShock with Tadmor flux scheme crashes.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/614runnning with dummy Pstream library does not have pthread dependency2020-04-06T10:37:45ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrunnning with dummy Pstream library does not have pthread dependencyFor now add it to dummy/Pstream dependency (since libOSspecific is not a shared library)For now add it to dummy/Pstream dependency (since libOSspecific is not a shared library)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/613foamToEnsight in parallel leaks memory2019-06-28T09:55:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamToEnsight in parallel leaks memoryRunning foamToEnsight -parallel produces under valgrind:
==4371== 88 bytes in 1 blocks are possibly lost in loss record 164 of 225
==4371== at 0x4C2B537: operator new[](unsigned long) (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-...Running foamToEnsight -parallel produces under valgrind:
==4371== 88 bytes in 1 blocks are possibly lost in loss record 164 of 225
==4371== at 0x4C2B537: operator new[](unsigned long) (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==4371== by 0x47332A: Foam::hashedWordList::hashedWordList(std::initializer_list<Foam::word>) (in /home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/platforms/linux64GccDPInt32Opt/bin/foamToEnsight)
==4371== by 0x44F003: main (in /home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/platforms/linux64GccDPInt32Opt/bin/foamToEnsight)
Error doesn't seem to be there non-parallel!Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/612CodedSource<Type>::description() contains space2020-01-03T11:13:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comCodedSource<Type>::description() contains spaceMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/611incorrect format on VTK xml output2019-12-09T22:11:26ZMark OLESENincorrect format on VTK xml outputThe face writer emits `ASCII` and `BINARY` instead of `ascii` and `binary`The face writer emits `ASCII` and `BINARY` instead of `ascii` and `binary`Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/609I/O problem on cluster with multiple nods2017-12-18T05:18:24ZAdminI/O problem on cluster with multiple nodsHi,
I want to report some error connected with the parallel running of fireFoam on salomon cluster (https://docs.it4i.cz/salomon/introduction). When I am using fireFoam (10M of cells) in parallel mode on one node everything is OK. But w...Hi,
I want to report some error connected with the parallel running of fireFoam on salomon cluster (https://docs.it4i.cz/salomon/introduction). When I am using fireFoam (10M of cells) in parallel mode on one node everything is OK. But when I try to run the same case on multiple nodes I get following error
[288] --> FOAM FATAL IO ERROR:
[288] error in IOstream "IOstream" for operation Foam::Istream &Foam::operator>>(Foam::Istream &, Foam::List<T> &) [with T = Foam::Vector<double>]
[288]
[288] file: IOstream at line 0.
[288]
[288] From function void Foam::IOstream::fatalCheck(const char *) const
[288] in file db/IOstreams/IOstreams/IOstream.C at line 109.
[288]
FOAM parallel run exiting
[288]
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 288
The error message usually depends on number of nodes. I am using OpenFOAM-v1706 translated with intel compiler 2017 and intel mpi library.
I want to ask you if you have met similar error.
With regards
Vojtech Betakhttps://develop.openfoam.com/Development/openfoam/-/issues/608stitchMesh doesn't work with restart2017-12-18T23:12:46ZMark OLESENstitchMesh doesn't work with restartCross-reference EP#313. EP#444Cross-reference EP#313. EP#444v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/607missing handling of various C++ suffixes2017-10-02T07:48:32ZMark OLESENmissing handling of various C++ suffixesAssociated with commit bc5134a55e the handling of all C++ suffixes other than `.C` was dropped.
The corresponding compiler rules still exist. But since they can be never triggered, makes it impossible to use the wmake framework for arbi...Associated with commit bc5134a55e the handling of all C++ suffixes other than `.C` was dropped.
The corresponding compiler rules still exist. But since they can be never triggered, makes it impossible to use the wmake framework for arbitrary bits of C++ code.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/605redistributePar does not distribute clouds correctly2020-01-03T10:04:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar does not distribute clouds correctlyhttps://develop.openfoam.com/Development/openfoam/-/issues/604BUG: class header incorrect for writeObject - anywrite2017-12-18T05:20:13ZPrashant SonakarBUG: class header incorrect for writeObject - anywriteRefer EP#516Refer EP#516v1712AdminAdmin