Development issueshttps://develop.openfoam.com/groups/Development/-/issues2024-02-16T13:40:05Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1634Style formatting config needed (e.g. clang-format)2024-02-16T13:40:05ZGerasimos ChourdakisStyle formatting config needed (e.g. clang-format)### Functionality to add/problem to solve
Add a [clang-format](https://clang.llvm.org/docs/ClangFormat.html) or similar system config file in the code repository, so that contributions to the repository or derived projects can follow th...### Functionality to add/problem to solve
Add a [clang-format](https://clang.llvm.org/docs/ClangFormat.html) or similar system config file in the code repository, so that contributions to the repository or derived projects can follow the [Coding Style Guide](https://develop.openfoam.com/Development/openfoam/wikis/Coding-Style-Guide).
Clang-format is an established formatting tool and integration is already provided in many editors and IDEs, including [Emacs](https://clang.llvm.org/docs/ClangFormat.html#emacs-integration), [Vim](https://clang.llvm.org/docs/ClangFormat.html#vim-integration), and [CLion](https://clang.llvm.org/docs/ClangFormat.html#clion-integration).
### Target audience
- Regular developers of OpenFOAM
- External contributors to OpenFOAM
- Contributors to third-party OpenFOAM projects (e.g. function objects, such as the [preCICE OpenFOAM adapter](https://github.com/precice/openfoam-adapter))
### Proposal
1. Create a `.clang-format` file, e.g. in the root directory of the repository, or any other directory preferred for developers' tools.
- For example, with `clang-format -style=llvm -dump-config > .clang-format`
2. Define the preferred rules following the [Clang-Format Style Options](https://clang.llvm.org/docs/ClangFormatStyleOptions.html). Beware that the rules may depend on the Clang-Format version.
### What does success look like, and how can we measure that?
Running `clang-format -i FILES` should reformat the source files `FILES` to follow the coding style guidelines.
### Links / references
- [Clang-Format Style Options](https://clang.llvm.org/docs/ClangFormatStyleOptions.html)
- [OpenFOAM Coding Style Guide](https://develop.openfoam.com/Development/openfoam/wikis/Coding-Style-Guide)
### Funding
I am not aware of existing functionality regarding this. However, it may have been already developed by other developers.https://develop.openfoam.com/Development/openfoam/-/issues/1399Suggestion for improvement of Code development guide2021-08-27T14:40:15ZJohan RoenbySuggestion for improvement of Code development guideCommunity contributors who want to fix a bug or make an improvement to OpenFOAM will often have an older compiled version of the OpenFOAM-plus develop branch on their local computer. The proper workflow for such people would (as I unders...Community contributors who want to fix a bug or make an improvement to OpenFOAM will often have an older compiled version of the OpenFOAM-plus develop branch on their local computer. The proper workflow for such people would (as I understand it) be to git pull the latest OpenFOAM-plus, recompile it and then introduce their changes in a bug-fix/feature branch derived from there.
However, if API changes have occurred since their last git pull, the recompilation will fail due to outdated dep files etc. Having to wait for a full recompilation of everything every time I wanted to contribute has been a source of frustration for me until I discovered the -u/-update flag of the Allwmake script, which removes deprecated files and directories so the updating becomes much faster.
I therefore suggest to make contributors aware of this flag in the code development guide [here](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-code-development).Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1796support for only single patch between processors (e.g. ProcessorTopology::pro...2023-06-22T14:01:45ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsupport for only single patch between processors (e.g. ProcessorTopology::procPatchMap())### Functionality to add/problem to solve
Some functionality only supports a single processor patch. Sometimes there can be more than one patch between processors. E.g. processorCyclic (processor patch with cyclic transformations), over...### Functionality to add/problem to solve
Some functionality only supports a single processor patch. Sometimes there can be more than one patch between processors. E.g. processorCyclic (processor patch with cyclic transformations), overset (introduces additional lduInterfaces to handle the interpolation)
See e.g.
```ProcessorTopology::procPatchMap()```
which is used to lookup a patch given a remote processor (used in snappyHexMesh/extrudeMesh)https://develop.openfoam.com/Development/openfoam/-/issues/3111Support for Radial Basis Function (RBF) based mesh deformation2024-03-21T11:43:48ZAqeel AhmedSupport for Radial Basis Function (RBF) based mesh deformation### Functionality to add/problem to solve
Large mesh deformations on complex meshes require specilized methods to avoid mesh quality issues.
It becomes challenging to control the mesh quality with existing displacement based mesh motion...### Functionality to add/problem to solve
Large mesh deformations on complex meshes require specilized methods to avoid mesh quality issues.
It becomes challenging to control the mesh quality with existing displacement based mesh motion solvers for large deformations.
In the OpenFOAM journal article [2] it was also mentioned that for large deformations advanced techniques could help. An extract form figure 12 caption: "These results highlight the need for advanced mesh motion techniques in OpenFOAM".
### Target audience
All practical FSI cases with complex meshes.
Mesh deformations with fine boundary layers.
### Proposal
RBF morphing techniques have proven to be robust for large variety of problems among others [2].
One of the motion solver using RFB is available in an another library solids4Foam [3]. However, this implementation relies on external library and is not maintained anymore. If possible, would really benefit the community if this could be implemented in OpenFOAM directly.
### What does success look like, and how can we measure that?
Ability to deform complex meshes with large deformations.
A minimal example is provided here:[flapDeformation.zip](/uploads/fa8541188d3a1c22eab91f2cc257a952/flapDeformation.zip)
[meshAndDefInfo.pdf](/uploads/239c5b577c90be8e7a96e22df3f367e6/meshAndDefInfo.pdf)
### Links / references
[1] OpenFOAM-preCICE: Coupling OpenFOAM with External Solvers for Multi-Physics Simulations. https://journal.openfoam.com/index.php/ofj/article/view/88
[2] CFD Methodology for Wind Turbines Fluid-Structure Interaction. https://theses.hal.science/tel-01562675
[3] https://github.com/solids4foam/solids4foam/tree/master/src/RBFMeshMotionSolverhttps://develop.openfoam.com/Development/openfoam/-/issues/1677Support rigidBodyMotionState object in writeObjects2021-07-07T08:16:22ZJaap StolkSupport rigidBodyMotionState object in writeObjects### Functionality to add/problem to solve
To reduce the number of fields files written by openFoam, the normal writes can be disabled with a very large write interval and a custom "writeObjects" can be used instead. This makes it possib...### Functionality to add/problem to solve
To reduce the number of fields files written by openFoam, the normal writes can be disabled with a very large write interval and a custom "writeObjects" can be used instead. This makes it possible to specify exactly which field(s) need to be written to disk. For users interested in the rigidBodyMotionState this does not work because it is not an "Available objects in database".
### Target audience
Anyone wanting more control over which fields are written to disk, and needing the rigidBodyMotionState.
Note that re-staring a case from a saved data point requires the rigidBodyMotionState file.
It can also be used for transformations in paraFoam, to invert or match the object motion.
(as workaround, a user could try to recreate the missing rigidBodyMotionState files from the orientation information in the log.interFoam file. And maybe there are other workarounds.)
### Proposal
If it is a database object but it is not listed for some reason, make sure rigidBodyMotionState is listed when available.
If rigidBodyMotionState is not a "real" database object, it may be possible to add an option to "writeObjects" to enable writing of non-real-databse-objects, similar to how the normal write writes these files, and probably similar to how the "time" file is not listed but is written automatically.
I don't know how complex this is to add. During a normal write they are written and in the rigidBodyMotionState files header claim to be a database object.
### What does success look like, and how can we measure that?
The rigidBodyMotionState(.gz) file appearing in the processor0/0.1/uniform folders.
### example case
Using the normal write:
- start with the multiphase/interFoam/RAS/DTCHullMoving example
- change endTime to 0.2 and writeInterval to 0.1 (to speed up the test)
- Allrun
- there now is a processor0/0.1/uniform/rigidBodyMotionState file.
Using a custom write with just "U" and "points":
- copy the attached controlDict in the multiphase/interFoam/RAS/DTCHullMoving example
- Allrun
- processor0/0.1 folder now only contains the selected (U) file.
Including "rigidBodyMotionState" results in warning and no file:
- copy the attached controlDict in the multiphase/interFoam/RAS/DTCHullMoving example
- uncomment the rigidBodyMotionState line in controlDict
- Allrun
- log.interFoam contains a warning for rigidBodyMotionState, and lists the 56 objects available in the database.
### Links / references
example [controlDict](/uploads/d5a3043780580a578e69e4fa655d64d2/controlDict)
resulting warning: [log.interFoam_snippet](/uploads/d01e48fe4aee07ebd258f57adfc593b2/log.interFoam_snippet)
typical result object file: [rigidBodyMotionState](/uploads/7551e066077c035de70b75d519199051/rigidBodyMotionState)https://develop.openfoam.com/Development/openfoam/-/issues/2000Support surface sampling on internal fields2021-02-09T19:26:52ZMark OLESENSupport surface sampling on internal fieldsMentioned on cfd-online, could be useful to sample internal (dimensioned) fields. Will work for many surface types, but might need special care for patch samplers etc.Mentioned on cfd-online, could be useful to sample internal (dimensioned) fields. Will work for many surface types, but might need special care for patch samplers etc.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1820Support wallHeatFluxCalculation on incompressible fluid (icoReactingMultiphas...2022-04-26T16:10:00ZThomas EnzingerSupport wallHeatFluxCalculation on incompressible fluid (icoReactingMultiphaseInterFoam solver)### Functionality to add/problem to solve
Actually wallHeatFlux can be only calculated with compressible fluids. A try with the icoReactingMultiphaseInterFoam solver runs into the error message
> Unable to find compressible turbulence ...### Functionality to add/problem to solve
Actually wallHeatFlux can be only calculated with compressible fluids. A try with the icoReactingMultiphaseInterFoam solver runs into the error message
> Unable to find compressible turbulence model in the database
>
> From virtual bool Foam::functionObjects::wallHeatFlux::execute()
> in file wallHeatFlux/wallHeatFlux.C at line
### Target audience
Who will benefit from the changes?
All cases that need an wallHeatFlux value with incompressible solvers.
Other software in that OpenFOAM is included build actually own solutions for the problem and try to detect compressible/incompressible solver type. (e.g. preCICE openfoam-adapter)
### Proposal
A solution is present since 2012.
https://github.com/wyldckat/wallHeatFluxIncompressible
A look to
https://github.com/precice/openfoam-adapter/tree/master/CHT
could be helping.
### Changes
- Edit title. Maybe a problem with the solver?v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/2265surfaceAlignedSBRStress mesh motion solver not working2021-12-14T23:08:59ZSaeedsaeed.salehi@chalmers.sesurfaceAlignedSBRStress mesh motion solver not working<!--
*** 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
The surfaceAlignedSBRStressFvMotionSolver mesh motion solver seems quite interesting to me and fits my research area. However, it appears that it does not work. The simulation crashes at the very first iteration with following error:
`--> FOAM FATAL ERROR: (openfoam-2106)`\
` [cellDisplacement[0 1 -1 0 0 0 0] ] + [div(sigmaD)[0 -1 0 0 0 0 0] ]`
### Steps to reproduce
Replace the mesh motion solver in the SnakeRiverCanyon tutorial with surfaceAlignedSBRStress. Extra entities need to be added to the dynamicMeshDict. For instance one might add the following lines:
`surfaces ("AcrossRiver.stl");`\
`nNonOrthogonalCorr 4;`
Also, a scheme needs to be provided for the "div(sigmaD)" in the fvSchemes. Then, run the case with the moveDynamicMesh utility and you will see the error.
### Example case
The above-described reproduction test case is also attached.
[surfaceAlignedSBRStress.tar.gz](/uploads/ef13f393a7a0f973a7d59d56bfbedbb5/surfaceAlignedSBRStress.tar.gz)
### What is the current *bug* behaviour?
The surfaceAlignedSBRStress mesh motion solver is similar to the displacementSBRStress with an extra source term to make the close cells to an STL surface aligned to the surface. I am not sure what is wrong here. The implementation of the source term seems rather complex. But since there is a dimensionality check error, it could be that the formulation is somehow not correct. The error is thrown when the DEqn is to be constructed.
### What is the expected *correct* behavior?
The expected correct behavior is to run without error!!!
### Environment information
I checked this on v1912, v2006, v2012, and v2106. They all throw the same error.https://develop.openfoam.com/Development/openfoam/-/issues/1486surfaceFeatureExtract trims all features on a brick when minElem > 12020-01-06T19:29:41ZAdminsurfaceFeatureExtract trims all features on a brick when minElem > 1### Summary
Not sure if this is a bug report of a feature request, but here it goes.
When I extract features on a brick defined by an stl file, the edge features (12 of them) only get extracted if trimFeatures minElem is not used or set...### Summary
Not sure if this is a bug report of a feature request, but here it goes.
When I extract features on a brick defined by an stl file, the edge features (12 of them) only get extracted if trimFeatures minElem is not used or set to something not higher than 1. Since all the features are "connected" on the brick, I would have expected features to not be trimmed until at least a value of 13 on minElem.
This probably gets into how you are determining the number of elements in feature strings. In other software I've used, they generally separate things into "connected" feature groups and then apply element filtering to each of those. For example, a brick would have 12 connected feature edges and be in one group, so a minElem of 2 shouldn't trim any of the features, but in surfaceFeatureExtract, it does.
### Steps to reproduce
Run surfaceFeatureExtract on the attached brick model. No features will be extracted because minElem is set to 2. If you set it to 1, the features get extracted.
### Example case
[brick.zip](/uploads/be63b675856f5a189e7cd6035e0294e6/brick.zip)
### What is the current *bug* behaviour?
No features will be extracted because minElem is set to something above 1.
### What is the expected *correct* behavior?
I would expect all features to be extracted until minElem reaches 13, since there are 12 connected feature edges on a brick.
### Environment information
OpenFOAM version : v1906
Operating system : RHEL / Windows
Compiler : gcc / MinGW
### Possible fixes
I looked in surfaceFeatures.C to try and glean how feature strings were being determined, but I was unable to decipher the strategy being used. My guess is that there is a difference in strategy, if that's the case, then this is a feature request.
\## Reattaching the author to the issue ticket: @graups ##https://develop.openfoam.com/Development/openfoam/-/issues/2272surface file reader for ftr and off files2021-12-10T13:06:38ZBas Nieuwboersurface file reader for ftr and off files<!--
*** 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
I've come across two issues with surface files:
- surfaceTransformPoints does not support ftr file.
- off files are read without reading the region (patch) information. While it seems to be present in the file.
Both these issues are non-essential for me, since I never use these file types. I've created this bug-report to let you know the inconsistency in the use of these files. Therefore a result of this report could be that it is not worth the time to look into this.
### Steps to reproduce
I found the issue in creating a tool, described in: In https://develop.openfoam.com/Development/openfoam/-/issues/2239#note_54832
The test.sh file in this post, illustrates both issues. @mark already commented on the issues in this post: https://develop.openfoam.com/Development/openfoam/-/issues/2239#note_54835
### 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
OpenFOAM version : v2106v2212https://develop.openfoam.com/Development/openfoam/-/issues/2295swirl bc does not handle cyclic being decomposed2021-12-10T19:57:14ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comswirl bc does not handle cyclic being decomposed### Functionality to add/problem to solve
swirl bc 'sits' on a cyclic patch. However the patch might get decomposed into a processorCyclic (if the owner and neighbour are not on the same processor). This looses the extra physics from th...### Functionality to add/problem to solve
swirl bc 'sits' on a cyclic patch. However the patch might get decomposed into a processorCyclic (if the owner and neighbour are not on the same processor). This looses the extra physics from the swirl/jump bc (since it has zero faces on the original patch). In addition the particular swirlVelocity bc expects at least one local face on the patch to be able to calculate the swirl axis.
### Proposal
Avoid by e.g. having decomposition constraints:
```
constraints
{
patches
{
//- Keep owner and neighbour on same processor for faces in patches
// (only makes sense for cyclic patches and cyclicAMI)
type preservePatches;
patches (cyclic);
}
}
```
Or maybe add constraint override to decomposePar so the bc type is now again swirl instead of processorCyclic. However now this patch might not be present on all processors or at a different index in the patch list.
@Prashant @markhttps://develop.openfoam.com/Development/openfoam/-/issues/2925Tensor operations: taking the inner product of three tensors produces a diffe...2023-11-17T19:24:36ZRyley McConkeyTensor operations: taking the inner product of three tensors produces a different result depending on if an intermediate variable is used<!--
*** 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
The following operations do not produce the same result for C :
1. C = A & A & A;
2. B = A & A; then C = B & A;
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Here is an example set of operations. Tensors B2a and B2b should be equal (since they are both S & S & S), but the results are different.
```
S = symm(fvc::grad(U));
B1 = S & S;
B2a = S & S & S;
B2b = B1 & S;
```
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
I have attached an example case and example application that writes the above two results.
### What is the current *bug* behaviour?
A different result is produced for the two operations.
<!-- What actually happens -->
### What is the expected *correct* behavior?
The two operations should produce the same result. I believe the second result (after using an intermediate variable) is correct mathematically. I am not sure yet what operation is being performed in the first case (S & S & S).
<!-- 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.
-->
![Screenshot_from_2023-06-29_14-10-26](/uploads/cd1596da5d86af14d126bc93c02b109d/Screenshot_from_2023-06-29_14-10-26.png)
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v2212|v2206|v2112|v2106|v2012 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
- OpenFOAM version : v2112
- Operating system :
- Hardware info :
- Compiler :
### 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
-->[case_0p5.zip](/uploads/bb01c9483630e4766047cdd604e4a897/case_0p5.zip)[writeFields_test.zip](/uploads/e1acfc378b8ff008c795511c01ca5bec/writeFields_test.zip)Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/84timeVaryingMappedFixedValue uses linear extrapolation if outside triangulation2019-12-11T16:52:37ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtimeVaryingMappedFixedValue uses linear extrapolation if outside triangulationtimevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest...timevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest triangle. This is generally not ideal and especially very high aspect ratio triangles it gives problems (e.g. interpolation weights (23937.3 -48293 24356.7)
I think we should use zero-gradient outside triangles.
https://develop.openfoam.com/Development/openfoam/-/issues/1353topoSet: No warning when using inconsistent setup2019-07-03T04:56:26ZPrashant SonakartopoSet: No warning when using inconsistent setup### Functionality to add/problem to solve
When setup is inconsistent, e.g. type cellSet, while source e.g. boxToFace, there is no warning/ error.
The cellSet is created with faces as labels. This should be checked for consistency.
@mark### Functionality to add/problem to solve
When setup is inconsistent, e.g. type cellSet, while source e.g. boxToFace, there is no warning/ error.
The cellSet is created with faces as labels. This should be checked for consistency.
@markhttps://develop.openfoam.com/Development/openfoam/-/issues/2024topoSet with faceSetToZone2024-02-22T10:08:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtopoSet with faceSetToZone### Functionality to add/problem to solve
I would like to be able to do:
```
{
name intFaceZone;
type faceZoneSet;
action new;
source boundaryToFace;
}
{
name intFaceZone;
...### Functionality to add/problem to solve
I would like to be able to do:
```
{
name intFaceZone;
type faceZoneSet;
action new;
source boundaryToFace;
}
{
name intFaceZone;
type faceZoneSet;
action invert;
}
```
but this gives
```
Created faceZoneSet intFaceZone
Applying source boundaryToFace
Adding all boundary faces ...
--> FOAM Warning :
From virtual void Foam::faceZoneSet::sync(const Foam::polyMesh &)
in file sets/topoSets/faceZoneSet.C at line 331
Detected 6880 faces that are in the faceZone but not in the faceSet or vice versa. The faceZoneSet should only be manipulated using setsToFaceZone or setToFaceZone
faceZoneSet intFaceZone now size 0
Read set faceZoneSet intFaceZone with size 0
Inverting faceZoneSet
faceZoneSet intFaceZone now size 22640
```
@mark @Prashanthttps://develop.openfoam.com/Development/openfoam/-/issues/1581transient solver with suitable ddtScheme2020-02-03T12:37:26ZPrashant Sonakartransient solver with suitable ddtScheme### Functionality to add/problem to solve
Trying to run a transient solver with 'steadyState' as ddtScheme usually causes a divide by zero (sigfpe). This is quite an easy mistake to make when starting from a steady-state solution.
###...### Functionality to add/problem to solve
Trying to run a transient solver with 'steadyState' as ddtScheme usually causes a divide by zero (sigfpe). This is quite an easy mistake to make when starting from a steady-state solution.
### Proposal
Would be nice to give a warning message. It still should be possible in general (e.g. to replace an outer loop with the time loop).
Cross Ref: EP#1204https://develop.openfoam.com/Development/openfoam/-/issues/3040Turbulence model not runtime selectable2023-12-05T11:50:08ZBas NieuwboerTurbulence model not runtime selectable<!--
*** 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
When I change a turbulence model during runtime, the turbulence properties are re-read as shown by the log: "Re-reading object turbulenceProperties from file ". However, the turbulence model itself does not change. I've tested this on openfoam V2306 and V1712 (oldest one I have on my machine).
It might be a design choice not to have this feature. However, I cannot find any warning on this in the documentation (or in the log). I might be a an odd one, wanting to change the turbulence model during runtime. I would like to change the turbulence model, since it allows using a more stable turbulence model during startup and changing it to a more accurate one during runtime.
### Steps to reproduce
1) Take the incompresseble TJunction case: (tutorials/incompressible/pimpleFoam/RAS/TJunction)
2) Increase the simulated time (say 15 s) to ensure you have time to change the turbulence dict before the end of the simulation
3) run blockMesh
4) run pimpleFoam > log
5) Change the turbulence model to kOmega in turbulenceProperties
- This should cause a crash, since the Omega field is not created/read. However, the solver just keeps on running
- Check if the turbulence properties is changed by looking for: "Re-reading object turbulenceProperties from file " in the log file.
### Example case
the incompresseble TJunction case: (tutorials/incompressible/pimpleFoam/RAS/TJunction)
### What is the current *bug* behaviour?
The simulation keeps on running using the kEpsilon model
### What is the expected *correct* behavior?
The simulation should crash, since the Omega field is not present.
### Environment information
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : aff5c3b680-20230703 OPENFOAM=2306 version=v2306 | v1712
Operating system : ubuntu 18.04
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
-->https://develop.openfoam.com/Development/openfoam/-/issues/2420tutorial "rigidBodyHull" crashes after applying "prescribedRotation" restrain...2022-03-23T08:11:25ZLu Xintutorial "rigidBodyHull" crashes after applying "prescribedRotation" restraint to the propeller<!--
*** 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 -->
The tutorial case crashes soon after applying a prescribed rotational motion to the propeller.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
append the following after the 'force' restraint
propellerRotation
{
type prescribedRotation;
body propeller;
referenceOrientation (1 0 0 0 1 0 0 0 1);
axis (1 0 0);
omega table
(
(0 (0 0 0))
(50.0 (10.0 0 0))
);
relax 0.5;
p 0.6;
i 0.6;
d 0.6;
}
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
### What is the current *bug* behaviour?
<!-- What actually happens -->
Program crashes
### What is the expected *correct* behavior?
<!-- 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 : v2112|v2106|
Operating system : centos
Compiler : gcc
-->
- OpenFOAM version :v2112|v2106
- Operating system :centos
- 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
-->
The program runs well if the hull is only allowed to do translations.https://develop.openfoam.com/Development/openfoam/-/issues/3103unable to use mpirun in precomplied windows version2024-03-04T06:18:45Z加成 唐unable to use mpirun in precomplied windows versionHi,It's maybe a stupid question and I'm new to openfoam. but I can't use mpi to run job in paraell in precomplied openfoam at windows platform.
I'm using `mpirundebug -normal -np 6 potentialFoam -parallel`
and I'm getting
```
Error enc...Hi,It's maybe a stupid question and I'm new to openfoam. but I can't use mpi to run job in paraell in precomplied openfoam at windows platform.
I'm using `mpirundebug -normal -np 6 potentialFoam -parallel`
and I'm getting
```
Error encountered:
Unsupported WM_MPLIB setting : MSMPI
```
and I already installed msmpi like
![image](/uploads/108b30df08e09bf572264bd473138d4e/image.png)
Thanks for helping!Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/999unavailable "timeExample" V&V testcase2023-05-17T15:57:13ZAdminunavailable "timeExample" V&V testcaseThe documentation describes an example of various time schemes (ref. 1) with a link to a V&V testcase, timeExample (ref. 2).
The specific case seem to be unavailable in the repository (when following the link I get error 404: The page c...The documentation describes an example of various time schemes (ref. 1) with a link to a V&V testcase, timeExample (ref. 2).
The specific case seem to be unavailable in the repository (when following the link I get error 404: The page could not be found or you don't have permission to view it.).
References:
1) https://openfoam.com/documentation/cpp-guide/html/guide-schemes-time-example.html
2) https://develop.openfoam.com/development/OpenFOAM-plus/tree/master/tutorials/verificationAndValidation/schemes/timeExample
\## Reattaching the author to the issue ticket: @michele ##v2012Kutalmış BerçinKutalmış Berçin