Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-05-29T10:49:29Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/36compile issue with kahip v17122018-05-29T10:49:29ZJed Storeycompile issue with kahip v1712I get the following error trying to build (./Allwmake > log.make 2>&1) the ThirdParty software from v1712:
"make: *** No rule to make target 'Make/linux64GccDPInt64Opt/interface/kaHIP/_interface.cpp.dep', needed by 'Make/linux64GccDPInt...I get the following error trying to build (./Allwmake > log.make 2>&1) the ThirdParty software from v1712:
"make: *** No rule to make target 'Make/linux64GccDPInt64Opt/interface/kaHIP/_interface.cpp.dep', needed by 'Make/linux64GccDPInt64Opt/interface/kaHIP_interface/o' . Stop. Error buidling: kahip.
Not sure if it is relevant, but there were a bunch (~100) of these lines in the kahip part of the log: "make: /opt/OpenFOAM-v1712/wmake/platforms/linux64Gcc/wmkdep: Command not found", though not every line was that.
Also, not sure if it is relevant, but when I source the OpenFOAM bashrc, I get the following warning: "No completion added for /opt/OpenFOAM-v1712/platforms/linux64GccDPInt640Opt/bin".
I also have a problem compiling cfmesh (separate bug report, probably not related?), but besides that and this, everything else seems to compile and work fine.
OF: v1712
OS: CentOS 7.5
Bash: 4.2
GCC: 4.8.5 (system)
cmake: 3.11.2 (manual install system)
Boost: 1.53 (system)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/139Compiler error in activePressureForceBaffleVelocityFvPatchVectorField.C2016-06-13T08:30:35ZAdminCompiler error in activePressureForceBaffleVelocityFvPatchVectorField.CWrong assignment in activePressureForceBaffleVelocityFvPatchVectorField.C:283:23
Division of scalar and scalarFieldWrong assignment in activePressureForceBaffleVelocityFvPatchVectorField.C:283:23
Division of scalar and scalarFieldSergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/886compiler warnings: unused variables2018-07-02T09:34:07ZPrashant Sonakarcompiler warnings: unused variablesCan we do anything about compiler warnings of unused variables?
1) applications/solvers/DNS/dnsFoam
- readTurbulenceProperties.H:28:18: warning: unused variable 'recRootN'
2) applications/solvers/combustion/fireFoam
- createFields.H:11...Can we do anything about compiler warnings of unused variables?
1) applications/solvers/DNS/dnsFoam
- readTurbulenceProperties.H:28:18: warning: unused variable 'recRootN'
2) applications/solvers/combustion/fireFoam
- createFields.H:117:6: warning: unused variable 'solvePrimaryRegion'
- createFields.H:122:6: warning: unused variable 'solvePyrolysisRegion'
3) src/finiteVolume/cfdTools/general/include/alphaControls.H:24:8:
- warning: unused variable 'scAlpha'
4) applications/solvers/incompressible/simpleFoam/overSimpleFoam
- createOversetFields.H:27:6: warning: unused variable 'adjustFringe'
- createOversetFields.H:31:6: warning: unused variable 'massFluxInterpolation'
5) applications/solvers/incompressible/simpleFoam/porousSimpleFoam
- createPorousZones.H:2:10: warning: variable 'pressureImplicitPorosity' set but not used
6) applications/solvers/lagrangian/reactingParcelFoam
- createFields.H:106:6: warning: unused variable 'solvePrimaryRegion'
@andy @Mattijs @mark @Sergiohttps://develop.openfoam.com/Development/openfoam/-/issues/1912Compiling OpenFOAM v.20062020-11-10T12:10:41ZTasman Van LoonCompiling OpenFOAM v.2006Hi there, I'm trying to compile OpenFOAM v.2006 and have followed the instructions as per this webpage:
https://develop.openfoam.com/Development/openfoam/blob/develop/doc/Build.md
There are no issues with the foamSystemCheck. But when I...Hi there, I'm trying to compile OpenFOAM v.2006 and have followed the instructions as per this webpage:
https://develop.openfoam.com/Development/openfoam/blob/develop/doc/Build.md
There are no issues with the foamSystemCheck. But when I go to execute the ./Allwmake command, there is an error message (which I have attached).
Any advice would be appreciated!
Kind regards,
Tasman. ![Screen_Shot_2020-11-05_at_11.04.27_pm](/uploads/60136129f5c4821f4a97e5281f02c7b7/Screen_Shot_2020-11-05_at_11.04.27_pm.png)https://develop.openfoam.com/Development/openfoam/-/issues/2100COMP: incGamma: factorial(int&) is ambiguous for int642021-06-09T14:37:43ZKutalmış BerçinCOMP: incGamma: factorial(int&) is ambiguous for int64### Summary
[log.linux64GccDPInt64Opt](/uploads/eaa9df454f443ec583bef0f628fe71e4/log.linux64GccDPInt64Opt)
```
primitives/functions/Math/incGamma.C:260:57: error: call of overloaded ‘factorial(int&)’ is ambiguous
```
### Possible f...### Summary
[log.linux64GccDPInt64Opt](/uploads/eaa9df454f443ec583bef0f628fe71e4/log.linux64GccDPInt64Opt)
```
primitives/functions/Math/incGamma.C:260:57: error: call of overloaded ‘factorial(int&)’ is ambiguous
```
### Possible fixes
[0001-COMP-incGamma-invIncGamma-adjustments-for-int64-2100.patch](/uploads/392ba16cd777e98a7f431245990d3dbd/0001-COMP-incGamma-invIncGamma-adjustments-for-int64-2100.patch)v2106Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/13COMP: Inconsistent files for ADIOS2019-07-21T22:56:27ZPrashant SonakarCOMP: Inconsistent files for ADIOShttps://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain...https://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain `Makefile.in` (has Makefile.am) and gets terminated during compilation.
- The alt download returns `adios-1.11.0` but makeADIOS script expects the folder name in CAPITAL.
@andyVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/695COMP: incorrect executable path2019-12-09T22:18:10ZPrashant SonakarCOMP: incorrect executable pathhttps://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/applications/solvers/finiteArea/sphereSurfactantFoam/Make/files points to USER area and not standard APPBIN
@andy @markhttps://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/applications/solvers/finiteArea/sphereSurfactantFoam/Make/files points to USER area and not standard APPBIN
@andy @markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1068COMP: issue in executables getting segmentFault2018-11-13T09:48:23ZPrashant SonakarCOMP: issue in executables getting segmentFaultWith latest develop pulled today, the compilations runs through OK.
However none of the executable work. All end up with segment Fault.
Changing the file src/OpenFOAM/fields/Fields/fieldTypes.C
```
const Foam::wordList Foam::fieldTypes...With latest develop pulled today, the compilations runs through OK.
However none of the executable work. All end up with segment Fault.
Changing the file src/OpenFOAM/fields/Fields/fieldTypes.C
```
const Foam::wordList Foam::fieldTypes::basic
({
"labelField", //Foam::labelIOField::typeName,
"scalarField", //Foam::scalarIOField::typeName,
"vectorField", //Foam::vectorIOField::typeName,
"sphericalTensorField", //Foam::sphericalTensorIOField::typeName,
"symmTensorField", //Foam::symmTensorIOField::typeName,
"tensorField" //Foam::tensorIOField::typeName
});
```
seems to work.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2934COMP: missing hostUncollatedFileOperation2023-09-01T10:39:30ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comCOMP: missing hostUncollatedFileOperation### Functionality to add/problem to solve
hostUncollated fileOperation not included in Make/files in v2306.### Functionality to add/problem to solve
hostUncollated fileOperation not included in Make/files in v2306.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/682COMP : missing make files for heatTransferCoeff function object2017-12-28T04:51:51ZAdminCOMP : missing make files for heatTransferCoeff function objectMissing
heatTransferCoeff/heatTransferCoeff.C
heatTransferCoeff/heatTransferCoeffModels/fixedReferenceTemperature/fixedReferenceTemperature.C
heatTransferCoeff/heatTransferCoeffModels/localReferenceTemperature/localReferenceTemperature...Missing
heatTransferCoeff/heatTransferCoeff.C
heatTransferCoeff/heatTransferCoeffModels/fixedReferenceTemperature/fixedReferenceTemperature.C
heatTransferCoeff/heatTransferCoeffModels/localReferenceTemperature/localReferenceTemperature.C
heatTransferCoeff/heatTransferCoeffModels/heatTransferCoeffModel/heatTransferCoeffModelNew.C
heatTransferCoeff/heatTransferCoeffModels/heatTransferCoeffModel/heatTransferCoeffModel.C
heatTransferCoeff/heatTransferCoeffModels/ReynoldsAnalogy/ReynoldsAnalogy.C
in Make/files
@andyhttps://develop.openfoam.com/Development/openfoam/-/issues/457compressible dynamicLagrangian SGS2017-07-20T08:46:57ZAdmincompressible dynamicLagrangian SGSIt seems that there is a bug in dynamicLagrangian SGS model implemented for “compressible” solver. Since the rho value already implemented into the equations for fmm and flm then flm and fmm files in zero directory should have the same d...It seems that there is a bug in dynamicLagrangian SGS model implemented for “compressible” solver. Since the rho value already implemented into the equations for fmm and flm then flm and fmm files in zero directory should have the same dimension as incompressible version which is [0 4 -4 0 0 0 0] for both fmm and flm. However, with this set of dimension and with many other combinations, OpenFOAM is giving the “incompatible dimensions for operation” error.Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/1813compressibleInterFoam: unphysical oscillations in transonic flows2020-11-10T17:34:53ZMartin HeinrichcompressibleInterFoam: unphysical oscillations in transonic flows### Summary
compressibleInterFoam produces unrealistic oscillations for transonic flow simulations. This can be demonstrated using a simple shockTube tutorial case. Interestingly, this problem was not present prior to OpenFOAM 5.0.
###...### Summary
compressibleInterFoam produces unrealistic oscillations for transonic flow simulations. This can be demonstrated using a simple shockTube tutorial case. Interestingly, this problem was not present prior to OpenFOAM 5.0.
### Steps to reproduce
Use the shockTube tutorial case of rhoCentralFoam and solve it with compressibleInterFoam with OpenFOAM v2006
### Example case
I have attached the shockTube tutorial case set up for compressibleInterFoam and for comparison also the case for rhoPimpleFoam with OpenFOAM v2006 [summary.zip](/uploads/f912e1f72bfd05fd7edd866bc4417c04/summary.zip). The solution for rhoPimpleFoam matches quite well with rhoCentralFoam. However, compressibleInterFoam is quite far off and oscillates strongly between x = 2 and x = 4. This happens for all OpenFOAM versions starting with 5.0, including the latest v2006. However, it does not happen in OpenFOAM 4.x and earlier.
![shockTube](/uploads/fae665ca0e06cef72810a3349011f4b6/shockTube.png)
### Environment information
- OpenFOAM version : v2006
- Operating system : Debian 10
- Hardware info :
- Compiler : gcc 9.1
### Possible fixes
This problem started somewhere around [commit e8daaa5c767ac9731fb7ec3259043a4aae5ae972](https://github.com/OpenFOAM/OpenFOAM-5.x/commit/e8daaa5c767ac9731fb7ec3259043a4aae5ae972) in OpenFOAM 5.x. Prior to that (for example OpenFOAM 4.x), the results agree quite well with rhoCentralFoam and rhoPimpleFoam.https://develop.openfoam.com/Development/openfoam/-/issues/2172Conan Package Manager for OpenFOAM2024-01-09T12:12:47ZHenning ScheuflerConan Package Manager for OpenFOAMHi,
I recently stumbled over the conan c/c++ package manager and was impressed by how easy it is to use. It downloads the precompiled package and dramatically simplifies the installation process of new libraries similar to pip install i...Hi,
I recently stumbled over the conan c/c++ package manager and was impressed by how easy it is to use. It downloads the precompiled package and dramatically simplifies the installation process of new libraries similar to pip install in python.
The available libraries can be browsed here:
https://conan.io/center/
The most common generator used with conan is cmake, but it can be easily extended, as shown in the example below:
https://github.com/HenningScheufler/OpenFOAMGen
The above generator inserts the conan-dependencies in the options file in the Make folder based on a file named options.template. I successfully linked the boost library and nlohmann/json with just a few lines of code.
This is the first draft of the generator, and I would be happy to get your thoughts and suggestions as I only know the basics of the OpenFOAM build system.
Best Regards,
Henninghttps://develop.openfoam.com/Development/openfoam/-/issues/2199coneInjection fails to atomize in all injector positions.2021-09-07T07:55:40ZJairo Andrés GutiérrezconeInjection fails to atomize in all injector positions.<!--
*** 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 -->
I am working with sprayFoam using a Multi-point cone injection atomization (16 injectors). They are set radially mimicking a rotary atomizer. A massRossin Rammler distribution is used. Depending on the injectionModels configuration (massTotal - SOI - parcelsPerSecond - duration), some injectors do not inject parcels or inject a much lower number of them. In all cases, Injector 1 works well, as the problem gradually appears from injectors down the list.
The attached figure presents an example of part of the problem:
- Increasing the parcelsPerInjector helps to improve the behaviour.
- Decreasing the totalMass helps to improve the behaviour.
![aachemBombBug](/uploads/b158690b6fe5ff69fc41f7b5a6492e9f/aachemBombBug.jpeg)
### Steps to reproduce
I am attaching with this report a modified "AachenBomb" case. To reproduce, go to the sprayCloudProperties file, line 86, where I have highlighted some massTotal and parcelsPerSecond values that generate the problem.
This is the example case:
[aachenBomb.zip](/uploads/65e39525858de81bce338cce11dc599a/aachenBomb.zip)
### Example case
<!-- What actually happens -->
### What is the expected *correct* behaviour?
The expected behaviour is having all the injectors of the coneInjection working, even when a low number of parcels (nParcels per timestep is lower than the # of Injectors) is injected per time-step.
<!-- What you should see instead -->
### Relevant logs and/or images
<!--
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906|v1912|v2006|v2012|v2106 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : 2012
- Operating system : Ubuntu 18.04 LTS
- Hardware info : Core I7 - 7th gen.
- Compiler :
### Possible fixes
I think the error is caused when the number of added parcels (per timestep) is lower than the number of injectors.
When the totalMass to inject is decreased, the dt increases (as the momentum source for the gas phase decreases) and more parcels are injected per time step. When ParcelsToInject is increased, more parcels are injected per second, until this value is greater than the number of injectors.
I am not sure exactly where in the code, but there should be a loop stating forAll(positionAxis_....) forcing the first parcel to be injected in injector 1, and the second to injector 2, and so. Thefore, I think the order of injection per time-step should be randomized.
<!--
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
-->Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/674configuring 3rd party clang and mpfr2018-03-05T15:26:00ZMark OLESENconfiguring 3rd party clang and mpfr- When using third-party compilers, it is currently possible to build gcc with a system or third-party installation of gmp/mpfr. The clang installation does not normally need these. However CGAL does normally build using gmp/mpfr. If the...- When using third-party compilers, it is currently possible to build gcc with a system or third-party installation of gmp/mpfr. The clang installation does not normally need these. However CGAL does normally build using gmp/mpfr. If these are not available on the system, it is also possible to compile without. Eg,
./makeCGAL gmp-none mpfr-none
This mostly solves the problem, but only until the final link stage. The wmake rules for CGAL include `-lmpfr` explicitly. As a workaround, this can be removed, but a better solution may be to check the contents of the CGAL/compiler_config.h for this type of content:
#define CGAL_USE_GMP 1
#define CGAL_USE_MPFR 1
//#define CGAL_USE_GMPXX 1v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2926Confusing/misleading GeometricField constructor2023-07-06T06:29:11ZMark OLESENConfusing/misleading GeometricField constructorAs raised as [cfd-online issue](https://www.cfd-online.com/Forums/openfoam-programming-development/250569-how-create-field-without-reading-0-directroy.html), the following field constructor can be misleading:
```
//- Construct and read g...As raised as [cfd-online issue](https://www.cfd-online.com/Forums/openfoam-programming-development/250569-how-create-field-without-reading-0-directroy.html), the following field constructor can be misleading:
```
//- Construct and read given IOobject
GeometricField
(
const IOobject& io,
const Mesh& mesh,
const bool readOldTime = true
);
```
One could suppose that the constructor respects the readOption of the IOobject but it does not. It always reads!
For a non-read constructor, the preferred form would be
```
GeometricField
(
const IOobject& io,
const Mesh& mesh,
const dimensionSet& ds,
const word& patchFieldType = PatchField<Type>::calculatedType()
);
```
but this may be non-obvious.
- Minimum fix: more explicit documentation, add a warning message when using with incorrect readOption so that it emits something before possibly failing.
- TBD: have the constructor switch to readIfPresent behaviour or even no-read. In these cases, not really sure if the implied boundaries are also "calculated" etc. Could potentially change some existing code?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1756Confusing typo in boundary conditions docs2020-07-02T10:14:26ZArashConfusing typo in boundary conditions docsI believe the description of `pressureInletOutletVelocity` is wrong.
>This velocity inlet/outlet boundary condition is applied to **pressure** boundaries where the pressure is specified. A zero-gradient condition is applied for outflow...I believe the description of `pressureInletOutletVelocity` is wrong.
>This velocity inlet/outlet boundary condition is applied to **pressure** boundaries where the pressure is specified. A zero-gradient condition is applied for outflow (as defined by the flux); for inflow, the velocity is obtained from the patch-face normal component of the internal-cell value.
Yet, as the name suggests (or looking at the `Vector` type in the source code implies that it should be applied on **velocity**. It is iterated both in [site](https://www.openfoam.com/documentation/user-guide/standard-boundaryconditions.php) and the [Doxygen](https://www.openfoam.com/documentation/guides/latest/api/classFoam_1_1pressureInletOutletVelocityFvPatchVectorField.html#details) doc. It's not by any means critical, yet it makes it a bit harder to puzzle out for beginners like me.
The very same thing has recurred in `pressureDirectedInletOutletVelocityFvPatchVectorField` too: [Doxygen](https://www.openfoam.com/documentation/guides/latest/api/classFoam_1_1pressureDirectedInletOutletVelocityFvPatchVectorField.html#details)https://develop.openfoam.com/Development/openfoam/-/issues/513consolidate arch and version strings2017-07-08T09:16:54ZMark OLESENconsolidate arch and version stringsv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/520consolidate table bounding2017-07-08T09:14:05ZMark OLESENconsolidate table boundingduplicate or nearly duplicate older code for handling table bounds. Can use Enum instead.duplicate or nearly duplicate older code for handling table bounds. Can use Enum instead.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1708construct edge/fixed list from subset2020-05-22T12:24:32ZMark OLESENconstruct edge/fixed list from subset@Mattijs@MattijsMark OLESENMark OLESEN