Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-05-02T08:54:30Zhttps://develop.openfoam.com/Development/openfoam/-/issues/459BUG: forceCoeff not working in sonicFoam -> nacaAirfoil2017-05-02T08:54:30ZPrashant SonakarBUG: forceCoeff not working in sonicFoam -> nacaAirfoilcarried forward from https://develop.openfoam.com/Community/OpenFOAM-addOns/issues/4carried forward from https://develop.openfoam.com/Community/OpenFOAM-addOns/issues/4https://develop.openfoam.com/Development/openfoam/-/issues/632wrong entry in new tutorial vortexShed2017-11-07T10:52:27ZMatej Formanwrong entry in new tutorial vortexShedIn tutorial $FOAM_TUTORIALS/incompressible/pimpleFoam/LES/vortexShed
the noise utility dictionary for surface has wrong specification of the cutting plane.
file: system/noise-surface
it reads:
`file "postProcessing/cuttingPla...In tutorial $FOAM_TUTORIALS/incompressible/pimpleFoam/LES/vortexShed
the noise utility dictionary for surface has wrong specification of the cutting plane.
file: system/noise-surface
it reads:
`file "postProcessing/cuttingPlane/yNormal_0.0/yNormal_0.0.case";`
but should:
`file "postProcessing/cuttingPlane/zNormal/zNormal.case";`
to point to correct cutting plane.
would be nice to create Allrun.noise
to show how to get the noise data actuallyhttps://develop.openfoam.com/Development/openfoam/-/issues/47BUG: Failure in medium test2016-01-07T11:43:44ZPrashant SonakarBUG: Failure in medium testFollowing tutorial failed:
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/multiphase/part1/compressibleInterDyMFoam/ras/sloshingTank2D/log.compressibleInterDyMFoam
@andy @Mattijs Following tutorial failed:
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorials/multiphase/part1/compressibleInterDyMFoam/ras/sloshingTank2D/log.compressibleInterDyMFoam
@andy @Mattijs Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/1270incorrect default location for project site binaries2019-12-09T22:37:28ZMark OLESENincorrect default location for project site binaries`FOAM_SITE_APPBIN` and `FOAM_SITE_LIBBIN` are still using WM_PROJECT_VERSION instead of FOAM_API`FOAM_SITE_APPBIN` and `FOAM_SITE_LIBBIN` are still using WM_PROJECT_VERSION instead of FOAM_APIMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/930cyclicAMI not robust for perpendicular triangles; plane normal2019-12-09T22:22:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcyclicAMI not robust for perpendicular triangles; plane normalOn badly matching AMI patches the individual triangles can be perpendicular to the projection normal. If they are exactly perpendicular this can cause division by zero.
See ep 704.
```
--> FOAM Warning :
From function Foam::plane:...On badly matching AMI patches the individual triangles can be perpendicular to the projection normal. If they are exactly perpendicular this can cause division by zero.
See ep 704.
```
--> FOAM Warning :
From function Foam::plane::plane(const point&, const vector&, bool)
in file meshes/primitiveShapes/plane/plane.C at line 145
plane normal has zero length. base point:(2.492624677978299 0.7945491940387345 -0.06079065865800785)
```Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/659collated: incorrect checking for thread support2017-12-30T21:30:13ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcollated: incorrect checking for thread supportMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1012use normal distance in distanceSurface2018-09-19T21:39:42ZMark OLESENuse normal distance in distanceSurfaceFor zero distance, ignore user input and always make signed (requirement for zero-crossings to work at all).
Special treatment of surfaces with open edges (eg, an STL surface, a searchable disk etc): nothing reasonable for non-zero dist...For zero distance, ignore user input and always make signed (requirement for zero-crossings to work at all).
Special treatment of surfaces with open edges (eg, an STL surface, a searchable disk etc): nothing reasonable for non-zero distances. For zero-distance, using the normal distance from the surface hitPoint instead of real distance to the surface hitPoint alleviates problems caused by rounding.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/365BUG: inconsistency in fvOptions ->directionalPressureGradientExplicitSource2018-05-29T05:39:49ZPrashant SonakarBUG: inconsistency in fvOptions ->directionalPressureGradientExplicitSourceIt still refers to old *Name* style?
```
keyword fieldNames is undefined
```
@SergioIt still refers to old *Name* style?
```
keyword fieldNames is undefined
```
@SergioAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/906AMIInterpolation uses non-assigned magSf in parallel2018-07-03T10:40:07ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comAMIInterpolation uses non-assigned magSf in parallelMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/836v1712 cfmesh compile errors2018-05-28T13:07:23ZAdminv1712 cfmesh compile errorsSee thread here: https://www.cfd-online.com/Forums/openfoam-community-contributions/199262-openfoam-1712-cfmesh-compile-error.html
Compiling OpenFOAM v1712 works except for cfmesh. I got the same errors as the two people in the above th...See thread here: https://www.cfd-online.com/Forums/openfoam-community-contributions/199262-openfoam-1712-cfmesh-compile-error.html
Compiling OpenFOAM v1712 works except for cfmesh. I got the same errors as the two people in the above thread. I have not tried to troubleshoot this.
I did a quick search of the issues and didn't find anything regarding cfmesh, but sorry if this has already been reported.
OS: CentOS 7.5
OF: v1712https://develop.openfoam.com/Development/openfoam/-/issues/822Function1 could use faster searching in input is sorted2020-01-06T10:30:33ZPrashant SonakarFunction1 could use faster searching in input is sortedIf the table is sorted in increasing order we could use a binary search (e.g. ListOps::findLower) to speed up interpolation.If the table is sorted in increasing order we could use a binary search (e.g. ListOps::findLower) to speed up interpolation.https://develop.openfoam.com/Development/openfoam/-/issues/77Installation Error on OpenSUSE ---icoFoam critical error2016-03-15T03:55:56ZAdminInstallation Error on OpenSUSE ---icoFoam critical errorMy system is OpenSUSE 13.2. I have done the Installation several times as website openfoam.org/download/source.php, but the error still cannot be solved. The details are:
When I execute the 'foamInstallationTest', it displays as follo...My system is OpenSUSE 13.2. I have done the Installation several times as website openfoam.org/download/source.php, but the error still cannot be solved. The details are:
When I execute the 'foamInstallationTest', it displays as follows:
__________________________________-
Third party software
-------------------------------------------------------------------------------
Software Version Location
-------------------------------------------------------------------------------
flex 2.5.37 /usr/bin/flex
gcc 4.8.3 /usr/bin/gcc
g++ 4.8.3 /usr/bin/g++
gzip 1.6 /usr/bin/gzip
tar 1.28 /bin/tar
icoFoam
WARNING: Conflicting installations:
OpenFOAM settings : /home/van/OpenFOAM/OpenFOAM-3.0.1/platforms/linux64GccDPInt32Opt/bin/icoFoam
current path :
CRITICAL ERROR
-------------------------------------------------------------------------------
Summary
-------------------------------------------------------------------------------
Base configuration ok.
The foam installation contains 1 critical error(s).
----------------------------------
BESIDES, when I check the make.log file under OpenFOAM-3.0.1, it shows as follow:
___________________________________________
In file included from UOPwrite.C:30:0:
PstreamGlobals.H:41:17: fatal error: mpi.h: No such file or directory
#include <mpi.h>
^
compilation terminated.
/home/van/OpenFOAM/OpenFOAM-3.0.1/wmake/rules/General/transform:8: recipe for target '/home/van/OpenFOAM/OpenFOAM-3.0.1/platforms/linux64GccDPInt32OptSYSTEMOPENMPI/src/Pstream/mpi/UOPwrite.o' failed
make: *** [/home/van/OpenFOAM/OpenFOAM-3.0.1/platforms/linux64GccDPInt32OptSYSTEMOPENMPI/src/Pstream/mpi/UOPwrite.o] Error 1
____________________________________________
FURTHER MORE, when I check the make.log file under ThirdParty-3.0.1, it shows as follow:
make[1]: Leaving directory '/home/van/OpenFOAM/ThirdParty-3.0.1/scotch_6.0.3/src/check'
(cd esmumps ; make realclean)
make[1]: Entering directory '/home/van/OpenFOAM/ThirdParty-3.0.1/scotch_6.0.3/src/esmumps'
rm -f *~ common.h *.o lib*.so main_esmumps
make[1]: Leaving directory '/home/van/OpenFOAM/ThirdParty-3.0.1/scotch_6.0.3/src/esmumps'
rm -f ../bin/* ../include/* ../lib/*
WARNING: required include file 'ptscotch.h' not found!
========================================
Build Metis decomposition
optional component Metis was not found
========================================
Build CGAL
CGAL headers in /home/van/OpenFOAM/ThirdParty-3.0.1/platforms/linux64Gcc/CGAL-4.7/include
CGAL libs in /home/van/OpenFOAM/ThirdParty-3.0.1/platforms/linux64Gcc/CGAL-4.7/lib
========================================
Done ThirdParty Allwmake
========================================
I'd appreciate if anyone knows the answer! AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/960require secondary template parameter for findLower2018-08-08T12:16:31ZMark OLESENrequire secondary template parameter for findLowerfindLower has `typename ListType::const_reference val` for its value parameter, which limits the type of comparison predicate.
Change needed for #801 to use for a binary search on a PtrList of XXX.
For example,
const polyPatchList...findLower has `typename ListType::const_reference val` for its value parameter, which limits the type of comparison predicate.
Change needed for #801 to use for a binary search on a PtrList of XXX.
For example,
const polyPatchList& patches = *this;
return
findLower
(
patches,
faceIndex,
0,
[](const polyPatch& p, label val) { return (p.start() <= val); }
);
Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/559unbounded volume fraction for floatingBody example2019-01-08T15:41:26ZAdminunbounded volume fraction for floatingBody exampleI am playing with floatingBody tutorial to test the overset functionality.
At first, I set up a drop test by modifying the initial position of the floating body.
It looked good.
So, next I rotated the body by 35 deg to simulate a lifeboa...I am playing with floatingBody tutorial to test the overset functionality.
At first, I set up a drop test by modifying the initial position of the floating body.
It looked good.
So, next I rotated the body by 35 deg to simulate a lifeboat drop test. the attached file is the case for this simulation. the simulation did not work on the impact of interface about 0.52 sec.
I checked fields and found the volume fraction went up above 1 (max is above 800) and the phases went upside-down. I spent several days to resolve this behavior but failed.
It would be gratefull if somebody guide me what should be corrected.
Also, is there a way to impose initial velocity and angular velocity to the floating body?
Thanks in advance.
[inclinedDrop.tar.bz2](/uploads/a69e1d43eba9a5e205e0441c1df28365/inclinedDrop.tar.bz2)https://develop.openfoam.com/Development/openfoam/-/issues/1177allow adjustment of write precision for foamDictionary2019-10-29T10:59:04ZMark OLESENallow adjustment of write precision for foamDictionary- since foamDictionary doesn't use `system/controlDict` it will use the standard default precision.
- Add -precision option to allow adjusting this value.
@amutzk @svilfaye- since foamDictionary doesn't use `system/controlDict` it will use the standard default precision.
- Add -precision option to allow adjusting this value.
@amutzk @svilfayeMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/20Placeholder: self-intersections of surfaces (surfacePatch utility)2020-01-03T10:03:55ZPrashant SonakarPlaceholder: self-intersections of surfaces (surfacePatch utility)Tested again with non-overlapping nodes/edges case.
It still fails (see intersections of unitCubes.stl)
[surfaceToPatch.tgz](/uploads/0a78a54cddbf2e7f03a36a27fed5d9aa/surfaceToPatch.tgz)
Tested again with non-overlapping nodes/edges case.
It still fails (see intersections of unitCubes.stl)
[surfaceToPatch.tgz](/uploads/0a78a54cddbf2e7f03a36a27fed5d9aa/surfaceToPatch.tgz)
Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/820yna2018-05-08T07:52:35ZAdminynahttps://develop.openfoam.com/Development/openfoam/-/issues/531Feature: Possibility to suppress slaves from output2018-04-19T08:02:53ZPrashant SonakarFeature: Possibility to suppress slaves from outputWhen using large number of CPU e.g 720+, each execution of utility prints slaves.
-should this printing be optional ?When using large number of CPU e.g 720+, each execution of utility prints slaves.
-should this printing be optional ?https://develop.openfoam.com/Development/openfoam/-/issues/246Add sudo to docker container2020-06-18T21:18:13ZAdminAdd sudo to docker containerIn the install script /etc/profile.d is projected into the container. Which is great because that way a non-root access for installing software etc could be set up. Problem is that sudo currently is not installed in the container.
\## ...In the install script /etc/profile.d is projected into the container. Which is great because that way a non-root access for installing software etc could be set up. Problem is that sudo currently is not installed in the container.
\## Reattaching the author to the issue ticket: @bgschaid ##Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/823reference functionObject : issue while running in parallel2018-06-08T22:46:03ZAdminreference functionObject : issue while running in parallelWhile running in parallel, `pRef` field is written in `processor0` only.While running in parallel, `pRef` field is written in `processor0` only.AdminAdmin