Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-09-06T09:16:17Zhttps://develop.openfoam.com/Development/openfoam/-/issues/997dynamicMultiMotionSolverFvMesh discussion2018-09-06T09:16:17ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdynamicMultiMotionSolverFvMesh discussion1. only provision is for motion on cellZone, not on cellSet
2. cellZone specification might easily be inconsistent with sub-motion solver (e.g. solidBodyMotionSolver) which looks for a cellZone or cellSet specification itself. (as long a...1. only provision is for motion on cellZone, not on cellSet
2. cellZone specification might easily be inconsistent with sub-motion solver (e.g. solidBodyMotionSolver) which looks for a cellZone or cellSet specification itself. (as long as this selection includes the multimotion cell selection it is ok)
3. output of solidBodyMotion might be confusing: e.g. `applying solid body motion to entire mesh` which then gets truncated by the dynamicMultiMotionSolverhttps://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/649movingWallVelocity allows non-zero input in case of static mesh2020-01-03T12:00:36ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commovingWallVelocity allows non-zero input in case of static meshIn case of non-moving the only value that makes sense is (0 0 0). Can we enforce this as per noSlip? Or do we re-interpret the value as a relative, additional motion in which case the moving() functionality should account for that.In case of non-moving the only value that makes sense is (0 0 0). Can we enforce this as per noSlip? Or do we re-interpret the value as a relative, additional motion in which case the moving() functionality should account for that.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/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/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/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.comhttps://develop.openfoam.com/Development/openfoam/-/issues/881dictionary deprecation mechanism quite verbose2018-06-21T09:20:13ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdictionary deprecation mechanism quite verboseI am getting (e.g. smallPoolFire2D tutorial)
```
keyword is deemed to be 5 months old
```
on all processors. One should be enough.I am getting (e.g. smallPoolFire2D tutorial)
```
keyword is deemed to be 5 months old
```
on all processors. One should be enough.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/449"timeVaryingMappedFixedValue" cannot read files when I use mpirun2019-12-09T21:29:29ZAdmin"timeVaryingMappedFixedValue" cannot read files when I use mpirunHi,
The boundary condition "timeVaryingMappedFixedValue" refuses to read inlet files in boundaryData/inlet at each time steps when I use mpirun.
**1. I post what I saw from the screen: **
```
Starting time loop
streamLine stream...Hi,
The boundary condition "timeVaryingMappedFixedValue" refuses to read inlet files in boundaryData/inlet at each time steps when I use mpirun.
**1. I post what I saw from the screen: **
```
Starting time loop
streamLine streamLines:
Employing velocity field U
automatic track length specified through number of sub cycles : 5
Time = 1
timeVaryingFixedValueFvPatchField : Read 70 sample points from "/home/ofuser/wor
kingDir/run/pitzDailyExptInlet/processor0/../constant/boundaryData/inlet/points"
timeVaryingFixedValueFvPatchField : In directory "/home/ofuser/workingDir/run/pi
tzDailyExptInlet/processor0/../constant/boundaryData/inlet" found times
4
(
0
0.7
2
4
)
[0] checkTable : Reading startValues from "boundaryData/inlet/0.7"
[3] checkTable : Reading startValues from "boundaryData/inlet/0.7"
[2] checkTable : Reading startValues from "boundaryData/inlet/0.7"
[1] checkTable : Reading startValues from "boundaryData/inlet/0.7"
[3] checkTable : Reading endValues from "boundaryData/inlet/2"
[0] checkTable : Reading endValues from "boundaryData/inlet/2"
[2] checkTable : Reading endValues from "boundaryData/inlet/2"
[0]
[0]
[0] --> FOAM FATAL IO ERROR:
[0] file "../constant/boundaryData/inlet/2/U" does not exist
[0]
[0] file: ../constant/boundaryData/inlet/2/U at line 1.
[0]
[0] From function Foam::IFstream& Foam::IFstream::operator()() const
[0] in file db/IOstreams/Fstreams/IFstream.C at line 176.
[0]
FOAM parallel run exiting
[0]
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
[1] checkTable : Reading endValues from "boundaryData/inlet/2"
[3]
[3]
[3] --> FOAM FATAL IO ERROR:
[3] file "../constant/boundaryData/inlet/2/U" does not exist
[3]
[3] file: ../constant/boundaryData/inlet/2/U at line 1.
[3]
[3] From function Foam::IFstream& Foam::IFstream::operator()() const
[3] in file db/IOstreams/Fstreams/IFstream.C at line 176.
[3]
FOAM parallel run exiting
[3]
[2]
[2]
[2] --> FOAM FATAL IO ERROR:
[2] file "../constant/boundaryData/inlet/2/U" does not exist
[2]
[2] file: ../constant/boundaryData/inlet/2/U at line 1.
[2]
[2] From function Foam::IFstream& Foam::IFstream::operator()() const
[2] in file db/IOstreams/Fstreams/IFstream.C at line 176.
[2]
FOAM parallel run exiting
[2]
[1]
[1]
[1] --> FOAM FATAL IO ERROR:
[1] file "../constant/boundaryData/inlet/2/U" does not exist
[1]
[1] file: ../constant/boundaryData/inlet/2/U at line 1.
[1] [default:26184] 1 more process has sent help message help-mpi-api.txt / mpi-
abort
[default:26184] Set MCA parameter "orte_base_help_aggregate" to 0 to see all hel
p / error messages[pitzDailyExptInlet.7z](/uploads/eb58a7f8a25df1966091c72985e38262/pitzDailyExptInlet.7z)
```
[pitzDailyExptInlet.7z](/uploads/9df573a34ff06fbb460b03bd7e9f71b4/pitzDailyExptInlet.7z)
**2. To reproduce the error, the steps are: **
*step 1*: clone pitzDailyExptInlet;
*step 2*: creat new files of others time steps by copying constant/boundaryData/inlet/0. So I have new directories and files like:
constant/boundaryData/inlet/0.7/U
constant/boundaryData/inlet/0.7/k
constant/boundaryData/inlet/0.7/epsilon
constant/boundaryData/inlet/2/U
constant/boundaryData/inlet/2/k
constant/boundaryData/inlet/2/epsilon
constant/boundaryData/inlet/4/U
constant/boundaryData/inlet/4/k
constant/boundaryData/inlet/4/epsilon
*step 3*: I run "blockMesh" "decomposePar" then "mpirun -np 4 simpleFoam -parallel"
**3. The version OpenFoam 3.0.x is used and the case is run in windows system (windows server 2012). **
* No errors are producted during "blockMesh", "decomposePar" in mpirun
* No errors are producted in sequential calculation.
* I have attached my test case.
Best Regards,AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/580contiguous flag2018-07-02T09:38:59ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcontiguous flagIn lagrangian there are various occurrences of making a specialisation of contiguous(), returning false:
coalCombustion/coalParcel/coalParcel.H
intermediate/parcels/derived/basicReactingMultiphaseParcel/basicReactingMultiphaseParcel.H
i...In lagrangian there are various occurrences of making a specialisation of contiguous(), returning false:
coalCombustion/coalParcel/coalParcel.H
intermediate/parcels/derived/basicReactingMultiphaseParcel/basicReactingMultiphaseParcel.H
intermediate/parcels/derived/basicReactingParcel/basicReactingParcel.H
spray/parcels/derived/basicSprayParcel/basicSprayParcel.H
The default template function returns false so they're not needed.AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/552managing fatal exceptions is awkward2017-07-29T11:22:50ZMark OLESENmanaging fatal exceptions is awkwardMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1237add support for writing finiteArea fields2019-04-26T08:09:45ZMark OLESENadd support for writing finiteArea fields- currently no easy mean of writing into other formats (ensight, vtk, etc).
- implement as a function object, reusing the newly revised surface writers
cross-ref: EP945- currently no easy mean of writing into other formats (ensight, vtk, etc).
- implement as a function object, reusing the newly revised surface writers
cross-ref: EP945Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1117foamToVTK cannot write faceZones only2018-12-12T15:29:45ZMark OLESENfoamToVTK cannot write faceZones onlyAs noted by @Prashant - used to be able to hack foamToVTK with -noInternal and -excludePatches to get faceZones only, but now these are linked to the internal mesh (so that -no-internal really doesn't generate internal data fields).
Agr...As noted by @Prashant - used to be able to hack foamToVTK with -noInternal and -excludePatches to get faceZones only, but now these are linked to the internal mesh (so that -no-internal really doesn't generate internal data fields).
Agreed that it probably makes more sense to explicitly request faceZones by name or regex as per foamToEnsight. This makes it more flexible and more consistent with foamToEnsight.Mark OLESENMark OLESEN