Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-09-17T09:49:32Zhttps://develop.openfoam.com/Development/openfoam/-/issues/765fvMotionSolvers not using fvOptions2018-09-17T09:49:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfvMotionSolvers not using fvOptionsThis is quite useful to have internal (cell based) constraints, e.g.
[fvOptions](/uploads/4f90b3668aa719e42dae501ad51f9511/fvOptions)This is quite useful to have internal (cell based) constraints, e.g.
[fvOptions](/uploads/4f90b3668aa719e42dae501ad51f9511/fvOptions)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/343foamList does not link if no conformalVoronoiMesh, randomProcesses (depend on...2018-05-29T05:39:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamList does not link if no conformalVoronoiMesh, randomProcesses (depend on optional 3rd party libs)https://develop.openfoam.com/Development/openfoam/-/issues/543scotch include file is /usr/include/scotch/scotch.h which does not work in sr...2019-12-09T22:11:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch include file is /usr/include/scotch/scotch.h which does not work in src/parallel/decompose/AllwmakeTest is for $SCOTCH_ARCH_PATH/include/scotch.h or /usr/include/scotch.h
This is on Ubuntu 12.10.Test is for $SCOTCH_ARCH_PATH/include/scotch.h or /usr/include/scotch.h
This is on Ubuntu 12.10.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/331scaleFactor for fieldValue function-objects is 'sticky'2018-05-29T05:39:48ZMark OLESENscaleFactor for fieldValue function-objects is 'sticky'After removing a `scaleFactor` keyword from the dictionary, the previous scaling is retained. It is not reset to the default of 1.After removing a `scaleFactor` keyword from the dictionary, the previous scaling is retained. It is not reset to the default of 1.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/79OpenFOAM is not running on Windows 72016-03-15T03:53:17ZAdminOpenFOAM is not running on Windows 7Hello,
I installed OpenFOAM v3.0+ on Windows7 and I followed the installation procedure. However I cannot enter the OpenFOAM environment.
When I click on "OpenFOAM_Start" shortcut in Desktop to start OpenFOAM environment, an error ...Hello,
I installed OpenFOAM v3.0+ on Windows7 and I followed the installation procedure. However I cannot enter the OpenFOAM environment.
When I click on "OpenFOAM_Start" shortcut in Desktop to start OpenFOAM environment, an error occurs and no container is started.
I attached an image which can be useful.
Does anyone have a clue?
![pic1](/uploads/3eb796a3f25112077907537e21d5e35f/pic1.png)Pawan GhildiyalPawan Ghildiyalhttps://develop.openfoam.com/Development/openfoam/-/issues/965cyclicACMIFvPatchField with non-overlap field constructed afterwards2018-11-09T05:25:16ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcyclicACMIFvPatchField with non-overlap field constructed afterwardsIn case with ACMI: change e.g. 0/U to have the non-overlap bc (usually a wall) after the ACMI bc. If there is no initial value it will trigger 'evaluate' which will try to access the non-overlap patch field value - which has not been ini...In case with ACMI: change e.g. 0/U to have the non-overlap bc (usually a wall) after the ACMI bc. If there is no initial value it will trigger 'evaluate' which will try to access the non-overlap patch field value - which has not been initialised yet.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/96turbulentHeatFluxTemperature cannot be used anymore with buoyantBoussinesqSim...2016-04-13T06:52:11ZAdminturbulentHeatFluxTemperature cannot be used anymore with buoyantBoussinesqSimpleFoamDescription :
In OpenFOAM 2.4.0 it was possible to use the boundary condition turbulentHeatFluxTemperature with an incompressible solver like buoyantBoussinesqSimpleFoam. But in OpenFOAM v3.0+ I face the error:
--> FOAM FATAL IO ERRO...Description :
In OpenFOAM 2.4.0 it was possible to use the boundary condition turbulentHeatFluxTemperature with an incompressible solver like buoyantBoussinesqSimpleFoam. But in OpenFOAM v3.0+ I face the error:
--> FOAM FATAL IO ERROR:
Unknown patchField type turbulentHeatFluxTemperature for patch type wall
Steps to reproduce:
Take the hotRoom tutorial:
tutorials/heatTransfer/buoyantBoussinesqSimpleFoam/hotRoom
Change the patch floor in the 0/T.org file to:
floor
{
type turbulentHeatFluxTemperature;
gradient uniform 0;
heatSource power;
q uniform 64;
alphaEff alphaEff;
value uniform 300;
}
Launch the Allrun
SIMPLE: convergence criteria
field p_rgh tolerance 0.01
field U tolerance 0.0001
field T tolerance 0.01
field "(k|epsilon|omega)" tolerance 0.001
Reading thermophysical properties
Reading field T
--> FOAM FATAL IO ERROR:
Unknown patchField type turbulentHeatFluxTemperature for patch type wall
Valid patchField types are :
104
(
advective
alphatJayatillekeWallFunction
atmBoundaryLayerInletEpsilon
atmBoundaryLayerInletK
calculated
codedFixedValue
codedMixed
compressible::alphatJayatillekeWallFunction
compressible::alphatWallFunction
compressible::thermalBaffle1D<hConstSolidThermoPhysics>
compressible::thermalBaffle1D<hPowerSolidThermoPhysics>
compressible::turbulentHeatFluxTemperature
Additional information :
If we repeat the same procedure in OF2.4.0 :
tutorials/heatTransfer/buoyantBoussinesqSimpleFoam/hotRoom
1) change the patch floor 0/T.org:
floor
{
type turbulentHeatFluxTemperature;
gradient uniform 0;
heatSource power;
q uniform 64;
alphaEff alphaEff;
value uniform 300;
}
2) add the line rhoCp0 1173; in transportProperties
3) launch the Allrun
SIMPLE: convergence criteria
field p_rgh tolerance 0.01
field U tolerance 0.0001
field T tolerance 0.01
field "(k|epsilon|omega)" tolerance 0.001
Starting time loop
Time = 1
DILUPBiCG: Solving for Ux, Initial residual = 0, Final residual = 0, No Iterations 0
DILUPBiCG: Solving for Uy, Initial residual = 0, Final residual = 0, No Iterations 0
DILUPBiCG: Solving for Uz, Initial residual = 0, Final residual = 0, No Iterations 0
DILUPBiCG: Solving for T, Initial residual = 1, Final residual = 0.0475703, No Iterations 1
DICPCG: Solving for p_rgh, Initial residual = 1, Final residual = 0.00653368, No Iterations 7
time step continuity errors : sum local = 5.65209e-09, global = -4.97342e-25, cumulative = -4.97342e-25
DILUPBiCG: Solving for epsilon, Initial residual = 0.0458815, Final residual = 0.00188758, No Iterations 1
DILUPBiCG: Solving for k, Initial residual = 1, Final residual = 0.0721881, No Iterations 1
ExecutionTime = 0.05 s ClockTime = 0 s
Time = 2
DILUPBiCG: Solving for Ux, Initial residual = 0.651198, Final residual = 0.00701648, No Iterations 1
DILUPBiCG: Solving for Uy, Initial residual = 0.558322, Final residual = 0.00593882, No Iterations 1
DILUPBiCG: Solving for Uz, Initial residual = 0.651198, Final residual = 0.00701648, No Iterations 1
DILUPBiCG: Solving for T, Initial residual = 0.431799, Final residual = 0.0275141, No Iterations 1
DICPCG: Solving for p_rgh, Initial residual = 0.86867, Final residual = 0.00688476, No Iterations 27
time step continuity errors : sum local = 3.05697e-07, global = -6.73656e-24, cumulative = -7.2339e-24
DILUPBiCG: Solving for epsilon, Initial residual = 0.115159, Final residual = 0.00602713, No Iterations 1
DILUPBiCG: Solving for k, Initial residual = 0.624686, Final residual = 0.0490608, No Iterations 1
ExecutionTime = 0.06 s ClockTime = 0 s
OK no error.
why in OF240 the turbulentHeatFluxTemperature is present in incompressible
https://github.com/OpenFOAM/OpenFOAM-2.4.x/blob/2b147f41daf9ca07d0fb4c6b0576dc3d10a435f3/src/turbulenceModels/incompressible/turbulenceModel/derivedFvPatchFields/turbulentHeatFluxTemperature/turbulentHeatFluxTemperatureFvPatchScalarField.H
but not in OFv3.0+?
https://develop.openfoam.com/search?utf8=%E2%9C%93&search=turbulentHeatFluxTemperature&group_id=&project_id=5&search_code=true&repository_ref=master
Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/1130update comment in tabulatedAccelerationSource2020-03-13T13:39:50ZAdminupdate comment in tabulatedAccelerationSourceInformation about the file structure were missing in the comments and the documentation seems outdated:
https://www.openfoam.com/documentation/cpp-guide/html/guide-fvoptions-sources-tabulated-acceleration.html
```
Usage
Example usa...Information about the file structure were missing in the comments and the documentation seems outdated:
https://www.openfoam.com/documentation/cpp-guide/html/guide-fvoptions-sources-tabulated-acceleration.html
```
Usage
Example usage:
\verbatim
SBM
{
type tabulatedAccelerationSource;
active yes;
timeDataFileName "constant/acceleration-terms.dat";
}
cat constant/acceleration-terms.dat:
2
( t acc omega dOmegadt
(0.0 ((1 0 0) (0 0 0) (0 0 0)))
(10 ((2 0 0) (0 0 0) (0 0 0)))
)
t = time [s]
acc = acceleration vector [m/s2]
omega = rotation vector [rad/s]
dOmegadt = angular acceleration [rad/s2]
details see tabulatedAccelerationSourceTemplates.C
\endverbatim
```
\## Reattaching the author to the issue ticket: @Henning86 ##v2006Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/253ENH: provided a flexible string formatting2017-01-02T12:25:35ZMark OLESENENH: provided a flexible string formattingProvide the possibility of sprintf-style formatting for basic primitives (int, float) in the `Foam::name()` globals.
Example syntax,
word outname = name("%08d", intval);
instead of
std::ostringstream oss;
oss << std::setfi...Provide the possibility of sprintf-style formatting for basic primitives (int, float) in the `Foam::name()` globals.
Example syntax,
word outname = name("%08d", intval);
instead of
std::ostringstream oss;
oss << std::setfill('0') << std::setw(8) << intval;
word outname = oss.str();Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/89fvOption limitTemperature not recognised2016-04-05T05:22:11ZAdminfvOption limitTemperature not recognisedthe fvOption limitTemperature is not recognised as a valid fvOption. This is because it is omitted from the OpenFOAM-v3.0+/src/fvOptions/Make/files although the source is present in OpenFOAM-v3.0+/src/fvOptions/corrections/limitTemperatu...the fvOption limitTemperature is not recognised as a valid fvOption. This is because it is omitted from the OpenFOAM-v3.0+/src/fvOptions/Make/files although the source is present in OpenFOAM-v3.0+/src/fvOptions/corrections/limitTemperature.
howver the entry for limitTemperature is present in OpenFOAM-3.0.1/src/fvOptions/Make/fileshttps://develop.openfoam.com/Development/openfoam/-/issues/283Provide method to write boundary field entries as dictionary entries2017-01-02T12:24:26ZMark OLESENProvide method to write boundary field entries as dictionary entriesSimilar to what dictionary::writeEntries() offers - just the contents, without a surrounding 'boundaryField' block.Similar to what dictionary::writeEntries() offers - just the contents, without a surrounding 'boundaryField' block.Version v1612Mark OLESENMark OLESEN2016-10-31https://develop.openfoam.com/Development/openfoam/-/issues/1230optionally suppress cell, proc, patch ids for foamToVTK2019-03-22T08:02:06ZMark OLESENoptionally suppress cell, proc, patch ids for foamToVTKcross-reference EP718
@SonESIcross-reference EP718
@SonESIMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/333provide log option to top-level build2018-05-29T05:39:49ZMark OLESENprovide log option to top-level buildCapture stdout/stderr for later diagnostics.Capture stdout/stderr for later diagnostics.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/469DTCHull fails on various number of domains in parallel2018-07-03T10:43:06ZMatej FormanDTCHull fails on various number of domains in parallel$FOAM_TUTORIALS/multiphase/interDyMFoam/ras/DTCHull run on centOS (vanilla 1612+ compiled with all default options).
runs fine on 16 and 32 CPUs
fails on 4 and 8 CPUs.
case on 4CPUs on k growing out of bounds:
[log_interDyMFoam_4](/u...$FOAM_TUTORIALS/multiphase/interDyMFoam/ras/DTCHull run on centOS (vanilla 1612+ compiled with all default options).
runs fine on 16 and 32 CPUs
fails on 4 and 8 CPUs.
case on 4CPUs on k growing out of bounds:
[log_interDyMFoam_4](/uploads/f6e2af364a76f0f11ab862f95e658e77/log_interDyMFoam_4)
case on 8 CPUs suddenly with SigSev on pressure equation.
[log_interDyMFoam_8](/uploads/49d6b19325216b4a30686d11081d8952/log_interDyMFoam_8)
See logs attached.Prashant SonakarPrashant Sonakarhttps://develop.openfoam.com/Development/openfoam/-/issues/119BUG: inconsistent configuation files in develop branch2016-11-24T07:34:55ZPrashant SonakarBUG: inconsistent configuation files in develop branchSome setup configuration files are missing in etc/config.csh
e.g. scotch
@Mattijs Some setup configuration files are missing in etc/config.csh
e.g. scotch
@Mattijs AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1034searchableSurfacesQueries does not handle multiple separate surfaces2021-07-06T13:28:14ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsearchableSurfacesQueries does not handle multiple separate surfacesMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/759snappyHexMesh : layer extrusion in parallel2018-07-02T16:14:00ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh : layer extrusion in parallelshm avoids trying to extrude if:
1) locally two patch faces only connect via a point
`
+--+
| |
+--+--+
| |
+--+
`
It does this even though neighbouring processors might have the missing patch faces.
2) if a mesh point is not on...shm avoids trying to extrude if:
1) locally two patch faces only connect via a point
`
+--+
| |
+--+--+
| |
+--+
`
It does this even though neighbouring processors might have the missing patch faces.
2) if a mesh point is not on the patch on some processors. This state 'wins'.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/933mpirun on less than decomposed number of processors does not give error message2020-01-03T14:21:29ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commpirun on less than decomposed number of processors does not give error messageE.g. decompose into 8 with a non-standard decomposeParDict but run checkMesh on 6 (as set by system/decomposeParDict). This bypasses the argList check on incorrect number of processors so now gives sigsegv from processorPolyPatch trying ...E.g. decompose into 8 with a non-standard decomposeParDict but run checkMesh on 6 (as set by system/decomposeParDict). This bypasses the argList check on incorrect number of processors so now gives sigsegv from processorPolyPatch trying to send to non-existing neighbouring processors.https://develop.openfoam.com/Development/openfoam/-/issues/260implicit plane constructors cause weirdness2016-12-23T12:39:40ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comimplicit plane constructors cause weirdnessin shm was using
p.boundaryField()[patchi] == scalarField(..)
which causes implicit plane-construct-from-scalarList to be invoked.in shm was using
p.boundaryField()[patchi] == scalarField(..)
which causes implicit plane-construct-from-scalarList to be invoked.https://develop.openfoam.com/Development/openfoam/-/issues/808checkMesh crash on zero volume cell2018-07-02T16:12:22ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh crash on zero volume cellMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com