Development issueshttps://develop.openfoam.com/groups/Development/-/issues2020-06-18T22:05:35Zhttps://develop.openfoam.com/Development/openfoam/-/issues/920checkMesh reports negative internal points2020-06-18T22:05:35ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh reports negative internal points- take multiRegionHeater tutorial
- comment out regions in decomposeParDict, i.e. use scotch for decomposition
```mpirun -np 4 checkMesh -region heater -parallel```
produces
```
internal points: -2
--> FOAM Warning :
From fu...- take multiRegionHeater tutorial
- comment out regions in decomposeParDict, i.e. use scotch for decomposition
```mpirun -np 4 checkMesh -region heater -parallel```
produces
```
internal points: -2
--> FOAM Warning :
From function void Foam::printMeshStats(const Foam::polyMesh&, bool)
in file checkTools.C at line 66
```https://develop.openfoam.com/Development/openfoam/-/issues/489sphereDrop testcase; -postProcess option for time list2018-07-03T10:43:48ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsphereDrop testcase; -postProcess option for time listRunning:
1) compressibleInterDyMFoam -postProcess -time 0.003
This works
2) compressibleInterDyMFoam -postProcess
This crashes at time 0.0003
Something does not get updated in looping over the time ('Reading thermophysical propertie...Running:
1) compressibleInterDyMFoam -postProcess -time 0.003
This works
2) compressibleInterDyMFoam -postProcess
This crashes at time 0.0003
Something does not get updated in looping over the time ('Reading thermophysical properties')? Attached both files.[log.compressibleInterDyMFoam_postProcess2](/uploads/89cc9fdfa1bb219aba2764f7471ca788/log.compressibleInterDyMFoam_postProcess2)[log.compressibleInterDyMFoam_postProcess1](/uploads/1f13654600e4b3fab85c6eb268ff5e59/log.compressibleInterDyMFoam_postProcess1)https://develop.openfoam.com/Development/openfoam/-/issues/500sampling the surface ('triSurfaceMesh') normal component not supported2017-06-29T20:38:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampling the surface ('triSurfaceMesh') normal component not supportedThere is the fieldValues with areaNormalAverage but that uses the regionType's (faceZone, patch) normal.There is the fieldValues with areaNormalAverage but that uses the regionType's (faceZone, patch) normal.Version v1706Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/612CodedSource<Type>::description() contains space2020-01-03T11:13:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comCodedSource<Type>::description() contains spaceMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1228old time field being read in postprocessing2020-01-08T14:36:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comold time field being read in postprocessing<!--
*** 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
-->
<!--
All text between these marker...<!--
*** 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
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
During post processing it reads the contents of the directory e.g. as volFields. There is no need to automatically read the old-time field as well. This is just an efficiency issue.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Use e.g. setFields. Copy a field to make an old-time one: ```cp zoneID zoneID_0```
Switch on debug flag for ```volScalarField``` and run ```setFields``` with relevant ```setFieldsDict```. It shows loading the old-time field.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/122Bug: noise-plus utility2023-12-07T19:01:57ZPrashant SonakarBug: noise-plus utilityThe noise utility exports or reads in data files to ensight format.
The data could be read in paraview but not in EnSight be cause ensight reader can't support special characters
e.g. reader would skip % sign when reading motorBike...The noise utility exports or reads in data files to ensight format.
The data could be read in paraview but not in EnSight be cause ensight reader can't support special characters
e.g. reader would skip % sign when reading motorBike case
patch_motorBike_rider-helmet`%`65.0000.mesh is interpreted as
patch_motorBike_rider-helmet`0`65.0000.mesh
Please update the writer to skip special characters in family name!
Probably this needs to be checked for ensight export in general (?)
@Mattijs Mark OLESENMark OLESENhttps://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/1134sampledSets that sampled mesh points/faces/cells (e.g. reads pointSet, faceSe...2018-12-19T11:46:45ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampledSets that sampled mesh points/faces/cells (e.g. reads pointSet, faceSet, cellSet)Would be quite nice to sample selected mesh elements. We've got cellCentreSet but that samples all cells. There are probes but they only sample a single location.Would be quite nice to sample selected mesh elements. We've got cellCentreSet but that samples all cells. There are probes but they only sample a single location.https://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/1133cyclic pathes converted into processorCyclic not handled in patch name lookups2018-12-20T14:33:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcyclic pathes converted into processorCyclic not handled in patch name lookupsdecomposePar can split a cyclic into processorCyclics. These then will not be picked up by user patch-selection (e.g. through `polyBoundaryMesh::patchSet`).
Add functionality to e.g. patchSet to support this transparently.decomposePar can split a cyclic into processorCyclics. These then will not be picked up by user patch-selection (e.g. through `polyBoundaryMesh::patchSet`).
Add functionality to e.g. patchSet to support this transparently.https://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/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/files