Development issueshttps://develop.openfoam.com/groups/Development/-/issues2022-02-28T13:26:41Zhttps://develop.openfoam.com/Development/openfoam/-/issues/2280remove unused domainName and full hostName2022-02-28T13:26:41ZMark OLESENremove unused domainName and full hostName- neither are used
- probably don't work properly on windows
- POSIX version use deprecated gethostbyname()- neither are used
- probably don't work properly on windows
- POSIX version use deprecated gethostbyname()v2206Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1204renaming of residuals to solverInfo2019-02-14T21:54:35ZMark OLESENrenaming of residuals to solverInfo```
--> FOAM Warning :
Unknown function type residuals
```
Could resolve compatibility by adding an addNamed... lookup, but may also need symlink the etc/caseDicts/../numerical/residuals* files```
--> FOAM Warning :
Unknown function type residuals
```
Could resolve compatibility by adding an addNamed... lookup, but may also need symlink the etc/caseDicts/../numerical/residuals* filesAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/2311renaming the case-sensitive paths2022-01-12T08:58:30ZFoadrenaming the case-sensitive pathsFor some reason, OpenFOAM developers have case-sensitive paths in the codebase. As a result, it is difficult to port the software or to other OSes, such as macOS and/or Windows. For example, trying to `git clone` this repository on macOS...For some reason, OpenFOAM developers have case-sensitive paths in the codebase. As a result, it is difficult to port the software or to other OSes, such as macOS and/or Windows. For example, trying to `git clone` this repository on macOS results
<pre>
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'applications/test/Dictionary/Make/files'
'applications/test/dictionary/Make/files'
'applications/test/Dictionary/Make/options'
'applications/test/dictionary/Make/options'
'applications/test/Dictionary/Test-Dictionary.C'
'applications/test/dictionary/Test-dictionary.C'
'applications/test/Tensor2D/Make/files'
'applications/test/tensor2D/Make/files'
'applications/test/Tensor2D/Make/options'
'applications/test/tensor2D/Make/options'
'applications/test/Tensor2D/Test-Tensor2D.C'
'applications/test/tensor2D/Test-tensor2D.C'
'src/finiteVolume/finiteVolume/fvc/fvcDDt.C'
'src/finiteVolume/finiteVolume/fvc/fvcDdt.C'
'src/finiteVolume/finiteVolume/fvc/fvcDDt.H'
'src/finiteVolume/finiteVolume/fvc/fvcDdt.H'
'src/finiteVolume/finiteVolume/gradSchemes/LeastSquaresGrad/LeastSquaresGrad.C'
'src/finiteVolume/finiteVolume/gradSchemes/leastSquaresGrad/leastSquaresGrad.C'
'src/finiteVolume/finiteVolume/gradSchemes/LeastSquaresGrad/LeastSquaresGrad.H'
'src/finiteVolume/finiteVolume/gradSchemes/leastSquaresGrad/leastSquaresGrad.H'
'src/finiteVolume/finiteVolume/gradSchemes/LeastSquaresGrad/LeastSquaresGrads.C'
'src/finiteVolume/finiteVolume/gradSchemes/leastSquaresGrad/leastSquaresGrads.C'
'src/finiteVolume/finiteVolume/gradSchemes/LeastSquaresGrad/LeastSquaresVectors.C'
'src/finiteVolume/finiteVolume/gradSchemes/leastSquaresGrad/leastSquaresVectors.C'
'src/finiteVolume/finiteVolume/gradSchemes/LeastSquaresGrad/LeastSquaresVectors.H'
'src/finiteVolume/finiteVolume/gradSchemes/leastSquaresGrad/leastSquaresVectors.H'
'src/fvOptions/sources/derived/phaseLimitStabilization/PhaseLimitStabilization.C'
'src/fvOptions/sources/derived/phaseLimitStabilization/phaseLimitStabilization.C'
'src/fvOptions/sources/general/semiImplicitSource/SemiImplicitSource.C'
'src/fvOptions/sources/general/semiImplicitSource/semiImplicitSource.C'
'src/OpenFOAM/db/Time/instant/Instant.C'
'src/OpenFOAM/db/Time/instant/instant.C'
'src/OpenFOAM/db/Time/instant/Instant.H'
'src/OpenFOAM/db/Time/instant/instant.H'
'src/OpenFOAM/interpolations/patchToPatchInterpolation/PatchToPatchInterpolation.H'
'src/OpenFOAM/interpolations/patchToPatchInterpolation/patchToPatchInterpolation.H'
'src/OpenFOAM/interpolations/primitivePatchInterpolation/PrimitivePatchInterpolation.H'
'src/OpenFOAM/interpolations/primitivePatchInterpolation/primitivePatchInterpolation.H'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrix.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrix.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrix.H'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrix.H'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixATmul.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixATmul.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixOperations.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixOperations.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixPreconditioner.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixPreconditioner.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixSmoother.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixSmoother.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixSolver.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixSolver.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/LduMatrixUpdateMatrixInterfaces.C'
'src/OpenFOAM/matrices/lduMatrix/lduMatrix/lduMatrixUpdateMatrixInterfaces.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/SolverPerformance.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/solverPerformance.C'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/SolverPerformance.H'
'src/OpenFOAM/matrices/LduMatrix/LduMatrix/solverPerformance.H'
'src/OpenFOAM/matrices/LduMatrix/Preconditioners/DiagonalPreconditioner/DiagonalPreconditioner.C'
'src/OpenFOAM/matrices/lduMatrix/preconditioners/diagonalPreconditioner/diagonalPreconditioner.C'
'src/OpenFOAM/matrices/LduMatrix/Preconditioners/DiagonalPreconditioner/DiagonalPreconditioner.H'
'src/OpenFOAM/matrices/lduMatrix/preconditioners/diagonalPreconditioner/diagonalPreconditioner.H'
'src/OpenFOAM/matrices/LduMatrix/Preconditioners/NoPreconditioner/NoPreconditioner.C'
'src/OpenFOAM/matrices/lduMatrix/preconditioners/noPreconditioner/noPreconditioner.C'
'src/OpenFOAM/matrices/LduMatrix/Preconditioners/NoPreconditioner/NoPreconditioner.H'
'src/OpenFOAM/matrices/lduMatrix/preconditioners/noPreconditioner/noPreconditioner.H'
'src/OpenFOAM/matrices/LduMatrix/Solvers/DiagonalSolver/DiagonalSolver.C'
'src/OpenFOAM/matrices/lduMatrix/solvers/diagonalSolver/diagonalSolver.C'
'src/OpenFOAM/matrices/LduMatrix/Solvers/DiagonalSolver/DiagonalSolver.H'
'src/OpenFOAM/matrices/lduMatrix/solvers/diagonalSolver/diagonalSolver.H'
'src/OpenFOAM/matrices/LduMatrix/Solvers/SmoothSolver/SmoothSolver.C'
'src/OpenFOAM/matrices/lduMatrix/solvers/smoothSolver/smoothSolver.C'
'src/OpenFOAM/matrices/LduMatrix/Solvers/SmoothSolver/SmoothSolver.H'
'src/OpenFOAM/matrices/lduMatrix/solvers/smoothSolver/smoothSolver.H'
'src/OpenFOAM/meshes/MeshObject/MeshObject.C'
'src/OpenFOAM/meshes/MeshObject/meshObject.C'
'src/OpenFOAM/meshes/primitiveMesh/PrimitivePatch/PrimitivePatch.H'
'src/OpenFOAM/meshes/primitiveMesh/primitivePatch/primitivePatch.H'
'src/OpenFOAM/meshes/primitiveShapes/objectHit/PointHit.H'
'src/OpenFOAM/meshes/primitiveShapes/objectHit/pointHit.H'
'src/OpenFOAM/meshes/primitiveShapes/objectHit/PointIndexHit.H'
'src/OpenFOAM/meshes/primitiveShapes/objectHit/pointIndexHit.H'
'src/phaseSystemModels/multiphaseInter/phasesSystem/InterfaceCompositionModel/InterfaceCompositionModel.C'
'src/phaseSystemModels/multiphaseInter/phasesSystem/interfaceCompositionModel/interfaceCompositionModel.C'
'src/phaseSystemModels/multiphaseInter/phasesSystem/InterfaceCompositionModel/InterfaceCompositionModel.H'
'src/phaseSystemModels/multiphaseInter/phasesSystem/interfaceCompositionModel/interfaceCompositionModel.H'
'src/phaseSystemModels/reactingEuler/multiphaseSystem/interfacialCompositionModels/interfaceCompositionModels/InterfaceCompositionModel/InterfaceCompositionModel.C'
'src/phaseSystemModels/reactingEuler/multiphaseSystem/interfacialCompositionModels/interfaceCompositionModels/interfaceCompositionModel/interfaceCompositionModel.C'
'src/phaseSystemModels/reactingEuler/multiphaseSystem/interfacialCompositionModels/interfaceCompositionModels/InterfaceCompositionModel/InterfaceCompositionModel.H'
'src/phaseSystemModels/reactingEuler/multiphaseSystem/interfacialCompositionModels/interfaceCompositionModels/interfaceCompositionModel/interfaceCompositionModel.H'
'src/thermophysicalModels/chemistryModel/chemistryModel/BasicChemistryModel/BasicChemistryModel.C'
'src/thermophysicalModels/chemistryModel/chemistryModel/basicChemistryModel/basicChemistryModel.C'
'src/thermophysicalModels/chemistryModel/chemistryModel/BasicChemistryModel/BasicChemistryModel.H'
'src/thermophysicalModels/chemistryModel/chemistryModel/basicChemistryModel/basicChemistryModel.H'
'src/thermophysicalModels/chemistryModel/chemistryModel/BasicChemistryModel/BasicChemistryModelI.H'
'src/thermophysicalModels/chemistryModel/chemistryModel/basicChemistryModel/basicChemistryModelI.H'
'tutorials/combustion/PDRFoam/flamePropagationWithObstacles/0.orig/B.gz'
'tutorials/combustion/PDRFoam/flamePropagationWithObstacles/0.orig/b.gz'
'wmake/rules/General/CGAL'
'wmake/rules/General/cgal'
</pre>
It should be very easy to rename the conflicting directories and files maybe by adding an `_` to the end of some.https://develop.openfoam.com/Development/openfoam/-/issues/2043Renumbering mesh results in high non-orthogonality and skewness2021-04-15T08:57:40ZGhost UserRenumbering mesh results in high non-orthogonality and skewnessHello,
When I run the `checkMesh` utility in my case with the attached Grid `mesh.x`, it reports the following values of non-orthogonality and skewness (See the `checkMesh.beforeRenumbering` attached file for details):
**Before running...Hello,
When I run the `checkMesh` utility in my case with the attached Grid `mesh.x`, it reports the following values of non-orthogonality and skewness (See the `checkMesh.beforeRenumbering` attached file for details):
**Before running renumberMesh**:
```
Mesh non-orthogonality Max: 36.0957 average: 9.08335
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 2.03538 OK.
```
But when I run the renumberMesh utility, then checkMesh, I get the following (see `checkMesh.afterRenumbering` attached file):
**After running renumberMesh**:
```
Mesh non-orthogonality Max: 78.4614 average: 9.84955
*Number of severely non-orthogonal (> 70 degrees) faces: 26.
Non-orthogonality check OK.
<<Writing 26 non-orthogonal faces to set nonOrthoFaces
Face pyramids OK.
Max skewness = 3.322 OK.
Coupled point location match (average 0) OK.
Failed 1 mesh checks.
```
As you can see, the **max skewness becomes 3.322**, and the **max non-orthogonality becomes 78.4614**.
I wonder if this is a side-effect of renumbering the cells or is it a bug?
Thank you
**Note**:
to convert the mesh.x to OpenFOAM format, use: `plot3dToFoam -2D 0.01 -noBlank mesh.x`
**Attached files**:
[mesh.x](/uploads/398f669511ad3547d37385db6383b66b/mesh.x)
[checkMesh.beforeRenumbering](/uploads/1e6e09b3c8fbfab13039646c3db28f60/checkMesh.beforeRenumbering)
[checkMesh.afterRenumbering](/uploads/358d8b8b7eb0e0df2df265b343716c1b/checkMesh.afterRenumbering)https://develop.openfoam.com/Development/openfoam/-/issues/221renumberMesh doesn't work2016-08-26T05:29:46ZAdminrenumberMesh doesn't workI want to solve the DTC-Hull in interFoam solver with another ship. all the commands in allrun file work properly except "renumberMesh" with the following error.![Screenshot_from_2016-08-25_03-17-23](/uploads/16343e9389fbea7cd23573c74692...I want to solve the DTC-Hull in interFoam solver with another ship. all the commands in allrun file work properly except "renumberMesh" with the following error.![Screenshot_from_2016-08-25_03-17-23](/uploads/16343e9389fbea7cd23573c746927bbc/Screenshot_from_2016-08-25_03-17-23.png)https://develop.openfoam.com/Development/openfoam/-/issues/351renumberMesh no longer cleans up old ProcAdressing files in develop2018-05-29T05:39:48ZAdminrenumberMesh no longer cleans up old ProcAdressing files in developI'm unsure if this was intentional or by mistake, but renumberMesh no longer cleans up old ProcAdressing files. Any mesh changes done in parallel now require the manual cleanup of the ProcAdressing files, this functionality used to be pr...I'm unsure if this was intentional or by mistake, but renumberMesh no longer cleans up old ProcAdressing files. Any mesh changes done in parallel now require the manual cleanup of the ProcAdressing files, this functionality used to be provided by renumberMesh.
I've attached a pipe model with some faceZones that creates a porous jump using createBaffles in parallel and then runs renumberMesh and reconstruct. This no longer works due to out of date ProcAdressing files.
[tube_test_pj.tar.gz](/uploads/4cbaf933a3d1afc19178da2a92e74d55/tube_test_pj.tar.gz)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/344renumberMesh twice in the same workflow2018-05-29T05:39:49ZvilfayeaurenumberMesh twice in the same workflowHi,
In some situation, you have to run renumberMesh twice in the same workflow. For example, if you run a coarse case, map to a fine mesh and run it.
This leads to a error message:
Reading volScalarField cellID
[3]
[3]
[3] --> FOAM ...Hi,
In some situation, you have to run renumberMesh twice in the same workflow. For example, if you run a coarse case, map to a fine mesh and run it.
This leads to a error message:
Reading volScalarField cellID
[3]
[3]
[3] --> FOAM FATAL IO ERROR:
[3] size 58624 is not equal to the given value of 58185
[3]
[3] file: /home/a45bwpq/OpenFOAM/1606+/a45bwpq-16.06plus/tutorials/incompressible/simpleFoam/motorBike/processor3/constant/cellID from line 18 to line 58953.
[3]
[3] From function Foam::Field<Type>::Field(const Foam::word&, const Foam::dictionary&, Foam::label) [with Type = double; Foam::label = int]
[3] in file /appl/openfoam/16.06plus/OpenFOAM-16.06plus/src/OpenFOAM/lnInclude/Field.C at line 295.
[3]
FOAM parallel run exiting
motorBike test case is attached to reproduce the error.
Best,
Sebastien
[motorBike.tgz](/uploads/67b76ae6ecde6bb5fb8a3fa1179fdc9d/motorBike.tgz)https://develop.openfoam.com/Development/openfoam/-/issues/1645Re-open Issue: Gauss CoBlended scheme fails for div(phi,alpha) in interFoam2022-04-26T16:10:40ZLydia SchulzeRe-open Issue: Gauss CoBlended scheme fails for div(phi,alpha) in interFoam<!--
*** 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 ...<!--
*** 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
Note:
I re-open this issue, as it is still relevant and not fixed in the latest version.
The issue was already described in #1236 for version v1812.
When using the scheme Gauss CoBlended for the term div(phi,alpha) in the solver interFoam, the simulation breaks up with the following error message: fvSchemes:
```div(phi,alpha) Gauss CoBlended 1. Minmod 2. upwind;```
logfile output:
`\--> FOAM FATAL ERROR: Operator + is undefined for unoriented and oriented types From function Foam::orientedType Foam::operator+(const Foam::orientedType&, const Foam::orientedType&) in file orientedType/orientedType.C at line 458.`
### Steps to reproduce
Use tutorial /multiphase/RAS/interFoam/damBreak. Change in fvSchemes:
```div(phi,alpha) Gauss CoBlended 1. Minmod 2. upwind;```
Run the case with Allrun.
### Example case
The damBreak tutorial (tutorials/multiphase/RAS/damBreak)
### What is the current *bug* behaviour?
<!-- What actually happens -->
Run fails in first alpha-Subcycle.
See logfile output below.
### What is the expected *correct* behavior?
<!-- What you should see instead -->
Normal interFoam-running would be expected.
### 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.
-->
```Courant Number mean: 0 max: 0 Interface Courant Number mean: 0 max: 0 deltaT = 0.00119048 Time = 0.00119048 PIMPLE: iteration 1 smoothSolver: Solving for alpha.water, Initial residual = 0, Final residual = 0, No Iterations 0 Phase-1 volume fraction = 0.130194 Min(alpha.water) = 0 Max(alpha.water) = 1 --> FOAM FATAL ERROR: Operator + is undefined for unoriented and oriented types From function Foam::orientedType Foam::operator+(const Foam::orientedType&, const Foam::orientedType&) in file orientedType/orientedType.C at line 458.```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v1912
- Operating system : centos
- Hardware info :
- Compiler : gcc
### Possible fixes
<!--
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
-->v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1871replace autoPtr/tmp combination with refPtr2021-12-03T16:44:51ZMark OLESENreplace autoPtr/tmp combination with refPtrSome of the optimization code uses a combination of autoPtr and tmp to manage the referenced or local turbulence fields. This is ugly but works and was previously the only way to handle these variants.
In the meantime have a `refPtr` (f...Some of the optimization code uses a combination of autoPtr and tmp to manage the referenced or local turbulence fields. This is ugly but works and was previously the only way to handle these variants.
In the meantime have a `refPtr` (formerly called tmpNrc) which can wrap a reference or handle pointer management. Both `tmp` and `refPtr` now have three types of storage:
- PTR : Managing a pointer (not ref-counted)
- CREF : Using (const) reference to an object
- REF : Using (non-const) reference to an object
Can thus have storage with deletion, reference an external object, or a nullptr.
Using a `refPtr` instead of a `tmp` means that we shouldn't accidentally clear memory. Also no reference counting to get in the way.Vaggelis PapoutsisVaggelis Papoutsishttps://develop.openfoam.com/Development/openfoam/-/issues/3096replace listCombineReduce with allGatherList etc.2024-03-12T07:46:11ZMark OLESENreplace listCombineReduce with allGatherList etc.In places such as CloudIO.C, patchInjectionBase.C, turbulentDFSEMInletFvPatchVectorField.C (probably more), there is use of listCombineReduce to collect values from each processor into a list. This particular usage is directly equivalent...In places such as CloudIO.C, patchInjectionBase.C, turbulentDFSEMInletFvPatchVectorField.C (probably more), there is use of listCombineReduce to collect values from each processor into a list. This particular usage is directly equivalent to using allGatherList, which also corresponds to an MPI intrinsic for primitive types.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/2414report number of cells/faces capped by limitVelocity2022-04-25T11:49:45ZMark OLESENreport number of cells/faces capped by limitVelocitycf. EP1841
Also report relative (%) of cells/faces affected.cf. EP1841
Also report relative (%) of cells/faces affected.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/3Reposition fvMotionSolver in Allwmake2023-08-19T21:13:18ZPrashant SonakarReposition fvMotionSolver in AllwmakePlaceholder for resolution of mesh compilation, depending on fvMotionSolver
wmake $targetType fvMotionSolverPlaceholder for resolution of mesh compilation, depending on fvMotionSolver
wmake $targetType fvMotionSolverMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/78Request for a FAQ section on the Windows page2016-04-19T08:17:38ZAdminRequest for a FAQ section on the Windows pageAlthough the page on the [binary packages for Docker](http://openfoam.com/download/install-binary.php) has a FAQ section, the [one for Windows](http://openfoam.com/download/install-windows.php) currently does not :(
I'm asking you for...Although the page on the [binary packages for Docker](http://openfoam.com/download/install-binary.php) has a FAQ section, the [one for Windows](http://openfoam.com/download/install-windows.php) currently does not :(
I'm asking you for this here and not via email, given that this is more of a website-related issue than the project for the deployments of OpenFOAM+ with Docker (which would be nice to have one here in your Gitlab hub).
In addition, as a moderator on the CFD-Online forums, I've moved most of the threads on installation issues about OpenFOAM+ 3.0+ to the main [OpenFOAM installation forum](http://www.cfd-online.com/Forums/openfoam-installation/) - since OpenFOAM+ supports installation on Windows - and most of those threads currently have the prefix "[OpenFOAM plus]" to make it easier to spot them, simply by searching for `[OpenFOAM plus]` on this (sub)forum.
One thread in particular is what has lead me to create this bug report/feature request: [[OpenFOAM plus][3.0+] on Windows ---- How do I run tutorials?](http://www.cfd-online.com/Forums/openfoam-installation/165439-openfoam-plus-3-0-windows-how-do-i-run-tutorials.html)
Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/976Request for the thirdparty library version handling improvement2018-09-08T04:30:48ZAdminRequest for the thirdparty library version handling improvementI am using Lmod (environment module) for handling OpenFOAM-plus.
FYI, my Lmod file is attached.
Lmod comes in handy for OpenFOAM because it can manipulate environment variable dynamically as needed.
Most of the OpenFOAM behavior could b...I am using Lmod (environment module) for handling OpenFOAM-plus.
FYI, my Lmod file is attached.
Lmod comes in handy for OpenFOAM because it can manipulate environment variable dynamically as needed.
Most of the OpenFOAM behavior could be handled by Lmod without modifying bashrc and config.sh/* except thirdparty libraries.
The thirdparty libraries in ThirdParty-plus are referring to the script in OpenFOAM-plus/config.sh/* to get version information. Thus, the script file should be modified when building and installing OpenFOAM with custom thirdparty library version for the first time.
So I have a preference to have a way to get version information from environment variable without breaking OpenFOAM echo-system when it is possible.
I made some modification for the thirdparty library configurations in OpenFOAM/etc/config.sh as attached and hope this patch be reflected for better usability.
[latest.lua](/uploads/f9eab389272176e0a188e5b875535632/latest.lua)
[diff.patch](/uploads/95af7d4ea3734a2286a54801dc6df57a/diff.patch)[diff1.patch](/uploads/90133896d33aaf7083becd191246c620/diff1.patch)https://develop.openfoam.com/Development/openfoam/-/issues/1832REQUEST: Replace/Remove the terms "slave/master" and "blacklist/whitelist"2023-09-04T06:14:34ZKutalmış BerçinREQUEST: Replace/Remove the terms "slave/master" and "blacklist/whitelist"### Functionality
Replace/Remove all references to racially-charged jargon for neutral and inclusive terminology.
OpenFOAM should join the contemporary efforts of various tech companies and open-source projects in this regard, such as ...### Functionality
Replace/Remove all references to racially-charged jargon for neutral and inclusive terminology.
OpenFOAM should join the contemporary efforts of various tech companies and open-source projects in this regard, such as (the most recent) [Linux (kernel)](https://www.itpro.co.uk/software/development/356420/linux-kernel-to-strip-out-racially-insensitive-terms), GitHub, RedHat, Android etc.
[Proposed alternatives](https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/):
For `master/slave`:
```
primary/secondary
main/replica or subordinate
initiator/target
requester/responder
controller/device
host/worker or proxy
leader/follower
director/performer
```
For `blacklist/whitelist`:
```
denylist/allowlist
blocklist/passlist
```https://develop.openfoam.com/Development/openfoam/-/issues/1847REQUEST: snGrad field function object2020-09-21T07:59:30ZChiara PesciREQUEST: snGrad field function object### Functionality to add/problem to solve
It would be nice to have a field function object which computes the surface normal gradient (snGrad) at a boundary patch/patches, with patch name provided as input by the user.
### Proposal
Th...### Functionality to add/problem to solve
It would be nice to have a field function object which computes the surface normal gradient (snGrad) at a boundary patch/patches, with patch name provided as input by the user.
### Proposal
The field FO could look like the div or grad FOs.
Cheers,
ChiaraKutalmış BerçinKutalmış Berçinhttps://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/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/533Request to modify directory name2019-12-09T22:11:26ZAdminRequest to modify directory nameCould you give the directory and its source file for the solver, e.g. interCondensatingEvaporatingFoam, the same name?Could you give the directory and its source file for the solver, e.g. interCondensatingEvaporatingFoam, the same name?https://develop.openfoam.com/Development/openfoam/-/issues/1846REQUEST: yPlus FO error message in "postProcess -func yPlus" mode2021-09-14T15:29:00ZChiara PesciREQUEST: yPlus FO error message in "postProcess -func yPlus" mode### Functionality to add/problem to solve
When executing the yPlus function object as "postProcess -func yPlus" the following warning is issued:
```
--> FOAM Warning :
From virtual bool Foam::functionObjects::yPlus::execute()
i...### Functionality to add/problem to solve
When executing the yPlus function object as "postProcess -func yPlus" the following warning is issued:
```
--> FOAM Warning :
From virtual bool Foam::functionObjects::yPlus::execute()
in file yPlus/yPlus.C at line 166
Unable to find turbulence model in the database: yPlus will not be calculated
```
while running the FO as
`<solverName> -postProcess -func yPlus`
or directly during run time works fine.
### Proposal
It would be nice to substitute the warning message with something like "yPlus function in postProcess mode not supported". The current message is misleading and the user would think there is an error in the turbulence model setup, even though the latter is correct.v2112Kutalmış BerçinKutalmış Berçin