Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-12-19T11:26:51Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/26ThirdParty-plus FFTW version2018-12-19T11:26:51ZRoger AlmenarThirdParty-plus FFTW versionThe FFTW version that we have in our develop files (etc/config.sh/FFTW) has been withdrawn from the public domain.
See from www.fftw.org/release-notes.html:
FFTW 3.3.6-pl1 (withdrawn)
Jan 16th, 2017
Bugfix: FFTW 3.3.6 had the wrong...The FFTW version that we have in our develop files (etc/config.sh/FFTW) has been withdrawn from the public domain.
See from www.fftw.org/release-notes.html:
FFTW 3.3.6-pl1 (withdrawn)
Jan 16th, 2017
Bugfix: FFTW 3.3.6 had the wrong libtool version number, and generated shared libraries of the form libfftw3.so.2.6.6 instead of libfftw3.so.3.*.
We should probably move to -pl2 instead of –pl1 .v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/442Bug in InterMixingFoam2017-04-18T13:40:34ZAdminBug in InterMixingFoamThere is a bug in the code of the InterMixingFoam solver in alphaEqns. The problem is in the ordering. Ordering in current code: Step 1: phase 1-the convection flux is created, bounded, corrected and limited. Step 2: phase 2-the convecti...There is a bug in the code of the InterMixingFoam solver in alphaEqns. The problem is in the ordering. Ordering in current code: Step 1: phase 1-the convection flux is created, bounded, corrected and limited. Step 2: phase 2-the convection flux is created, bounded, corrected and limited. Step 3: phase 1-limited flux constructed. Step 4: phase 2-limited flux constructed. The problem is the coefficients calculated in mules limiter for phase 1 are being overwritten by coefficients calculated for phase 2 and the the SAME coefficients are being used to construct both phases.Order should be: step 1,3,2,4. Line 175 should be put to 110.
Current solver: LEFT picture. Non sharp water-air interface between, due to wrong mules coefficients being used.
Corrected solver: RIGHT picture
(diffusion is set between other and water phase)
![ComparisonsOfSolvers](/uploads/a1519999c4105c03d767337397fe5bf9/ComparisonsOfSolvers.png)Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/27compilation of KaHIP2017-12-12T18:36:51ZMatej Formancompilation of KaHIPrunning `makeKAHIP` run in 2 issues on CentOS (would on anything)
1) downloaded KaHIP_2.00.tar.gz unpacks to KaHIP_v2.00d but `makeKAHIP` requires kahip-2.00 directory
2) compilation stumbles on directory which is already created:
``...running `makeKAHIP` run in 2 issues on CentOS (would on anything)
1) downloaded KaHIP_2.00.tar.gz unpacks to KaHIP_v2.00d but `makeKAHIP` requires kahip-2.00 directory
2) compilation stumbles on directory which is already created:
```
cpptoo: cycle_search.cpp
cpptoo: cycle_refinement.cpp
cpptoo: tabu_search.cpp
mkdir: cannot create directory ‘/home/linux/OpenFOAM/ThirdParty-plus/platforms/linux64GccDPInt32/lib’: File exists
make: *** [/home/linux/OpenFOAM/ThirdParty-plus/platforms/linux64GccDPInt32/lib/libkahip.so] Error 1
Error building: kahip
```v1712Mark OLESENMark OLESENhttps://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/ThirdParty-common/-/issues/28no mpicc on cray2017-12-18T10:05:26ZMark OLESENno mpicc on cray- the cray `cc` handles mpi paths- the cray `cc` handles mpi pathsv1712Mark OLESENMark OLESEN2017-12-18https://develop.openfoam.com/Development/openfoam/-/issues/438BUG: sonicFoam nacaAirfoil tutorial needs update2019-12-09T21:29:27ZAdminBUG: sonicFoam nacaAirfoil tutorial needs updateThe patches using in the `forceCoeffs` function object are out of dateThe patches using in the `forceCoeffs` function object are out of dateVersion v1706https://develop.openfoam.com/Development/ThirdParty-common/-/issues/29more stringency when exporting WM_ compiler settings2018-05-29T10:42:24ZMark OLESENmore stringency when exporting WM_ compiler settings- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env...- for building 3rd-party components, we export `WM_CC` and `WM_CXX` compiler settings as `CC` and `CXX` so the configure/CMake know about them. However, when trying to build something like Clang we can experience issues. The OpenFOAM env sets ThirdParty Clang (setting WM_CC in the process), but this is the component we are trying to build, so `makeLLVM` will have problems configuring for this non-existent compiler.
1. can avoid this by using `makeLLVM -gcc` to force use of gcc for making Clang. This seems to be an ok alternative, since this isn't part of the normal OpenFOAM process (we are building the toolchain for building OpenFOAM).
2. check within the ThirdParty scripts that the exported `CC` variable corresponds to a command. Eg,
if test -n "$WM_CC" && command -v "$WM_CC" >/dev/null
then
export CC="$WM_CC"
[ -n "$WM_CFLAGS" ] && export CFLAGS="$WM_CFLAGS"
fi
Probably the second one is OK to include too, but targeted for the next release.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/437BUG: function object time usage does not respect user time2019-12-09T21:29:28ZAdminBUG: function object time usage does not respect user timeIf cases are set up using, e.g. engineTime, the reported times are in 's' and not 'CA'. This relates to file output via the `writeFile` class, and all time-related inputsIf cases are set up using, e.g. engineTime, the reported times are in 's' and not 'CA'. This relates to file output via the `writeFile` class, and all time-related inputsVersion v1706https://develop.openfoam.com/Development/ThirdParty-common/-/issues/30Check for wmake toolchain in some third-party components2018-06-28T08:31:14ZMark OLESENCheck for wmake toolchain in some third-party componentsIf ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
If ThirdParty Allwmake is executed prior to the OpenFOAM Allwmake, the wmkdep and dirToString will not yet exist. Emit a warning about this and/or take some corrective action.
Mentioned in exchange#583
v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/436BUG: forceCoeffs function object not operating correctly for compressible cases2019-12-09T21:29:27ZAdminBUG: forceCoeffs function object not operating correctly for compressible casesThe rhoRef_ value is used when calculating the freestream dynamic pressure. This is only set in forces.C for incompressible cases, leaving the value uninitialised for compressible cases.The rhoRef_ value is used when calculating the freestream dynamic pressure. This is only set in forces.C for incompressible cases, leaving the value uninitialised for compressible cases.Version v1706https://develop.openfoam.com/Development/ThirdParty-common/-/issues/31scotch6.0.5a building2018-06-28T08:31:14ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch6.0.5a buildingdownloaded scotch6.0.5a (https://gforge.inria.fr/frs/?group_id=248), adapted etc/config.sh/scotch for new version. When building it cannot find scotch.h. It works fine if built 'by hand' : first builds dummysizes which then writes scotch.h.downloaded scotch6.0.5a (https://gforge.inria.fr/frs/?group_id=248), adapted etc/config.sh/scotch for new version. When building it cannot find scotch.h. It works fine if built 'by hand' : first builds dummysizes which then writes scotch.h.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/435BUG: wallHeatFlux function object output file missing header information2019-12-09T21:29:27ZAdminBUG: wallHeatFlux function object output file missing header informationThe writeFileHeader(os) function is not being called on construction as it should beThe writeFileHeader(os) function is not being called on construction as it should beVersion v1706https://develop.openfoam.com/Development/ThirdParty-common/-/issues/32QT installation moved to other location : need more environment variable to b...2018-05-14T13:28:25ZPawan GhildiyalQT installation moved to other location : need more environment variable to be setI need to add following environment variable to make paraview run .
export PYTHONHOME=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7
export PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/bin:$PATH
export LD_LIBRARY_PAT...I need to add following environment variable to make paraview run .
export PYTHONHOME=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7
export PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/bin:$PATH
export LD_LIBRARY_PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/python2.7/lib/:$LD_LIBRARY_PATH
export QT_PLUGIN_PATH=$WM_THIRD_PARTY_DIR/platforms/linux64Gcc/qt-5.9.0/pluginsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/433BUG? multiple cellZones sharing same cell?2017-04-18T13:40:34ZPrashant SonakarBUG? multiple cellZones sharing same cell?Following example produces two cellZones with having two cells in common.
Is this legal?
@mark [test_cellZone.tgz](/uploads/174ca4aa4281cd46bd250c65e0e92cee/test_cellZone.tgz)Following example produces two cellZones with having two cells in common.
Is this legal?
@mark [test_cellZone.tgz](/uploads/174ca4aa4281cd46bd250c65e0e92cee/test_cellZone.tgz)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/33compilation with IntelMPI failed2018-05-16T09:29:57ZPawan Ghildiyalcompilation with IntelMPI failedUsing ThirdParty compiler Gcc64 and pointing to MPI_ROOT path to intelMPI
complain about mpi.h not found during compilation .
"sinclude $(GENERAL_RULES)/mplib$(WM_MPLIB)"
"sinclude $(RULES)/mplib$(WM_MPLIB)"
Solution: **Mark** p...Using ThirdParty compiler Gcc64 and pointing to MPI_ROOT path to intelMPI
complain about mpi.h not found during compilation .
"sinclude $(GENERAL_RULES)/mplib$(WM_MPLIB)"
"sinclude $(RULES)/mplib$(WM_MPLIB)"
Solution: **Mark** pointed out following need to be added to fix this issue
"sinclude $(DEFAULT_RULES)/mplib$(WM_MPLIB)"
Regards
PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/430BUG: foamToEnsight failed when first patch type is empty?2019-12-09T21:29:27ZPrashant SonakarBUG: foamToEnsight failed when first patch type is empty?Attached modified tutorial with change only in
- blockMeshDict -> order of patch definition
- controlDict -> reduced run time
- Allrun -> Added foamToEnsight
[sineWaveDamping_modified.tgz](/uploads/a7dbed1ecb0e223edd8b39f2facd5ffc...Attached modified tutorial with change only in
- blockMeshDict -> order of patch definition
- controlDict -> reduced run time
- Allrun -> Added foamToEnsight
[sineWaveDamping_modified.tgz](/uploads/a7dbed1ecb0e223edd8b39f2facd5ffc/sineWaveDamping_modified.tgz)Version v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/34Request to make change in qt.conf using relocateQT2018-12-19T11:26:29ZPawan GhildiyalRequest to make change in qt.conf using relocateQTHi Mark
As discussed , please change path of **prefix** to installation qt dir
under third party dir .
the file is located inside
> qt-5.9.1/bin/qt.conf
Regards
PawanHi Mark
As discussed , please change path of **prefix** to installation qt dir
under third party dir .
the file is located inside
> qt-5.9.1/bin/qt.conf
Regards
PawanPawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/428mass conservation problem in interCondensingEvaporatingFoam2017-04-18T13:40:34ZAdminmass conservation problem in interCondensingEvaporatingFoamDear OF Developers,
I am working with interCondensingEvaporatingFoam solver. I have encountered a possibly very important problem.
I am calculating flow with a phase change in-between heated plates. Domain has one inlet, one outlet, and...Dear OF Developers,
I am working with interCondensingEvaporatingFoam solver. I have encountered a possibly very important problem.
I am calculating flow with a phase change in-between heated plates. Domain has one inlet, one outlet, and a body limited by two heated plates.
At the inlet the liquid enters the domain, is heated, partially evaporates and leaves the domain via outlet.
The problem is that the mass is not conserved. There is approximately 6x larger mass flow of the liquid/vapor mixture at the outlet that at the inlet.
Please see the attached picture, which shows some filed values and integrated 'u_x*rho' over the inlet and outlet patch (u_x in normal to the inlet/outlet, so it gives mass flow).
![mass_conservation_problem](/uploads/392619e49f0b4f2972c607e84143be8f/mass_conservation_problem.png)
upper row of the figure shows the data for the inlet; the value "U_x_times_rho_inlet" in the table on the right corresponds to inlet mass flow
lower row of the figure shows the data for the outlet; the value "U_x_times_rho_outlet" in the table on the right corresponds to outlet mass flow
Regards
Jimhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/35Request to add additional flag to resolve issue : QFontDatabase: Cannot find...2018-06-07T08:08:28ZPawan GhildiyalRequest to add additional flag to resolve issue : QFontDatabase: Cannot find font directoryIn makeQT
QT has two option either to use system font or use QT font to display fonts
in application build, using QT . I noticed that present makeQT script
is configured to use QT font. It has not caused any issue till now but i not...In makeQT
QT has two option either to use system font or use QT font to display fonts
in application build, using QT . I noticed that present makeQT script
is configured to use QT font. It has not caused any issue till now but i noticed
that with QT-5.9.1 , building with default makeQT script ,cause Paraview to pop
up message "QFontDatabase: Cannot find font directory" and no font appear in QT.
Configuring qt with additional flag ** -**fontconfig** **, resolved the issue.
I did test with SUSE-Enterprise-12SP1 using gcc-6.4.1
Regards
PawanMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/425BUG: Noise utility overwrites data2017-04-18T13:40:34ZPrashant SonakarBUG: Noise utility overwrites dataRefer EP#338
E.g. if inputFiles ("location1/p" "location2/p")
the output for 2 is overwritten on 1.Refer EP#338
E.g. if inputFiles ("location1/p" "location2/p")
the output for 2 is overwritten on 1.AdminAdmin