Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-03-30T14:43:03Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1262Processor Boundary Conditions2019-03-30T14:43:03ZAdminProcessor Boundary ConditionsDear Developers,
Suppose we have a domain and let a cell, say owner, own a face, say facei, whose downstream cell, say neighbour, be internal cells of the domain. While running application in parallel, let facei be a processor boundary...Dear Developers,
Suppose we have a domain and let a cell, say owner, own a face, say facei, whose downstream cell, say neighbour, be internal cells of the domain. While running application in parallel, let facei be a processor boundary and let cell owner be in a subdomain, say OwnerSubdomain and neighbour be in the neighbouring subdomain, say NeighbourSubdomain. If we have a volVectorfield, say U, and run a solver like icoFOAM to solve the laplace equation or any other equation for that matter, say
fvVectorMatrix UEqn
(
fvm::ddt(U)
+ fvm::div(phi, U)
- fvm::laplacian(nu, U)
);
, when we assemble the matrix and inspect its assembly, the value of the neighbour velocity are suppose to appear as the Boundary field of facei when in ownersubdomain. Also the value of U[owner] are suppose to appear as U.boundaryField()[patchID][faceID] in the neighbourSubdomain corresponding to facei. see the code below.
forAll(mesh.C(), cellid)
{
const cell& faces = mesh.cells()[cellid];
label face;
forAll( faces, faceid)
{
face = faces[faceid];
if(mesh.isInternalFace(face))
{
continue;
}
else
{
label patchID = mesh.boundaryMesh().whichPatch(face);
label faceID = mesh.boundaryMesh()[patchID].whichFace(face);
if( mesh.boundaryMesh()[mesh.boundaryMesh().whichPatch(face)].type() == "processor" )
Pout<<"\n\nFace:\t"<<face<<"\tFace centr:\t"<<mesh.Cf()[face]<<"\tOwner:\t"<<mesh.owner()[face]<<"\tU:\t"<<U[mesh.owner()[face]]<<"\tDiagonal:\t"<<
UEqn.diag()[mesh.owner()[face]]<<"\tSourceU\t"<<UEqn.source()[mesh.owner()[face]][0]
<<"\tSourceV\t"<<UEqn.source()[mesh.owner()[face]][1]<<"\tSourceW\t"<<UEqn.source()[mesh.owner()[face]][2]
<<"\nType\t"<< mesh.boundaryMesh()[mesh.boundaryMesh().whichPatch(face)].type()
<<"\tPatchName:\t"<<mesh.boundaryMesh()[mesh.boundaryMesh().whichPatch(face)].name()<<
"\tU boundary field:\t"<<U.boundaryField()[patchID][faceID]<<"\tBoundary Coeff:\t"<<
UEqn.boundaryCoeffs()[patchID][faceID]<<"\tInternal Coeff:\t"<<
UEqn.internalCoeffs()[patchID][faceID]<<"\n";
}
}
}
However, Openfoam moves a value U*DV/Dt (where U = velocity, DV = cell volume, Dt is timestep) to the source term which I think is an error. Please correct me if am wrong and explain the meaning of the quantity moved to the source. Also, please clarify the why we need the values of UEqn.boundaryCoeffs() since the out of core updates are performed explicitly.
Best,
Kamau K
University of North Texas.https://develop.openfoam.com/Development/openfoam/-/issues/809Error in documentation of effectivenessHeatExchangerSource in the Extended Co...2019-01-08T17:32:13ZAdminError in documentation of effectivenessHeatExchangerSource in the Extended Code GuideIn the Extended Code Guide, the table format for the effectiveness is written as:
(
0.02
(
(0.1 A)
(0.2 B)
(0.3 C)
),
0.04
(
(0.1 D)
...In the Extended Code Guide, the table format for the effectiveness is written as:
(
0.02
(
(0.1 A)
(0.2 B)
(0.3 C)
),
0.04
(
(0.1 D)
(0.2 E)
(0.3 F)
),
0.06
(
(0.1 G)
(0.2 H)
(0.3 I)
)
);
However, this format does not work. Instead, a working table looks like this:
(
(0.02
(
(0.1 A)
(0.2 B)
(0.3 C)
))
(0.04
(
(0.1 D)
(0.2 E)
(0.3 F)
))
(0.06
(
(0.1 G)
(0.2 H)
(0.3 I)
))
);
The documentation in the Extended Code Guide should be changed accordingly.https://develop.openfoam.com/Development/openfoam/-/issues/1152wmakeBuildInfo bash3 compatibility2019-12-09T22:37:27ZAdminwmakeBuildInfo bash3 compatibilityThere is a problem with using declare -A in wmakeBuildInfo if your bash version is less than 4 as associative arrays aren't available until version 4.
The libraries will build, except the global.Cver, which will be wrong and cause proble...There is a problem with using declare -A in wmakeBuildInfo if your bash version is less than 4 as associative arrays aren't available until version 4.
The libraries will build, except the global.Cver, which will be wrong and cause problems when building the applications.
It would be nice if there was a check for this and fixed to work even for bash version 3.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/975tutorials for compressible flow do not include the link to the source files2020-01-17T09:01:44ZAdmintutorials for compressible flow do not include the link to the source filesI'm trying to follow these tutorials regarding compressible flows:
https://www.openfoam.com/documentation/tutorial-guide/compressible.php
However they do not include the link towards the original source files. I would appreciate if yo...I'm trying to follow these tutorials regarding compressible flows:
https://www.openfoam.com/documentation/tutorial-guide/compressible.php
However they do not include the link towards the original source files. I would appreciate if you could help me find them and also add them to the pages.
\## Reattaching the author to the issue ticket: @foadsf ##https://develop.openfoam.com/Development/openfoam/-/issues/937decomposePar - disallow decomposition of 2D case along thickness2020-01-03T14:22:50ZPrashant SonakardecomposePar - disallow decomposition of 2D case along thicknessIs it possible to warn/ error when attempting to decompose along thickness?
@Mattijs @mark @andyIs it possible to warn/ error when attempting to decompose along thickness?
@Mattijs @mark @andyMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/81Build guide missing steps2016-03-15T11:22:33ZAdminBuild guide missing stepsIn http://www.openfoam.com/code/build-guide.php, after the cp -r step to copy the pitzDaily test cast to the local run directory, before blockMesh can find the input files you must "cd pitzDaily", then "blockMesh".In http://www.openfoam.com/code/build-guide.php, after the cp -r step to copy the pitzDaily test cast to the local run directory, before blockMesh can find the input files you must "cd pitzDaily", then "blockMesh".AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/819Documentation: Citation Instructions for OpenFOAM (ESI Group)2020-01-03T14:32:49ZKutalmış BerçinDocumentation: Citation Instructions for OpenFOAM (ESI Group)Hi,
There are many ways to reference OpenFOAM versions in an academic work, yet almost all of them are **heuristic**, to name but a few: https://www.cfd-online.com/Forums/openfoam/147217-how-do-i-cite-openfoam-documentation.html#post527...Hi,
There are many ways to reference OpenFOAM versions in an academic work, yet almost all of them are **heuristic**, to name but a few: https://www.cfd-online.com/Forums/openfoam/147217-how-do-i-cite-openfoam-documentation.html#post527834 ; https://openfoamwiki.net/index.php/FAQ/General ;
Is there any chance for OpenCFD to officially provide some instructions to the users on how to properly reference OpenFOAM, preferably **single** way?
IMHO, this might also be useful to OpenFOAM to quantify its (academic) impact in the long term.
Kind regards,
PS: Some examples:
https://www.ansys.com/en-gb/academic/terms-and-conditions
https://www-user.tu-chemnitz.de/~potts/nfft/doc.phpKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/807processorField FO cannot be used with 'postProcess -func'2018-07-04T10:47:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprocessorField FO cannot be used with 'postProcess -func'Put attached
[processorField](/uploads/88917ae3ececefb3629b9dc576537eb3/processorField)
in etc/caseDicts/postProcessing/fields/processorField and you can do
```
mpirun -np 2 postProcess -func processorField -parallel
```
Ok?
Put attached
[processorField](/uploads/88917ae3ececefb3629b9dc576537eb3/processorField)
in etc/caseDicts/postProcessing/fields/processorField and you can do
```
mpirun -np 2 postProcess -func processorField -parallel
```
Ok?
https://develop.openfoam.com/Development/openfoam/-/issues/876applications/test do not compile2018-12-21T18:07:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comapplications/test do not compileThe following do not compile:
```
List/Test-List.C
PackedList/Test-PackedList.C
rigidBodyDynamics/ (now needs Time&)
```The following do not compile:
```
List/Test-List.C
PackedList/Test-PackedList.C
rigidBodyDynamics/ (now needs Time&)
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1114No Iterations for U and p in tutorials/incompressible/simpleFoam/turbineSiting2019-12-18T16:20:42ZAdminNo Iterations for U and p in tutorials/incompressible/simpleFoam/turbineSiting****I just run the case from OpenFOAM-v1806/tutorials/incompressible/simpleFoam/turbineSiting. There is a problem about sloving the UEqn and pEqn. Log as shown below, Initial residual,Final residual amd No Iterations are always 0. I thin...****I just run the case from OpenFOAM-v1806/tutorials/incompressible/simpleFoam/turbineSiting. There is a problem about sloving the UEqn and pEqn. Log as shown below, Initial residual,Final residual amd No Iterations are always 0. I think this results from the ABL boundary condition, becasue there are no problems from other cases under tutorials/incompressible/simpleFoam. ****
============================================================
Starting time loop
Time = 1
smoothSolver: Solving for Ux, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uy, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uz, Initial residual = 0, Final residual = 0, No Iterations 0
GAMG: Solving for p, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0, global = 0, cumulative = 0
smoothSolver: Solving for epsilon, Initial residual = 0.0886043707687, Final residual = 0.00415880864373, No Iterations 3
smoothSolver: Solving for k, Initial residual = 0.999999999999, Final residual = 0.0561633717339, No Iterations 4
ExecutionTime = 1.14 s ClockTime = 1 s
Time = 2
smoothSolver: Solving for Ux, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uy, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uz, Initial residual = 0, Final residual = 0, No Iterations 0
GAMG: Solving for p, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0, global = 0, cumulative = 0
smoothSolver: Solving for epsilon, Initial residual = 0.0528178005233, Final residual = 0.00435780437261, No
Iterations 2
smoothSolver: Solving for k, Initial residual = 0.49548245865, Final residual = 0.0477465631246, No Iterations 3
ExecutionTime = 1.37 s ClockTime = 1 s
Time = 3
smoothSolver: Solving for Ux, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uy, Initial residual = 0, Final residual = 0, No Iterations 0
smoothSolver: Solving for Uz, Initial residual = 0, Final residual = 0, No Iterations 0
GAMG: Solving for p, Initial residual = 0, Final residual = 0, No Iterations 0
time step continuity errors : sum local = 0, global = 0, cumulative = 0
smoothSolver: Solving for epsilon, Initial residual = 0.0972013129464, Final residual = 0.00472751378512, No Iterations 3
smoothSolver: Solving for k, Initial residual = 0.394880724125, Final residual = 0.0221518636059, No Iterations 4
ExecutionTime = 1.59 s ClockTime = 1 s
...
**This case is also tested in OpenFOAM-v1712 and it looks no problem. The log is shown below.**
===========================================================================
Starting time loop
Time = 1
smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 0.0477489367561, No Iterations 1
smoothSolver: Solving for Uy, Initial residual = 1, Final residual = 0.0538730764114, No Iterations 2
smoothSolver: Solving for Uz, Initial residual = 1, Final residual = 0.0669858308617, No Iterations 2
GAMG: Solving for p, Initial residual = 1, Final residual = 0.0621855191776, No Iterations 3
time step continuity errors : sum local = 0.000974118673505, global = 1.89337013488e-05, cumulative = 1.89337013488e-05
smoothSolver: Solving for epsilon, Initial residual = 0.0608576422262, Final residual = 0.00235143170564, No Iterations 3
smoothSolver: Solving for k, Initial residual = 1, Final residual = 0.0517062220961, No Iterations 2
ExecutionTime = 1.12 s ClockTime = 1 s
Time = 2
smoothSolver: Solving for Ux, Initial residual = 0.255464680163, Final residual = 0.0195594486154, No Iterations 2
smoothSolver: Solving for Uy, Initial residual = 0.308510924562, Final residual = 0.0110977491911, No Iterations 3
smoothSolver: Solving for Uz, Initial residual = 0.284472419959, Final residual = 0.0280404303152, No Iterations 2
GAMG: Solving for p, Initial residual = 0.13322215283, Final residual = 0.0101976026944, No Iterations 3
time step continuity errors : sum local = 0.000902796719122, global = -3.47014708889e-05, cumulative = -1.57677695401e-05
smoothSolver: Solving for epsilon, Initial residual = 0.0346080936392, Final residual = 0.00267021263905, No Iterations 2
smoothSolver: Solving for k, Initial residual = 0.270329057688, Final residual = 0.0168602729862, No Iterations 2
ExecutionTime = 1.38 s ClockTime = 2 s
Time = 3
smoothSolver: Solving for Ux, Initial residual = 0.403798686956, Final residual = 0.0335683918725, No Iterations 2
smoothSolver: Solving for Uy, Initial residual = 0.32172625807, Final residual = 0.0306454045428, No Iterations 2
smoothSolver: Solving for Uz, Initial residual = 0.347723798359, Final residual = 0.0245220605412, No Iterations 2
GAMG: Solving for p, Initial residual = 0.0412987455385, Final residual = 0.00277826618771, No Iterations 2
time step continuity errors : sum local = 0.000703580205099, global = 0.000107184465015, cumulative = 9.14166954752e-05
smoothSolver: Solving for epsilon, Initial residual = 0.0277288699551, Final residual = 0.00233613182817, No Iterations 2
smoothSolver: Solving for k, Initial residual = 0.262482535305, Final residual = 0.021940268746, No Iterations 2
ExecutionTime = 1.62 s ClockTime = 2 s
Time = 4
smoothSolver: Solving for Ux, Initial residual = 0.179980986317, Final residual = 0.0153420244482, No Iterations 2
smoothSolver: Solving for Uy, Initial residual = 0.176634654264, Final residual = 0.0065788228814, No Iterations 3
smoothSolver: Solving for Uz, Initial residual = 0.191853265263, Final residual = 0.01904668678, No Iterations 2
GAMG: Solving for p, Initial residual = 0.0729952671173, Final residual = 0.00340694854856, No Iterations 3
time step continuity errors : sum local = 0.000569941231663, global = 7.07002016898e-05, cumulative = 0.000162116897165
smoothSolver: Solving for epsilon, Initial residual = 0.0271072262376, Final residual = 0.00108121164345, No Iterations 3
smoothSolver: Solving for k, Initial residual = 0.212894843102, Final residual = 0.00862376163002, No Iterations 3
ExecutionTime = 1.9 s ClockTime = 2 s
\## Reattaching the author to the issue ticket: @chuck ##Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/191patch or wall (case windshieldCondensation)?2019-09-20T13:24:55ZAdminpatch or wall (case windshieldCondensation)?In case $FOAM_TUTORIALS/heatTransfer/chtMultiRegionFoam/windshieldCondensation,
ParaView warns me that 'Wrong list type for uniform field' at every rendering.
I think this warning is caused because 'exterior' is not wall but patch ...In case $FOAM_TUTORIALS/heatTransfer/chtMultiRegionFoam/windshieldCondensation,
ParaView warns me that 'Wrong list type for uniform field' at every rendering.
I think this warning is caused because 'exterior' is not wall but patch after splitMeshRegions.
Is this correct?
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/401Limitation: sampling FO not working with ACMI2018-05-29T05:39:49ZPrashant SonakarLimitation: sampling FO not working with ACMIAttached case replicating the behavior [oscillatingInletACMI2D.tgz](/uploads/f53bda75257196fd3688e1b7d863e71c/oscillatingInletACMI2D.tgz)
@Mattijs @mark
(Ref EP#333)Attached case replicating the behavior [oscillatingInletACMI2D.tgz](/uploads/f53bda75257196fd3688e1b7d863e71c/oscillatingInletACMI2D.tgz)
@Mattijs @mark
(Ref EP#333)AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/601Description correction to spatialTransformI.H2019-01-09T21:20:59ZMatej FormanDescription correction to spatialTransformI.HIn spatialTransformI.H
line 260 needs to change from:
`//- Rotational spatial transformation tensor about the x-axis by omega radians`
to
`//- Rotational spatial transformation tensor about the y-axis by omega radians`In spatialTransformI.H
line 260 needs to change from:
`//- Rotational spatial transformation tensor about the x-axis by omega radians`
to
`//- Rotational spatial transformation tensor about the y-axis by omega radians`Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1085Cannot prevent use of user config.sh directories2019-06-28T09:47:28ZMark OLESENCannot prevent use of user config.sh directoriesThis can hit when building for spack, debian, rpms as a normal user.
Using `foamEtcFile` to locate elements such as `config.sh/mpi` mean that any existing entries under `~/.OpenFOAM` will be seen and possibly influence the build.
Anothe...This can hit when building for spack, debian, rpms as a normal user.
Using `foamEtcFile` to locate elements such as `config.sh/mpi` mean that any existing entries under `~/.OpenFOAM` will be seen and possibly influence the build.
Another potential problem could arise on cluster installations. The administrator may wish to lock down the OpenFOAM configuration values to avoid issues.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/998removeFaces removes too many points2020-01-08T14:42:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comremoveFaces removes too many pointsSeems to be if from 2x2 block of cells only 3 are selected. It also removes the points still used by the fourth cell.Seems to be if from 2x2 block of cells only 3 are selected. It also removes the points still used by the fourth cell.https://develop.openfoam.com/Development/openfoam/-/issues/187wrmo error: could not find Make directory2016-07-18T05:21:42ZAdminwrmo error: could not find Make directorySorry for taking your precious time.
I tried to install plus on LinuxMint17.1. Probably the compilation of ParaView was successed but that of the OF-plus
stopped building in src/Allwmake with an error. I can not find the dire...Sorry for taking your precious time.
I tried to install plus on LinuxMint17.1. Probably the compilation of ParaView was successed but that of the OF-plus
stopped building in src/Allwmake with an error. I can not find the directory that is written in my log file.[log.make-0.tar.gz](/uploads/6f2fc89601111d451e5a935a3bd9537a/log.make-0.tar.gz)
What should I do next?
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, bashhttps://develop.openfoam.com/Development/openfoam/-/issues/58Typos in community page2016-01-18T09:00:55ZAdminTypos in community pagePage: http://www.openfoam.com/services/community-projects.php
* `faomyHexMesh` should be `foamyHexMesh`.
* `envorinment` should be `environment`.Page: http://www.openfoam.com/services/community-projects.php
* `faomyHexMesh` should be `foamyHexMesh`.
* `envorinment` should be `environment`.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/718snappyHexMesh labelledTri error2018-01-31T09:02:27ZvilfayeausnappyHexMesh labelledTri errorHi,
In 1712, wehn running snappyHexMesh, I have a fatal error due to wrong labelledTri size. See attached log file.
In 2.3.1, the same case is working fine.
Best,
Sebastien
[snappyHexMeshDict](/uploads/172f59c6374c7e1c07d86acb9782a13...Hi,
In 1712, wehn running snappyHexMesh, I have a fatal error due to wrong labelledTri size. See attached log file.
In 2.3.1, the same case is working fine.
Best,
Sebastien
[snappyHexMeshDict](/uploads/172f59c6374c7e1c07d86acb9782a138/snappyHexMeshDict)
1712 log file:
[snappyHexMesh_4401168.log](/uploads/746be00dac64cc8770b0a90b9d628a60/snappyHexMesh_4401168.log)
2.3.1 log file:
[snappyHexMesh.4275735.log](/uploads/750bbf0c579eac1f8f8375cde0da41a7/snappyHexMesh.4275735.log)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/475Where are the mass transfer source terms in phase fraction equation in reacti...2019-01-08T14:44:40ZAdminWhere are the mass transfer source terms in phase fraction equation in reactingEulerFoam solver?In reactingEulerFoam from OF3.0.1, there are mass transfer between different phases. The phase fraction is estentially the continuity equations, and so there must be some source terms accounting for mass change of individual phases. In f...In reactingEulerFoam from OF3.0.1, there are mass transfer between different phases. The phase fraction is estentially the continuity equations, and so there must be some source terms accounting for mass change of individual phases. In fluid.solve(), actually I did not see these terms appearring in the RHS of the phase fraction equations. Is this a bug? or I dismiss something in the code?
BTW, the fluid.solve(); is from:
> twoPhaseSystem/twoPhaseSystem.C
Thank you.https://develop.openfoam.com/Development/openfoam/-/issues/106error after Linux installation: installOpenFOAM+ script2016-04-28T16:06:22ZAdminerror after Linux installation: installOpenFOAM+ scriptAfter installation of OpenFOAM3+ binary on Linux, the following error message appears with the execution of startOpenFOAM+ script.
docker : Error response from daemon : linux spec user Unable to find user *userName*
OS: ubuntu 16.04 ...After installation of OpenFOAM3+ binary on Linux, the following error message appears with the execution of startOpenFOAM+ script.
docker : Error response from daemon : linux spec user Unable to find user *userName*
OS: ubuntu 16.04 / Docker: version 1.11.1
Modification of InstallOpenFOAM+ script resolve this problem.
Before: user="$USER"
After: user="$(id -u)"
reference: https://github.com/docker/docker/issues/22323
my friend reported that downgrade from docker 1.11.0 to 1.10.3 resolve the above problem.
Pawan GhildiyalPawan Ghildiyal