Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-06-20T12:06:29Zhttps://develop.openfoam.com/Development/openfoam/-/issues/888bad indexing in regionSizeDistribution function object2018-06-20T12:06:29ZMark OLESENbad indexing in regionSizeDistribution function objectnoted by @Prashantnoted by @Prashantv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/416minor spelling in scalarTransport.C2019-12-09T21:29:27ZAdminminor spelling in scalarTransport.CI am guessing that in scalarTransport.C (in OpenFOAM-v1612+/src/functionObjects/solvers/scalarTransport), the variable
"limitedPhiAlpa" is supposed to be "limitedPhiAlpha" (i.e. "h" is missing), right!?I am guessing that in scalarTransport.C (in OpenFOAM-v1612+/src/functionObjects/solvers/scalarTransport), the variable
"limitedPhiAlpa" is supposed to be "limitedPhiAlpha" (i.e. "h" is missing), right!?https://develop.openfoam.com/Development/openfoam/-/issues/8BUG: graphics (runTimePostProcessing) compilation issue2023-08-19T21:13:19ZPrashant SonakarBUG: graphics (runTimePostProcessing) compilation issueDevelop branch fails to compile runTimePostprocessing.
/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop/log.allwmake_25Nov_IST0955
(line 5763)
@andy @Mattijs Develop branch fails to compile runTimePostprocessing.
/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop/log.allwmake_25Nov_IST0955
(line 5763)
@andy @Mattijs Functionality migration from internal development lineAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/136installation on ubuntu - flex version2016-06-06T10:17:11ZMatej Formaninstallation on ubuntu - flex versionOpenFOAM is checking for older version of flex then installed by default in Ubuntu.
Ubuntu 16.04 is using flex version 2.6.0-11
There is a solution https://openfoamwiki.net/index.php/Installation/Linux/OpenFOAM-3.0.1/Ubuntu
Step 10...OpenFOAM is checking for older version of flex then installed by default in Ubuntu.
Ubuntu 16.04 is using flex version 2.6.0-11
There is a solution https://openfoamwiki.net/index.php/Installation/Linux/OpenFOAM-3.0.1/Ubuntu
Step 10.
We should either add this step to the build guide: http://openfoam.com/code/build-guide.php
or suggest users to install flex-old package with version 2.5.4
Or do the changes in the source code for successful compilation.
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1080single precision fails for smallPoolFire3D2021-07-06T13:53:01ZAdminsingle precision fails for smallPoolFire3DI am trying to run fireFoam on the tutorials/combustion/fireFoam/LES/smallPoolFire3D case in single precision. The case fails. I've attached a log file for both fireFoam and checkMesh (which also fails). I've also attached my etc/bash...I am trying to run fireFoam on the tutorials/combustion/fireFoam/LES/smallPoolFire3D case in single precision. The case fails. I've attached a log file for both fireFoam and checkMesh (which also fails). I've also attached my etc/bashrc file. I am using OpenFOAM-v1806, commit 71942d682. For the record, smallPoolFire2D also fails.
[log.checkMesh](/uploads/cba325eede12734e3561ea56f5faed3c/log.checkMesh)
[log.fireFoam](/uploads/001c9a109a6eca12287dbba24d444255/log.fireFoam)
[bashrc](/uploads/794478bee3a54201abca07d8eda922e1/bashrc)
\#\# Reattaching the author to the issue ticket: @kvm \#\#https://develop.openfoam.com/Development/openfoam/-/issues/440Profiling does not correctly store data if two instances of profiling::Inform...2018-05-03T18:08:12ZAdminProfiling does not correctly store data if two instances of profiling::Information have the same nameIn cases where two profiling::Information-instances were created with the same name but different parents (for Example: energy-equation in a chtCase) only one was created and used for accounting the wrong parent. Which leads to strange/u...In cases where two profiling::Information-instances were created with the same name but different parents (for Example: energy-equation in a chtCase) only one was created and used for accounting the wrong parent. Which leads to strange/unusable profiling results because the parent might "believe" that more time was spent in its children (leading to negative "self"-times).
This patch is a port of the way it was implemented in the original profiling-patch (but there a STL-datastructure was used to make sure that profiling::Information ls looked for by name AND parent-ID. Now it uses a Foam-container)
[profilingFixSameNameDifferentParent.patch](/uploads/48de75cccf6e59d7822924bf674fd393/profilingFixSameNameDifferentParent.patch)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/50XiDyMFoam fails on oscillatingCylinder tutorial2016-01-05T22:37:13ZMatej FormanXiDyMFoam fails on oscillatingCylinder tutorialRunning tutorial $FOAM_TUTORIALS/combustion/XiDyMFoam/oscillatingCylinder.
@Prashant I have not found any note on this. Am I using wrong settings somewhere? I'm 200% positive I use dev version.
The run starts to fail at time: Time ...Running tutorial $FOAM_TUTORIALS/combustion/XiDyMFoam/oscillatingCylinder.
@Prashant I have not found any note on this. Am I using wrong settings somewhere? I'm 200% positive I use dev version.
The run starts to fail at time: Time = 0.0459441, where b starts to grow negative (see attached graph) - in the middle of the ignition time.
![plot_b](/uploads/9074b29869ce7161d07085a496ae7cf7/plot_b.png)
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/349BUG: Inconsistent library name in Header files2018-05-29T05:39:48ZPrashant SonakarBUG: Inconsistent library name in Header filesFollowing FO should have libfieldFunctionObjects.so in respective documentation header files.
- DESModelRegions/DESModelRegions.H
- PecletNo/PecletNo.H
- Q/Q.H
- vorticity/vorticity.H
- yPlus/yPlus.H
Similarly perhaps following also nee...Following FO should have libfieldFunctionObjects.so in respective documentation header files.
- DESModelRegions/DESModelRegions.H
- PecletNo/PecletNo.H
- Q/Q.H
- vorticity/vorticity.H
- yPlus/yPlus.H
Similarly perhaps following also need update
- src/functionObjects/lagrangian/cloudInfo/postProcessingDict
@andyVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/928Support user-independent build2020-03-16T14:24:57ZMark OLESENSupport user-independent buildWhen building for cluster installations the user prefs.sh and various config.sh/ files will be used, but this can lead to installations that are no longer properly portable.When building for cluster installations the user prefs.sh and various config.sh/ files will be used, but this can lead to installations that are no longer properly portable.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1220Updates for dense matrices2019-09-12T10:07:37ZMark OLESENUpdates for dense matricesThey are currently limited in functionalityThey are currently limited in functionalityKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1184turbulentDFSEM hangs at first PIMPLE iteration.2019-01-28T11:05:17ZAdminturbulentDFSEM hangs at first PIMPLE iteration.Hi,
I am trying to run with turbulentDFSEM boundary condition. I used the channel395DFSEM tutorial and modified the case.
First I tried to run with channel height for 0.8m with experimental data. The case didn't work and hangs at fir...Hi,
I am trying to run with turbulentDFSEM boundary condition. I used the channel395DFSEM tutorial and modified the case.
First I tried to run with channel height for 0.8m with experimental data. The case didn't work and hangs at first PIMPLE iteration. After many tries, It worked when I added boundary data for the whole height of the inlet.
Then I copied the same running case and modified for a channel height of 0.6m with different data. Even if I give boundary data for the whole height of the inlet, the case hangs at first PIMPLE iteration.
Both the cases can be found here.
[dfsem.zip](/uploads/8945d3bb7a778c518a58d7359353afab/dfsem.zip)
run blockMesh and then pimpleFoam to reproduce.
I am using OpenFOAM v1812. I tried running in serial and parallel. both didn't work for channel height of 0.6m.
This is similar to https://develop.openfoam.com/Development/OpenFOAM-plus/issues/894v1906Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/268BUG: distributedTriSurfaceMesh is always seen as an open geometry in snappyHe...2019-12-09T22:04:13ZAdminBUG: distributedTriSurfaceMesh is always seen as an open geometry in snappyHexMeshA distributedTriSurfaceMesh in snappyHexMesh cannot be used to define a cellZone using the cellZoneInside inside designation because snappyHexMesh sees the geometry as an open geometry. It works if you change it to triSurfaceMesh.A distributedTriSurfaceMesh in snappyHexMesh cannot be used to define a cellZone using the cellZoneInside inside designation because snappyHexMesh sees the geometry as an open geometry. It works if you change it to triSurfaceMesh.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/13Git: Download (GUI) doesn't work2023-08-19T21:13:19ZPrashant SonakarGit: Download (GUI) doesn't workGives error :
{"RepoPath":"/var/opt/gitlab/git-data/repositories/Development/OpenFOAM-dev-OpenCFD.git","ArchivePrefix":"OpenFOAM-dev-OpenCFD-develop-67c16ee5128f69ce99b221e104646222e16dd814","ArchivePath":"/var/opt/gitlab/gitlab-rails...Gives error :
{"RepoPath":"/var/opt/gitlab/git-data/repositories/Development/OpenFOAM-dev-OpenCFD.git","ArchivePrefix":"OpenFOAM-dev-OpenCFD-develop-67c16ee5128f69ce99b221e104646222e16dd814","ArchivePath":"/var/opt/gitlab/gitlab-rails/shared/cache/archive/OpenFOAM-dev-OpenCFD.git/OpenFOAM-dev-OpenCFD-develop-67c16ee5128f69ce99b221e104646222e16dd814.tar.bz2","CommitId":"67c16ee5128f69ce99b221e104646222e16dd814"}
However, the command line git clone works smoothly.
@Mattijs AdminAdminhttps://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/42paraview-4.4.0 install produces lib/paraview-3.0/, include/paraview-3.0 (inst...2016-10-01T08:55:40ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaview-4.4.0 install produces lib/paraview-3.0/, include/paraview-3.0 (instead of lib/paraview-4.4)The ./CMake/ParaViewDetermineVersion.cmake does a 'git describe' to find the current Paraview version. This recurses up and finds the ThirdParty/.git where 'git-describe' returns
version-3.0.0-7-g1e6453d
This path gets used to vers...The ./CMake/ParaViewDetermineVersion.cmake does a 'git describe' to find the current Paraview version. This recurses up and finds the ThirdParty/.git where 'git-describe' returns
version-3.0.0-7-g1e6453d
This path gets used to version the resulting files.
Workaround: build paraview not under a ThirdParty with a git. Or rename the resulting install directories.https://develop.openfoam.com/Development/openfoam/-/issues/895cellSet labelToCell (and labelToFace, labelToPoint) should check validity2018-07-22T16:58:47ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcellSet labelToCell (and labelToFace, labelToPoint) should check validityThe only manual input for sets (labelToXXX) should check for validity.The only manual input for sets (labelToXXX) should check for validity.https://develop.openfoam.com/Development/openfoam/-/issues/791time-control function object does not respect underlying function object2020-03-13T13:46:29ZMark OLESENtime-control function object does not respect underlying function objectWhen a function-object uses `timeStart`, `timeEnd` to control its activation, these values are used to define if execution or writing occurs, but can also mean that the underlying `end()` function is never called.
This can be problematic...When a function-object uses `timeStart`, `timeEnd` to control its activation, these values are used to define if execution or writing occurs, but can also mean that the underlying `end()` function is never called.
This can be problematic if the `end()` method is being used to free up resources.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/330periodic restart (eg, field-average) may exhibit odd behaviour when restartin...2018-05-29T05:39:48ZMark OLESENperiodic restart (eg, field-average) may exhibit odd behaviour when restarting a simulationThe constructor initializes with an index of 1, which is advanced by one during the calculation whenever a reset is triggered.
If the simulation is later restarted, the index 1 may not be appropriate - causing repeated resetting of the a...The constructor initializes with an index of 1, which is advanced by one during the calculation whenever a reset is triggered.
If the simulation is later restarted, the index 1 may not be appropriate - causing repeated resetting of the averaged values until the periodic interval 'catches up' to the current time.
@andy, @MattijsVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1083inconsistent handling of dimensioned types2018-11-26T20:53:03ZMark OLESENinconsistent handling of dimensioned typesIn `fixedPressureCompressibleDensityFvPatchScalarField`, for example, it grabs values from the thermodynamicProperties dictionary:
```
const scalar rholSat = dimensionedScalar(thermoProps.lookup("rholSat")).value();
```
The `dimensioned...In `fixedPressureCompressibleDensityFvPatchScalarField`, for example, it grabs values from the thermodynamicProperties dictionary:
```
const scalar rholSat = dimensionedScalar(thermoProps.lookup("rholSat")).value();
```
The `dimensioned(Istream&)` constructor forwards to `read(Istream&)` which requires name, dimensions, value.
In other locations (including in a tutorial example), these quantities are treated as if name, dimensions are optional.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1090decomposePar filters zero-sized fa (finiteArea) patches2019-12-09T22:37:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar filters zero-sized fa (finiteArea) patchesdecomposePar explicitly filters out zero-sized patches on faMeshes. Note that this used to be the behaviour for fvPatches as well. Likewise it is giving lots of issues if one is trying to do anything inside faPatches / faPatchFields.decomposePar explicitly filters out zero-sized patches on faMeshes. Note that this used to be the behaviour for fvPatches as well. Likewise it is giving lots of issues if one is trying to do anything inside faPatches / faPatchFields.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com