Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T22:04:15Zhttps://develop.openfoam.com/Development/openfoam/-/issues/376meshToMesh - incorrect cutting patch addressing2019-12-09T22:04:15ZAdminmeshToMesh - incorrect cutting patch addressingcutting patches indices are derived by finding the patch name on the tgtRegion - this should be performed on the srcRegion. Also, there is no protection for the case that the patch is not found, where the patch index is set to -1.cutting patches indices are derived by finding the patch name on the tgtRegion - this should be performed on the srcRegion. Also, there is no protection for the case that the patch is not found, where the patch index is set to -1.Version v1706https://develop.openfoam.com/Development/openfoam/-/issues/1511ensightReadFile ignores string limits2019-12-09T22:37:29ZMark OLESENensightReadFile ignores string limitsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1132rotorDisk tutorial uses 'slip' patch type2018-12-24T08:58:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrotorDisk tutorial uses 'slip' patch typeMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1472dynamicCode should use polling instead of re-checking only once2020-06-05T08:12:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdynamicCode should use polling instead of re-checking only once### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' secon...### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' seconds and rechecks. If this fails the code will fail. Nicer if the check gets done multiple times before failing.
Alternatively send over the library (is this possible? is it cross-node compatible?)https://develop.openfoam.com/Development/openfoam/-/issues/1510support specified time for transformPoints2019-12-15T21:09:38ZPrashant Sonakarsupport specified time for transformPoints### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constant### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1001IOstream uses pointer instead of bool operator2018-09-11T12:16:52ZMark OLESENIOstream uses pointer instead of bool operatorMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1341Improve lumped point functionality2020-06-19T14:38:04ZMark OLESENImprove lumped point functionality- Alternative euler orders for lumped point definitions
- with the more recent changes to quaternion and euler coordinate rotations we can now also support rotations
beyond the standard 'ZXZ' euler intrinsic rotations.
- cross ref: E...- Alternative euler orders for lumped point definitions
- with the more recent changes to quaternion and euler coordinate rotations we can now also support rotations
beyond the standard 'ZXZ' euler intrinsic rotations.
- cross ref: EP 1008
- Support multiple controllers (not just a single axis)
- Enable VTK output in parallel
Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/983BUG: externalWallHeatFluxTemperatureFvPatchScalarField crashes on reconstruct...2019-12-09T22:22:46ZAdminBUG: externalWallHeatFluxTemperatureFvPatchScalarField crashes on reconstructPar when qrName != nonev1812https://develop.openfoam.com/Development/openfoam/-/issues/1429Suggestions for the Submitting Issues page2019-11-12T14:37:03ZAdminSuggestions for the Submitting Issues page# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fix...# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fixes
## Patches for page "Submitting Issues"
I had a look into the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues) and I added a bit more information, trying to keep the text short and the instructions precise and platform-independent. Since I cannot open merge requests or even fork the repository, I attach a set of patches here (they are for the Wiki repository, anyway). These patches are based on d8c4d7 and I have tested them locally.
[wiki_Submitting-Issues_patches.tar.gz](/uploads/3ad5ce768f455724b1077150d59c21ab/wiki_Submitting-Issues_patches.tar.gz)
<p>
<details>
<summary>Here is a preview:</summary>
![Screenshot_from_2019-09-05_16-40-55](/uploads/422c9f0ab4f069a1bdbc713814bc87fb/Screenshot_from_2019-09-05_16-40-55.png)
</details>
</p>
## Add link on openfoam.com
A link to the page [Bug Reporting](https://www.openfoam.com/code/bug-reporting.php) is very prominent both in the side menu and in the "Code" drop-down. :+1:
However, the statement:
> Bug and issue reporting is provided via the repository hosting site https://develop.openfoam.com described [here](https://www.openfoam.com/code/repositories.php)
leads to a generic page, while it should lead to the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues).https://develop.openfoam.com/Development/openfoam/-/issues/1410FDICSmoother and SPDP2023-12-07T19:05:02ZAdminFDICSmoother and SPDPHi, just a small one:
Should the following members of `FDICSmoother.H` be `solveScalarFields` instead?
```
scalarField rD_;
scalarField rDuUpper_;
scalarField rDlUpper_;
```
Like its done in DICSmoother.H.Hi, just a small one:
Should the following members of `FDICSmoother.H` be `solveScalarFields` instead?
```
scalarField rD_;
scalarField rDuUpper_;
scalarField rDlUpper_;
```
Like its done in DICSmoother.H.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1413`apt update` missing from the System Requirement instructions2019-11-12T14:03:21ZAdmin`apt update` missing from the System Requirement instructionsI've noticed a few minutes ago, while looking into this thread: https://www.cfd-online.com/Forums/openfoam-installation/220196-question-cmake-ubuntu-prerequisite.html - that the "System Requirements" page: https://www.openfoam.com/docum...I've noticed a few minutes ago, while looking into this thread: https://www.cfd-online.com/Forums/openfoam-installation/220196-question-cmake-ubuntu-prerequisite.html - that the "System Requirements" page: https://www.openfoam.com/documentation/system-requirements.php - is missing a critical command:
```
sudo apt-get update
```
for Ubuntu/Debian instructions; without this, `apt` and `apt-get` will fail miserably if the auto-update system didn't kick-in soon enough or because it never does when using WSL.
As a side note, you can change `apt-get` to `apt` for the more recent versions of Ubuntu/Debian, which provides a nicer interface and progress bar... even though it still doesn't run `update` on its own...https://develop.openfoam.com/Development/openfoam/-/issues/1416MergeMeshes overset cell vertex messing2019-09-12T13:52:23ZMatej FormanMergeMeshes overset cell vertex messingBackground overset mesh created with SHM is nice and castellated.
Overset mesh is created with SHM. Mesh is nice cylinder and rather OK quality.
After the mergeMeshes the following happens
![Screenshot_2019-08-29_at_14.21.41](/uploads/...Background overset mesh created with SHM is nice and castellated.
Overset mesh is created with SHM. Mesh is nice cylinder and rather OK quality.
After the mergeMeshes the following happens
![Screenshot_2019-08-29_at_14.21.41](/uploads/96a08c28645462afa4811ea7fe385938/Screenshot_2019-08-29_at_14.21.41.png)
MergeMesh is NOT run in parallel. When renumbering meshes before merging, only one pierced cell is created, when not renumbering, more are created. Mesh has 8 mil. cells
@Mattijs @Sergiohttps://develop.openfoam.com/Development/openfoam/-/issues/1437overset: normalisation of new matrix entries for interpolated/hole cells does...2019-09-17T13:27:42ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comoverset: normalisation of new matrix entries for interpolated/hole cells does not include remote contributions<!--
*** 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
<!-- Summarize the bug encountered concisely -->
Division by zero (producing sigfpe) in the linear solver for p in some decompositions.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
basic/overPotentialFoam/cylinder/cylinderAndBackground and use e.g.
```
//- The total number of domains (mandatory)
numberOfSubdomains 30;
//- The decomposition method (mandatory)
method random;
```
The idea is that it creates cells where all the neighbours are on other processors. This leads to a zero normalisation in the matrix rewrite.
### 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 : v1906, develop
### 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
-->
When inserting the new matrix 'rows' for interpolated and/or hole cells make sure to use a normalisation that includes the remote contributions.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/902BUG: foamToEnsight replaces ":" with "_" for Lagrangian file names but retain...2020-06-22T15:13:04ZAdminBUG: foamToEnsight replaces ":" with "_" for Lagrangian file names but retains ":" in .case filefoamToEnsight replaces ":" with "_" when writing out Lagrangian file names. However, the .case file retains the ":" when listing the filenames for ensight to read. This results in a file read error when reading into EnSight.
[simple_spr...foamToEnsight replaces ":" with "_" when writing out Lagrangian file names. However, the .case file retains the ":" when listing the filenames for ensight to read. This results in a file read error when reading into EnSight.
[simple_spray_steady_good.case](/uploads/e5f3eb73f8b14dff94bcb333b019e50b/simple_spray_steady_good.case)
\#\# Reattaching the author to the issue ticket: @graups \#\#Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1479Broken link on openfoam.com2019-11-12T21:12:22ZAdminBroken link on openfoam.comOn [this website](https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-input-types.html) and many other sites, you have a button labeled "Create an issue" with a link to [this site](https://develop.openfoam.com/Communi...On [this website](https://www.openfoam.com/documentation/guides/latest/doc/openfoam-guide-input-types.html) and many other sites, you have a button labeled "Create an issue" with a link to [this site](https://develop.openfoam.com/Community/Documentation/issues/new?issue[title]=Doc%20improvement:%20Add%20your%20title%20here&issue[description]=Page:%20openfoam-guide-input-types%0A%0ADescribe%20your%20proposed%20changes%0A%0A%3C!--%20Do%20not%20edit%20below%20this%20line%20--%3E%0A%0A%2Flabel%20~improvement) . The link is HTTP 404 Not found.
I would recommend fixing this link and the use of an automatic broken link checker.https://develop.openfoam.com/Development/openfoam/-/issues/1395AMI zone inside another AMI zone2019-09-11T21:51:42ZAdminAMI zone inside another AMI zone### Functionality to add/problem to solve
Is it possible to run an AMI zone within another AMI zone? My case involves a cycloidal propeller, in which five blades will rotate together as a single AMI zone, and then each single blade will...### Functionality to add/problem to solve
Is it possible to run an AMI zone within another AMI zone? My case involves a cycloidal propeller, in which five blades will rotate together as a single AMI zone, and then each single blade will independently vary its pitch as an embedded AMI within the enclosing AMI.
### Target audience
Will benefit turbomachinery folks as well as those with geometrically complex problems.
### Proposal
(How are we going to solve the problem?)
Sounds like lots of additional bookkeeping to me.
### What does success look like, and how can we measure that?
(What are the success factors and acceptance criteria? e.g. test cases, error margins)
Success will enable solution of the above driver problem.
### Links / references
(Links to literature, supporting information)
none
### Funding
(Does the functionality already exist/is sponsorship available?)
Ansys Fluent supports this. Sorry, no known sponsorship. Am seeking funding to do this type of work myself.https://develop.openfoam.com/Development/openfoam/-/issues/755faceSet and cellSet also in topoSet, setSet2020-06-18T21:27:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfaceSet and cellSet also in topoSet, setSetIntegrate the checkMesh -writeSets functionality into topoSet, setSet. Especially the parallel reconstruction is very useful. (or have parallel set handling inside paraFoam)Integrate the checkMesh -writeSets functionality into topoSet, setSet. Especially the parallel reconstruction is very useful. (or have parallel set handling inside paraFoam)https://develop.openfoam.com/Development/openfoam/-/issues/1489LiquidEvaporationBoil spalding number defined on molar basis2019-12-24T10:34:28ZAdminLiquidEvaporationBoil spalding number defined on molar basisIn OpenFOAM-2.4.0 at **src/lagrangian/intermediate/submodels/Reacting/PhaseChangeModel/LiquidEvaporationBoil/LiquidEvaporationBoil.C**
line 318:
dMassPC[lid] += pi d Sh Dab rhos log(1.0 + Xr) dt;
where d is the droplet diameter, Sh is...In OpenFOAM-2.4.0 at **src/lagrangian/intermediate/submodels/Reacting/PhaseChangeModel/LiquidEvaporationBoil/LiquidEvaporationBoil.C**
line 318:
dMassPC[lid] += pi d Sh Dab rhos log(1.0 + Xr) dt;
where d is the droplet diameter, Sh is the Sherwood number (Sh(Re,Sc)), Dab the vapor diffusivity assuming properties at the film, rhos the density at the film and Xr (line313):
// molar ratio
const scalar Xr = (Xs - Xc)/max(SMALL, 1.0 - Xs);
The units of dMassPC are in kg. However, the dimensionless group Xr is expressed in terms of molar fractions.
In literature, Xr is better known as the Spalding mass number (BM) where the ratio is expressed in terms of mass fractions rather than molar fractions [1,2]
I wonder if there is an implementation reason, which I do not see immediately, or if this is an implementation issue that should be fixed in order to correctly predict the evaporation rate.
Thank you in advance for your support and reply.
Alessandro
[1] Sergei S. Sazhin, Advanced models of fuel droplet heating and evaporation, Progress in Energy and Combustion Science, Volume 32, Issue 2, 2006.
[2] Patrick Jenny, Dirk Roekaerts, Nijso Beishuizen, Modeling of turbulent dilute spray combustion, Progress in Energy and Combustion Science, Volume 38, Issue 6, 2012.
\## Reattaching the author to the issue ticket: @pappo1890 ##https://develop.openfoam.com/Development/openfoam/-/issues/545Problem with BC for upwind discretization causing oscillating/negative soluti...2020-10-02T23:27:10ZAdminProblem with BC for upwind discretization causing oscillating/negative solution (tested in 1D scalarTransportFoam)As described here
https://www.cfd-online.com/Forums/openfoam-bugs/188749-negative-values-scalartransportfoam-upwind-discretization.html
the usage of upwind discretization does not prevent the appearance of oscillations in the scalar fiel...As described here
https://www.cfd-online.com/Forums/openfoam-bugs/188749-negative-values-scalartransportfoam-upwind-discretization.html
the usage of upwind discretization does not prevent the appearance of oscillations in the scalar field with scalarTransportFoam in the standard 1D convection-diffusion test case (i.e. T(0)=0 and T(L)=1 with advection dominated flow), where the region with the high gradient is located directly at the x=L boundary.
If the gradient is located in the volume (by adding a volume source term for T vie the fvOptions and setting the BC at x=L to zeroGradient), the upwind discretization behaves as expected, giving a smooth (overly-diffusive) solution over the entire volume. This points to a problem with the boundary conditions.
\## Reattaching the author to the issue ticket: @Mesl ##https://develop.openfoam.com/Development/openfoam/-/issues/380cell determinant not normalised2019-12-09T21:29:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcell determinant not normalisedpolyMeshGeometry::cellDeterminant is not normalised. For internal cubic cells it returns 8. Propose to normalise it to 0..1.polyMeshGeometry::cellDeterminant is not normalised. For internal cubic cells it returns 8. Propose to normalise it to 0..1.