Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-05-29T05:39:49Zhttps://develop.openfoam.com/Development/openfoam/-/issues/319BUG: surfaceNormalFixedValue BC fails during redistributePar2018-05-29T05:39:49ZPrashant SonakarBUG: surfaceNormalFixedValue BC fails during redistributeParAttached a simple case replicating the issue.
[pitzDaily.tgz](/uploads/2d153a0aeba7112ece8642a067912ddc/pitzDaily.tgz)Attached a simple case replicating the issue.
[pitzDaily.tgz](/uploads/2d153a0aeba7112ece8642a067912ddc/pitzDaily.tgz)Version v1612Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/60BUG: surfaceRedistributePar with alternate decomposeparDict argument2019-12-09T22:04:14ZPrashant SonakarBUG: surfaceRedistributePar with alternate decomposeparDict argumentFrom @Roger
It seems the application surfaceRedistributePar ignores any
decomposeParDict other than the standard system/decomposeParDict.
@andy From @Roger
It seems the application surfaceRedistributePar ignores any
decomposeParDict other than the standard system/decomposeParDict.
@andy Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/21BUG: syntax correction in fieldCoordinateSystemTransform2016-04-25T10:52:55ZPrashant SonakarBUG: syntax correction in fieldCoordinateSystemTransformPlease correct the syntax in header as well as postProcessingDict file as per attached example
[functionObjects.fieldCoordinateSystemTransform](/uploads/a74c5adc2a66862259257dafbce04ed2/functionObjects.fieldCoordinateSystemTransform)
...Please correct the syntax in header as well as postProcessingDict file as per attached example
[functionObjects.fieldCoordinateSystemTransform](/uploads/a74c5adc2a66862259257dafbce04ed2/functionObjects.fieldCoordinateSystemTransform)
@andy
Functionality migration from internal development lineMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/2655BUG: thermalShell: only T-min/max of the main processor is reported for paral...2022-12-14T11:30:56ZKutalmış BerçinBUG: thermalShell: only T-min/max of the main processor is reported for parallel cases```
Info<< "T min/max = " << min(T_) << ", " << max(T_) << endl;
```
[thermalShell.C#L181](https://develop.openfoam.com/Development/openfoam/-/blob/develop/src/regionFaModels/thermalShell/thermalShell.C#L181)```
Info<< "T min/max = " << min(T_) << ", " << max(T_) << endl;
```
[thermalShell.C#L181](https://develop.openfoam.com/Development/openfoam/-/blob/develop/src/regionFaModels/thermalShell/thermalShell.C#L181)Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2377BUG: timeActivatedFileUpdate check on non-master2022-02-24T16:31:22ZMark OLESENBUG: timeActivatedFileUpdate check on non-masterduring startup it checks the file existence on all processes, but the source is usually normally only present on the master.
In the best case, this faulty logic causes excessive filesystem queries. In the worst case, it will abort due to...during startup it checks the file existence on all processes, but the source is usually normally only present on the master.
In the best case, this faulty logic causes excessive filesystem queries. In the worst case, it will abort due to missing file on the non-master processes.
cross-ref: EP1839Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2986BUG: timeActivatedFileUpdate: File state is not changed2023-09-19T16:00:52ZKutalmış BerçinBUG: timeActivatedFileUpdate: File state is not changed[2986-test.zip](/uploads/30a1159a8ff0c08f461ccafc8b4081a1/2986-test.zip) shows that [`fileHandler().getState(watchIndices_[i])`](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/OpenFOAM/db/regIOobject/regIOobjectRead....[2986-test.zip](/uploads/30a1159a8ff0c08f461ccafc8b4081a1/2986-test.zip) shows that [`fileHandler().getState(watchIndices_[i])`](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/OpenFOAM/db/regIOobject/regIOobjectRead.C#L241) returns `0` (i.e. `fileMonitor::UNMODIFIED`).
If the following is added into the `controlDict::functions`, `fileHandler().getState(watchIndices_[i])` correctly returns `1`:
```
sleep
{
type coded;
libs (utilityFunctionObjects);
name sleep;
codeExecute #{ sleep(0.00001); #};
}
```
133149a1ddKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/42BUG: [to be re-confirmed] : empty directory when using ThirdParty within Open...2019-01-09T10:15:33ZPrashant SonakarBUG: [to be re-confirmed] : empty directory when using ThirdParty within OpenFOAM installation folderWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markWhen TP is linked in OpenFOAM directory, Allwmake creates empty directory in OpenFOAM folder
build/linux64Gcc48DPInt32Opt/ThirdParty/kahip-2.00
Issue was noted during release, need to reconfirm.
@markhttps://develop.openfoam.com/Development/openfoam/-/issues/276BUG: triangle intersection problem with rays in plane of triangle2021-07-06T10:46:34ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comBUG: triangle intersection problem with rays in plane of triangletriangle: (0.00084175 -0.0104928 -0.0555556) (0.00252526 -0.0104928 -0.0555556) (0.00084175 8.97416e-19 -0.0625)
ray:
start: (0.0143097 8.73202e-19 -0.0625)
end: (0.0126263 8.76229e-19 -0.0625)
finds intersection at
(0.00084175 1.7...triangle: (0.00084175 -0.0104928 -0.0555556) (0.00252526 -0.0104928 -0.0555556) (0.00084175 8.97416e-19 -0.0625)
ray:
start: (0.0143097 8.73202e-19 -0.0625)
end: (0.0126263 8.76229e-19 -0.0625)
finds intersection at
(0.00084175 1.73472e-18 -0.0625)
since the determinant (volume) of the intersection is -3.53881e-26 which is below the cutoff point (ROOTVSMALL) but still too small to accurately determine the intersection.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/225BUG: triSurface IO operators are asymmetrical2019-12-09T22:04:11ZMark OLESENBUG: triSurface IO operators are asymmetricalAlso reported as http://bugs.openfoam.org/view.php?id=2188
The operator<<(Ostream&, const triSurface&) writes patches, points, faces.
However, the operator>>(Istream&, triSurface&) does not exist, and it resolves to operator>>(Istr...Also reported as http://bugs.openfoam.org/view.php?id=2188
The operator<<(Ostream&, const triSurface&) writes patches, points, faces.
However, the operator>>(Istream&, triSurface&) does not exist, and it resolves to operator>>(Istream&, List<labelledTri>&) via the PrimitivePatch parent.
This operator only reads faces.
The simple change would be to add an operator>>(Istream&, triSurface&) that delegates to the triSurface::read(Istream&) method.
@MattijsVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2132BUG: turbulenceFields: Local omega funcs are unused2021-08-04T13:32:32ZKutalmış BerçinBUG: turbulenceFields: Local omega funcs are unused<!--
*** 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 -->
- turbulenceFields.C#L185-188
```
case cfOmega:
{
processField<scalar>(f, omega(model));
break;
}
```
calls the `omega` of `turbulenceFields` rather than `model.omega()`.
- Another issue is that using `simulationType laminar;`, albeit unrealistic, unforgivingly throws fatal error - ceasing simulation.
- Also, the `nuTilda` expression of `turbulenceFields` is incorrect. `nuTilda` is not equal to `k/omega`:
```
template<class Model>
Foam::tmp<Foam::volScalarField>
Foam::functionObjects::turbulenceFields::nuTilda
(
const Model& model
) const
{
return tmp<volScalarField>::New
(
"nuTilda.tmp",
model.k()/omega(model)
);
}
```
### 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
-->
```
base1 = develop
api = 2106
patch = 0
HEAD = 3825c4ee95
version = com
compiler = Clang (system)
= clang version 9.0.1
mpi = SYSTEMOPENMPI
= mpirun (Open MPI) 1.10.7.0.5e373bf1fd
OS = Description: openSUSE Leap 15.1
opts = linux64ClangDPInt32Opt
```v2112Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1107BUG: turbulentDFSEMInlet; Option = planarInterpolation; decomposePar causes F...2019-11-06T18:38:30ZKutalmış BerçinBUG: turbulentDFSEMInlet; Option = planarInterpolation; decomposePar causes Floating Point Exception for Fields R/L/U### Summary
When `turbulentDFSEMInlet` with `planarInterpolation` option is ON, `decomposePar` causes FPE with the following error message:
```
Time = 0
Turbulent DFSEM patch inlet: interpolating field R from "/home/snoopy2/kuta/OpenFO...### Summary
When `turbulentDFSEMInlet` with `planarInterpolation` option is ON, `decomposePar` causes FPE with the following error message:
```
Time = 0
Turbulent DFSEM patch inlet: interpolating field R from "/home/snoopy2/kuta/OpenFOAM/kuta-v1806/run/channel395DFSEM/constant/boundaryData/inlet/0/R"
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2 ? in /lib64/libc.so.6
#3 Foam::pointToPointPlanarInterpolation::calcCoordinateSystem(Foam::Field<Foam::Vector<double> > const&) const at ??:?
#4 Foam::pointToPointPlanarInterpolation::pointToPointPlanarInterpolation(Foam::Field<Foam::Vector<double> > const&, Foam::Field<Foam::Vector<double> > const&, double, bool) at ??:?
#5 Foam::turbulentDFSEMInletFvPatchVectorField::patchMapper() const at ??:?
#6 Foam::tmp<Foam::Field<Foam::SymmTensor<double> > > Foam::turbulentDFSEMInletFvPatchVectorField::interpolateBoundaryData<Foam::SymmTensor<double> >(Foam::word const&) const at ??:?
#7 Foam::turbulentDFSEMInletFvPatchVectorField::turbulentDFSEMInletFvPatchVectorField(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#8 Foam::fvPatchField<Foam::Vector<double> >::adddictionaryConstructorToTable<Foam::turbulentDFSEMInletFvPatchVectorField>::New(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#9 Foam::fvPatchField<Foam::Vector<double> >::New(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#10 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::Boundary::readField(Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#11 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::readFields(Foam::dictionary const&) at ??:?
#12 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::readFields() at ??:?
#13 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::GeometricField(Foam::IOobject const&, Foam::fvMesh const&, bool) at ??:?
#14 ? at ??:?
#15 ? at ??:?
#16 __libc_start_main in /lib64/libc.so.6
#17 ? at /home/abuild/rpmbuild/BUILD/glibc-2.18/csu/../sysdeps/x86_64/start.S:125
Floating point exception
```
### Steps to reproduce
Please consider `tutorials/incompressible/pimpleFoam/LES/channel395DFSEM` case.
Change the following under `0/U`:
```
inlet
{
type turbulentDFSEMInlet;
...
mapMethod nearestCell;
...
}
```
to
```
inlet
{
type turbulentDFSEMInlet;
...
mapMethod planarInterpolation;
...
}
```
Then execute the following respectively:
`blockMesh`
`decomposePar`
PS: `scotch` and `hierarchial` were tested with various numbers of `numberOfSubdomains`.
@andyv1906Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2089BUG: turbulentDFSEMInlet: wrong operator in checkStresses function2021-06-09T13:47:40ZKutalmış BerçinBUG: turbulentDFSEMInlet: wrong operator in checkStresses function### Summary
<!-- Summarize the bug encountered concisely -->
In [L1003](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/finiteVolume/fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorF...### Summary
<!-- Summarize the bug encountered concisely -->
In [L1003](https://develop.openfoam.com/Development/openfoam/-/blob/master/src/finiteVolume/fields/fvPatchFields/derived/turbulentDFSEMInlet/turbulentDFSEMInletFvPatchVectorField.C#L1003), the relevant term `*a_yy` should be `/a_yy`.
The bug was found by Ole Meyer, @h2o_meyer.v2106Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2329BUG: turbulentDigitalFilterInlet: Forward-stepwise option is inoperative2022-06-07T20:17:09ZKutalmış BerçinBUG: turbulentDigitalFilterInlet: Forward-stepwise option is inoperative<!--
*** 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
In `turbulentDigitalFilterInletFvPatchVectorField.C`, the following assignment operation is inoperative:
```
for (direction dir = 0; dir < pTraits<vector>::nComponents; ++dir)
{
U.component(dir) =
U0_.component(dir)*coeffs1FSM_[dir]
+ U.component(dir)*coeffs2FSM_[dir];
}
```
The LHS `U.component(dir) = ` is unassignable; therefore, the content of `U` has never been altered by the intended RHS operations.
For this reason, `DFM` was acting as a single-cell box rather than the `FSM` simplifications are in effect.
This situation should have adverse effects on integral scale syntheses (which is luckily not considerably important), and should not have any effect on Reynolds stresses or mean quantities.
### 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
-->
base0 = base
base1 = develop
api = 2112
patch = 0
HEAD = befbcfce24
version = com
compiler = Clang (system)
= clang version 9.0.1
mpi = SYSTEMOPENMPI
= mpirun (Open MPI) 1.10.7.0.5e373bf1fd
OS = Description: openSUSE Leap 15.3
opts = linux64ClangDPInt32Opt
### 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
-->
```
for (direction dir = 0; dir < pTraits<vector>::nComponents; ++dir)
{
U.replace
(
dir,
U0.component(dir)*coeffs1FSM_[dir] + U.component(dir)*coeffs2FSM_[dir]
);
}
```v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/141BUG: Tutorial case failure2023-12-07T19:01:57ZPrashant SonakarBUG: Tutorial case failureMultiphase:
- reactingTwoPhaseEulerFoam/RAS/wallBoiling
- reactingTwoPhaseEulerFoam/laminar/fluidisedBed
- reactingTwoPhaseEulerFoam/laminar/mixerVessel2D
combustion
- fireFoam/les/oppositeBurningPanels (missing boundaryRadiationP...Multiphase:
- reactingTwoPhaseEulerFoam/RAS/wallBoiling
- reactingTwoPhaseEulerFoam/laminar/fluidisedBed
- reactingTwoPhaseEulerFoam/laminar/mixerVessel2D
combustion
- fireFoam/les/oppositeBurningPanels (missing boundaryRadiationProperties file)
heatTransfer
- chtMultiRegionFoam/windshieldDefrost
incompressible
- simpleFoam/rotorDisk (snappyHexMesh failure)
lagrangian
-MPPICFoam/column (undefined applyLimiting)
- MPPICFoam/cyclone (undefined applyLimiting, Allrun parallel compatible command)
- icoUncoupledKinematicParcelFoam/hopper/hopper* (undefined flux(U) )
mesh
- parallel/cavity/log.redistributePar.reconstruct
- foamyHexMesh/simpleShapes/log.surfaceBooleanFeatures (issue #124)
@Sergio @Mattijs AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/61BUG: Tutorial case failure: multiphase/interDyMFoam/ras/motorBike2016-02-05T05:25:05ZPrashant SonakarBUG: Tutorial case failure: multiphase/interDyMFoam/ras/motorBikeThe restarted interDyMFoam job fails.
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/multiphase/interDyMFoam/ras/motorBike/log.interDyMFoam_restart
@andy @Sergio The restarted interDyMFoam job fails.
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/multiphase/interDyMFoam/ras/motorBike/log.interDyMFoam_restart
@andy @Sergio Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/651bug : tutorial failure2018-01-08T15:19:52ZAdminbug : tutorial failuretutorials/heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
Failing in latest develop
[log.chtMultiRegionFoam](/uploads/454c0747c05d70b308d39da5fa7182d9/log.chtMultiRegionFoam)
@marktutorials/heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
Failing in latest develop
[log.chtMultiRegionFoam](/uploads/454c0747c05d70b308d39da5fa7182d9/log.chtMultiRegionFoam)
@markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/499BUG? tutorials/heatTransfer/chtMultiRegionFoam/externalSolarLoad-parallel2017-06-19T19:43:57ZPrashant SonakarBUG? tutorials/heatTransfer/chtMultiRegionFoam/externalSolarLoad-parallelThe tutorial when tried in parallel failed attached script.
[Allrun](/uploads/135d01d12be71db5fd0b074c3ac48ddc/Allrun)
```
[1]
[1] --> FOAM FATAL IO ERROR:
[1] cannot find file
[1]
[1] file: /hosts/xxx/externalSolarLoad-parallel/proc...The tutorial when tried in parallel failed attached script.
[Allrun](/uploads/135d01d12be71db5fd0b074c3ac48ddc/Allrun)
```
[1]
[1] --> FOAM FATAL IO ERROR:
[1] cannot find file
[1]
[1] file: /hosts/xxx/externalSolarLoad-parallel/processor1/constant/air/mapDist at line 0.
```
@andyVersion v1706Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/571BUG: Unable to create a List from a SLList2019-12-09T22:11:26ZAdminBUG: Unable to create a List from a SLListOn beahlf of @hjasak
The following code fails
```
int main(int argc, char *argv[])
{
SLList<label> a;
List<label> b(a);
return 0;
}
```
With the error message
```
src/OpenFOAM/lnInclude/ListI.H:94:35: error: invalid type a...On beahlf of @hjasak
The following code fails
```
int main(int argc, char *argv[])
{
SLList<label> a;
List<label> b(a);
return 0;
}
```
With the error message
```
src/OpenFOAM/lnInclude/ListI.H:94:35: error: invalid type argument of unary '*' (have 'int')
this->operator[](i) = *iter;
```v1712AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/52BUG: Unit test failed for kOmegaSSTDES2016-01-07T09:31:26ZPrashant SonakarBUG: Unit test failed for kOmegaSSTDESCould you please test
turbulenceModels/compressible/LES/pitzDaily from unit tests repository?
It seems to report unconfirmed completion
@andy @Mattijs Could you please test
turbulenceModels/compressible/LES/pitzDaily from unit tests repository?
It seems to report unconfirmed completion
@andy @Mattijs Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/340BUG: Unit test failures - 13.12.20162018-05-29T05:39:49ZPrashant SonakarBUG: Unit test failures - 13.12.2016Unknown dynamicFvMesh type solidBodyMotionFvMesh
* incompressible/pimpleDyMFoam/oscillatingInletPeriodicAMI2D - pimpleDyMFoam failed
* combustion/XiDyMFoam/annularCombustorTurbine - XiDyMFoam failed
keyword position is undefined, runTi...Unknown dynamicFvMesh type solidBodyMotionFvMesh
* incompressible/pimpleDyMFoam/oscillatingInletPeriodicAMI2D - pimpleDyMFoam failed
* combustion/XiDyMFoam/annularCombustorTurbine - XiDyMFoam failed
keyword position is undefined, runTimePP FO
* incompressible/pisoFoam/LES/motorBike/motorBike -simpleFoam failed
pointProcAddressing missing - Add reconstructParMesh before constructing data
* multiphase/interFoam/RAS/DTCHull - reconstructPar failed
* multiphase/interDyMFoam/RAS/DTCHull - reconstructPar failed
#339
#336
@internalVersion v1612Sergio FerrarisSergio Ferraris