Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-06-29T20:38:03Zhttps://develop.openfoam.com/Development/openfoam/-/issues/493BUG: orientedFields using filteredLinear2017-06-29T20:38:03ZPrashant SonakarBUG: orientedFields using filteredLinearAttached example replicating issue in develop branch:
[pitzDaily.tgz](/uploads/2c470a8ed9fed00fc5e782d0134a7d91/pitzDaily.tgz)
@SergioAttached example replicating issue in develop branch:
[pitzDaily.tgz](/uploads/2c470a8ed9fed00fc5e782d0134a7d91/pitzDaily.tgz)
@SergioAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/717surfaceCheck output2020-01-03T14:21:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsurfaceCheck output1. it does not display the number of badquality triangles.
2. it has no way of visualising these (apart from surfaceSubset+Dict)
Attached start of adding writeSet option to surfaceCheck. This needs to be extended to output strings of ed...1. it does not display the number of badquality triangles.
2. it has no way of visualising these (apart from surfaceSubset+Dict)
Attached start of adding writeSet option to surfaceCheck. This needs to be extended to output strings of edges. See ep #703.
[surfaceCheck.C](/uploads/dfe8af4f901817396c6bf2ca6d67793e/surfaceCheck.C)
Typical output:
```
min 0 for triangle 110081
max 1 for triangle 985653
--> FOAM Warning :
From function int main(int, char**)
in file surfaceCheck.C at line 483
0. This might give problems in self-intersection testing later on.
Dumping bad quality faces to "badFaces"
```https://develop.openfoam.com/Development/openfoam/-/issues/236link/compilation error2016-09-19T05:32:30ZAdminlink/compilation errorI have got a compilation error on my Linux (Suse tumbleweed) machine (all the environmental variables are set correctly , etc.)
/home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/src/finiteVolume/fields/fvsPatchField...I have got a compilation error on my Linux (Suse tumbleweed) machine (all the environmental variables are set correctly , etc.)
/home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/src/finiteVolume/fields/fvsPatchFields/basic/calculated/calculatedFvsPatchFields.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
make: *** [/home/walter/OpenFOAM/OpenFOAM-v1606+/wmake/makefiles/general:157: /home/walter/OpenFOAM/OpenFOAM-v1606+/platforms/linux64GccDPInt32Opt/lib/libfiniteVolume.so] Error 1
Any clues ?
Thank You.https://develop.openfoam.com/Development/openfoam/-/issues/134UOPstream indexes out of bounds for non-white character filtering2016-06-02T13:02:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comUOPstream indexes out of bounds for non-white character filteringFrom code inspection it seems as if the non-white character filtering in C-style string writing indexes out of bounds.From code inspection it seems as if the non-white character filtering in C-style string writing indexes out of bounds.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/163decomposePar does not softlink uniform if no fields decomposed2022-11-24T14:58:22ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar does not softlink uniform if no fields decomposedIf there are no fields to decompose the destination time directory never gets created and the softlinks get created in the wrong location.
If there are no fields to decompose the destination time directory never gets created and the softlinks get created in the wrong location.
https://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/839collated fileHandler writes to processor0/../postProcessing which create proc...2021-07-06T12:53:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcollated fileHandler writes to processor0/../postProcessing which create processor0 directoryEverywhere it uses (in parallel)
time().path()/".."
it should use
time().rootPath()/time().globalCaseName()
This will avoid the processor0/..
E.g. streamLineBase.C, writeFile.C
```
cd $FOAM_SRC
git grep '"postProcessing"'
```Everywhere it uses (in parallel)
time().path()/".."
it should use
time().rootPath()/time().globalCaseName()
This will avoid the processor0/..
E.g. streamLineBase.C, writeFile.C
```
cd $FOAM_SRC
git grep '"postProcessing"'
```https://develop.openfoam.com/Development/openfoam/-/issues/103BUG: changeDictionary adds non-existing patches2016-04-21T14:10:04ZPrashant SonakarBUG: changeDictionary adds non-existing patcheschangeDictionary should modify boundary file only if there exists any patch/patchGroup etc...
[pitzDaily.tgz](/uploads/a4a1039b8c9e68916d1b79cc53f291f9/pitzDaily.tgz)
@andy changeDictionary should modify boundary file only if there exists any patch/patchGroup etc...
[pitzDaily.tgz](/uploads/a4a1039b8c9e68916d1b79cc53f291f9/pitzDaily.tgz)
@andy Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/476Absorptivity in constant/boundaryRadiationProperties (e.g. hotRadiationRoom)2017-05-18T16:12:16ZAdminAbsorptivity in constant/boundaryRadiationProperties (e.g. hotRadiationRoom)I guess the absorptivity in constant/boundaryRadiationProperties not to be used in this case.
I invalidated it and then executed this case, but no problems occurred.
Is this parameter really necessary to execute this case?
--
...I guess the absorptivity in constant/boundaryRadiationProperties not to be used in this case.
I invalidated it and then executed this case, but no problems occurred.
Is this parameter really necessary to execute this case?
--
Build: plus- e 6 c b e 0 b 1 1 9 2 3, v1606+https://develop.openfoam.com/Development/openfoam/-/issues/237Instructions that refer to the cavity case need to be updated2016-09-28T16:27:29ZAdminInstructions that refer to the cavity case need to be updatedI haven't checked them all, but at least the following two pages need updating:
* http://www.openfoam.com/download/install-windows.php
* http://www.openfoam.com/download/install-binary.php
The reason is that the tutorial `incompress...I haven't checked them all, but at least the following two pages need updating:
* http://www.openfoam.com/download/install-windows.php
* http://www.openfoam.com/download/install-binary.php
The reason is that the tutorial `incompressible/icoFoam/cavity` is now a group of cases and not a single case. You have at least two possibilities:
* Use the path `incompressible/icoFoam/cavity/cavity`
* Use the `Allrun` script, instead of `blockMesh`+`icoFoam`
For more details: http://bugs.openfoam.org/view.php?id=2149#c6527
----
Side note: I only spotted this while trying to answer a question on the forum: http://www.cfd-online.com/Forums/openfoam-installation/176161-openfoam-plus-v1606-compiling-installing-problems-2.html#post618348AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/393dynamicMotionSolver plays catch up when started from a non-zero time step2018-05-29T05:39:48ZAdmindynamicMotionSolver plays catch up when started from a non-zero time stepNot sure if this is a bug or a limitation. But when using the dynamic mesh rotating solid body functionality in interDyMFoam, the dynamic mesh will play catch up if started from a non-zero time step. In other words, if I run a simulation...Not sure if this is a bug or a limitation. But when using the dynamic mesh rotating solid body functionality in interDyMFoam, the dynamic mesh will play catch up if started from a non-zero time step. In other words, if I run a simulation for 0.5s without mesh motion (staticFvMesh), stop it, turn on mesh motion (dynamicMotionSolverFvMesh), and restart from the latestTime, the mesh will jump to the 0.5s position (as if it had already run for 0.5s) to begin the simulation rather than starting at the location where staticFvMesh left off. I did try different combinations of startTime and startFrom in the controlDict before the restart, but still couldn't get it to stop playing catch up.
I don't have a good quick test model for you yet, but the mixerVesselAMI tutorial I imagine could be modified to show this (even though it too takes a while to run).https://develop.openfoam.com/Development/openfoam/-/issues/356movingCone tutorial leaks memory in cuttingPlane2021-07-06T10:54:54ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commovingCone tutorial leaks memory in cuttingPlaneAttached output from
valgrind --leak-check=full --show-reachable=yes
[log.pimpleDyMFoam](/uploads/30fe839ab542c1f8866ec7867680490e/log.pimpleDyMFoam)Attached output from
valgrind --leak-check=full --show-reachable=yes
[log.pimpleDyMFoam](/uploads/30fe839ab542c1f8866ec7867680490e/log.pimpleDyMFoam)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/372test app test/mesh does not compile2019-12-09T21:29:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtest app test/mesh does not compilehttps://develop.openfoam.com/Development/openfoam/-/issues/250Merge points with indirect list.2019-12-09T22:04:13ZMark OLESENMerge points with indirect list.Should be able to merge a subset of points (e.g. only those on boundaries). Adjust merge points parameters list to handle this.
@MattijsShould be able to merge a subset of points (e.g. only those on boundaries). Adjust merge points parameters list to handle this.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/128BUG: runTimePostProcessing static Mode with nFrames >12023-12-07T19:01:57ZPrashant SonakarBUG: runTimePostProcessing static Mode with nFrames >1There should be warning /error if nFrames is >1 for static mode.
Else, the position_ would keep increasing. There should be warning /error if nFrames is >1 for static mode.
Else, the position_ would keep increasing. AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/399running oscillatingInletACMI2D under valgrind reports 'in use at exit: 2,172 ...2020-06-16T16:14:56ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrunning oscillatingInletACMI2D under valgrind reports 'in use at exit: 2,172 bytes in 6 blocks'Not sure if this is a real problem. Re-run with all the memory tracing.Not sure if this is a real problem. Re-run with all the memory tracing.https://develop.openfoam.com/Development/openfoam/-/issues/494BUG: postProcess utility fails when reading stl file2017-06-27T05:49:17ZPrashant SonakarBUG: postProcess utility fails when reading stl fileLexer issue while reading ASCII STL file
- postProcess utility fails when reading stl for runTimePostProcessing
- when Make/options is modified to remove compressibleTurbulence dependency, the same does work (probably conflict with l...Lexer issue while reading ASCII STL file
- postProcess utility fails when reading stl for runTimePostProcessing
- when Make/options is modified to remove compressibleTurbulence dependency, the same does work (probably conflict with lexer in chemkin)
reproducible with pisoFoam motorBike (stl geometry -> using surfaceConvert)..
@andy @Mattijs @SergioVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/964Wrong default instalation path in bashrc of openfoam in native windows 10 ver...2019-07-03T20:13:17ZAdminWrong default instalation path in bashrc of openfoam in native windows 10 versionWhen installing openfoam 1806 for Win10 using WSL, the guide at openfoam site said the default installation directory is /opt/. However, in bashrc of openfoam the default instalation directory is $HOME. This cause an error if user try to...When installing openfoam 1806 for Win10 using WSL, the guide at openfoam site said the default installation directory is /opt/. However, in bashrc of openfoam the default instalation directory is $HOME. This cause an error if user try to follow the guide from website and source the provided bashrc without modification.https://develop.openfoam.com/Development/openfoam/-/issues/439Checking to see if the function object is time-based sub-optimal2017-06-29T20:38:04ZAdminChecking to see if the function object is time-based sub-optimalIn `functionObjectList` explicit checks on whether the input dictionary includes the entries `writeControl` or `outputControl` are used to determine whether to instantiate a time-based or plain- function object. This misses local entrie...In `functionObjectList` explicit checks on whether the input dictionary includes the entries `writeControl` or `outputControl` are used to determine whether to instantiate a time-based or plain- function object. This misses local entries used by the `timeControl` class, e.g. `timeStart` and `timeEnd` which are independent of the `*Control` entries.
Suggest moving the logic into the class that knows whether or not the dict will be used to create a time-based function object (or not)Version v1706https://develop.openfoam.com/Development/openfoam/-/issues/1208dpdt uninitialized in basicThermo2024-01-11T16:59:35ZMark OLESENdpdt uninitialized in basicThermo- one constructor ignores the "dpdt" entry- one constructor ignores the "dpdt" entryMark OLESENMark OLESEN