Development issueshttps://develop.openfoam.com/groups/Development/-/issues2021-07-06T11:23:02Zhttps://develop.openfoam.com/Development/openfoam/-/issues/631framework for cell cutting (placeholder)2021-07-06T11:23:02ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comframework for cell cutting (placeholder)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/632wrong entry in new tutorial vortexShed2017-11-07T10:52:27ZMatej Formanwrong entry in new tutorial vortexShedIn tutorial $FOAM_TUTORIALS/incompressible/pimpleFoam/LES/vortexShed
the noise utility dictionary for surface has wrong specification of the cutting plane.
file: system/noise-surface
it reads:
`file "postProcessing/cuttingPla...In tutorial $FOAM_TUTORIALS/incompressible/pimpleFoam/LES/vortexShed
the noise utility dictionary for surface has wrong specification of the cutting plane.
file: system/noise-surface
it reads:
`file "postProcessing/cuttingPlane/yNormal_0.0/yNormal_0.0.case";`
but should:
`file "postProcessing/cuttingPlane/zNormal/zNormal.case";`
to point to correct cutting plane.
would be nice to create Allrun.noise
to show how to get the noise data actuallyhttps://develop.openfoam.com/Development/openfoam/-/issues/633overset solver crash with layerRelax different to one2021-07-06T11:23:56ZAdminoverset solver crash with layerRelax different to oneI am playing around with the overset solvers, and I found that they crash when I use a value of layerRelax = 0.3 (actually any value less than one will make the solver crash). This value is not accessible via the dynamicMeshDict, so I d...I am playing around with the overset solvers, and I found that they crash when I use a value of layerRelax = 0.3 (actually any value less than one will make the solver crash). This value is not accessible via the dynamicMeshDict, so I directly changed the value in the source code.
I am also wondering if it is possible to change the cutting hole (which I think you call block cells). So far the minimum cutting hole is computed, but I would like to use the maximum cutting hole (or something larger than the minimum cutting hole as this one is too close to the walls).
I am attaching the reference case that I am using for validation.
[ref.tar.gz](/uploads/08f1d31c4fd7b52d8bb6c83ea2a64aff/ref.tar.gz)
\## Reattaching the author to the issue ticket: @jeogi ##https://develop.openfoam.com/Development/openfoam/-/issues/634ENH: Message running transient solver with steadyState ddtSchemes2019-12-09T22:11:26ZRoger AlmenarENH: Message running transient solver with steadyState ddtSchemesIf one tries to run a transient solver (pimpleFoam, rhoPimpleFoam) with a system/fvSchemes which contains a "steadyState" under ddtSchemes, the error message is too criptic to understand that the problem comes from the ddtSchemes keyword...If one tries to run a transient solver (pimpleFoam, rhoPimpleFoam) with a system/fvSchemes which contains a "steadyState" under ddtSchemes, the error message is too criptic to understand that the problem comes from the ddtSchemes keyword:
*PIMPLE: iteration 1
smoothSolver: Solving for Ux, Initial residual = 1, Final residual = 0.91075358, No Iterations 200
smoothSolver: Solving for Uy, Initial residual = 0.99948898, Final residual = 0.34301737, No Iterations 200
smoothSolver: Solving for Uz, Initial residual = 0.99948898, Final residual = 0.3430056, No Iterations 200
smoothSolver: Solving for e, Initial residual = 1, Final residual = 0.89821527, No Iterations 200
--> FOAM FATAL ERROR:
Operator + is undefined for oriented and unoriented types
From function Foam::orientedType Foam::operator+(const Foam::orientedType&, const Foam::orientedType&)
in file orientedType/orientedType.C at line 461.
FOAM aborting*
Changing the ddtScheme to Euler or to backward will get rid of the error message. It would help if a more meaningful message was set.https://develop.openfoam.com/Development/openfoam/-/issues/635Cleanup of git repo2020-03-13T14:25:47ZAdminCleanup of git repoHi,
Is it possible to do some cleanup of the repo. I noticed the "twoPhasePachuka" tutorial case has historical artefacts that are mainly responsible for this. I reduced the repo size from 1.1G to 300M by issuing the following commands (...Hi,
Is it possible to do some cleanup of the repo. I noticed the "twoPhasePachuka" tutorial case has historical artefacts that are mainly responsible for this. I reduced the repo size from 1.1G to 300M by issuing the following commands (and then re-added the tutorial case)
```
git filter-branch --tag-name-filter cat --index-filter 'git rm -rf --cached --ignore-unmatch tutorials/multiphase/MPPICInterFoam/twoPhasePachuka' --prune-empty -f -- --all
rm -rf .git/refs/original/
git reflog expire --expire=now --all
git gc --aggressive --prune=now
```
Regards
Andrew
\## Reattaching the author to the issue ticket: @Jackson ##https://develop.openfoam.com/Development/openfoam/-/issues/636Tutorial Test - 10.11.20172017-12-18T05:11:45ZPrashant SonakarTutorial Test - 10.11.2017Solver crash
- combustion/fireFoam/LES/flameSpreadWaterSuppressionPanel
- heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
- multiphase/driftFluxFoam/RAS/dahl
- multiphase/cavitatingFoam/LES/throttle
- multiphase/reacting...Solver crash
- combustion/fireFoam/LES/flameSpreadWaterSuppressionPanel
- heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
- multiphase/driftFluxFoam/RAS/dahl
- multiphase/cavitatingFoam/LES/throttle
- multiphase/reactingTwoPhaseEulerFoam/RAS/LBend
- incompressible/porousSimpleFoam/straightDuctImplicit (foamListTimes missing, failure in solver)
- mesh/foamyHexMesh/mixerVessel(foamListTimes missing, failure in createBaffles)
- multiphase/reactingTwoPhaseEulerFoam/laminar/steamInjection
- multiphase/interFoam/laminar/vofToLagrangian/eulerianInjection
Solver hangs
- tutorials/IO/fileHandler
General:
- Can we use runApplication for all instances of createGraph (as in heatTransfer/buoyantSimpleFoam/buoyantCavity/Allrun)?
All logs present at: /home/alex4/prashant/SUPPORT/ESI/MEDIUM_TEST/tutorials
@mark @Mattijsv1712https://develop.openfoam.com/Development/openfoam/-/issues/637ensight surface format missing space2017-11-21T07:09:14ZMark OLESENensight surface format missing spacewhen variables are too long - EP#547
@Prashantwhen variables are too long - EP#547
@Prashantv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/638foamListTimes disappeared; still used in tutorials2017-12-18T05:11:06ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamListTimes disappeared; still used in tutorialsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/639cleanup autoPtr, tmp, xfer2020-10-20T16:23:38ZMark OLESENcleanup autoPtr, tmp, xfer- Some constructors and methods can be constexpr, noexcept.
- most places have a const copy constructor that steals the contents. Could/should be revised to use a universal reference and prohibit const copy (as per std::unique_ptr).- Some constructors and methods can be constexpr, noexcept.
- most places have a const copy constructor that steals the contents. Could/should be revised to use a universal reference and prohibit const copy (as per std::unique_ptr).v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/640pRefValue not preserved in closed-domain simulation2017-11-16T05:08:53ZPrashant SonakarpRefValue not preserved in closed-domain simulationEP#474EP#474Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/641Unknow write type "boundaryData" in surfacesSampling format2018-05-31T09:58:47ZAdminUnknow write type "boundaryData" in surfacesSampling formatI used surfaceFormat boundaryData (A form that can be used with timeVaryingMapped boundary) in surfacesSampling to have point information.
I can still find it here :https://www.openfoam.com/documentation/user-guide/userse21.php.
In op...I used surfaceFormat boundaryData (A form that can be used with timeVaryingMapped boundary) in surfacesSampling to have point information.
I can still find it here :https://www.openfoam.com/documentation/user-guide/userse21.php.
In openFoam4.1 under Ubuntu system, "boundaryData" is a unknow type. I cannot figure it out.
Furthermore, "boundaryData" and "foamFile" don't give the same number points. The boundary conditon "timeVaryingMappedFixedValue" prefers the point file outputed from "boundaryData" which has less point number in the file than the one from "foamFile".
Best Regards,https://develop.openfoam.com/Development/openfoam/-/issues/642redistributePar with -decompose and ptscotch crashes2020-01-03T11:21:24ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar with -decompose and ptscotch crashesptscotch returns a one element decomposition on domains with zero cells.ptscotch returns a one element decomposition on domains with zero cells.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/643Feature: summary of parcels based on typeID2019-06-05T11:40:15ZPrashant SonakarFeature: summary of parcels based on typeIDRefer EP#525
@Sergio @andyRefer EP#525
@Sergio @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/644fieldMinMax reporting wrong location2017-12-18T05:07:55ZRoger AlmenarfieldMinMax reporting wrong locationUsing v1706.
I am monitoring min/max velocities in a thermal case using the fieldMinMax FO (rhoSimpleFoam). The report of the maximum velocity seems to be going OK, but I have an issue with the location: the cell number stays constant, w...Using v1706.
I am monitoring min/max velocities in a thermal case using the fieldMinMax FO (rhoSimpleFoam). The report of the maximum velocity seems to be going OK, but I have an issue with the location: the cell number stays constant, whilst the actual XYZ location changes along the iterations, as shown here:
*> max(mag(U)) = 20.252895 in cell 110637 at location (0.38 0.004410381 0.004410381) on processor 12
> max(mag(U)) = 20.257627 in cell 388740 at location (0.476 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.262458 in cell 388740 at location (0.47866667 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.267294 in cell 388740 at location (0.484 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.272106 in cell 388740 at location (0.48933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.276871 in cell 388740 at location (0.49466667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.281582 in cell 388740 at location (0.5 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.286253 in cell 388740 at location (0.50533333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.290906 in cell 388740 at location (0.51333333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.295564 in cell 388740 at location (0.52133333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.300241 in cell 388740 at location (0.532 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.304942 in cell 388740 at location (0.54 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.309656 in cell 388740 at location (0.548 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.314368 in cell 388740 at location (0.556 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.319065 in cell 388740 at location (0.564 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.323737 in cell 388740 at location (0.572 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.328381 in cell 388740 at location (0.58 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.333002 in cell 388740 at location (0.59066667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.337603 in cell 388740 at location (0.59866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.342193 in cell 388740 at location (0.60933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.346773 in cell 388740 at location (0.62 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.351343 in cell 388740 at location (0.628 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.355903 in cell 388740 at location (0.63866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.360447 in cell 388740 at location (0.64933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.364974 in cell 388740 at location (0.66 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.369483 in cell 388740 at location (0.668 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.373976 in cell 388740 at location (0.67866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.378457 in cell 388740 at location (0.68933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.382929 in cell 388740 at location (0.7 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.387393 in cell 388740 at location (0.71066667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.391851 in cell 388740 at location (0.71866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.396301 in cell 388740 at location (0.72933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.40074 in cell 388740 at location (0.74 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.405165 in cell 388740 at location (0.75066667 -0.0022061122 -0.0022061122) on processor 3*v1712https://develop.openfoam.com/Development/openfoam/-/issues/645-decomposeParDict invokes MPI2017-12-18T23:12:32ZMark OLESEN-decomposeParDict invokes MPIIt looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel r...It looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel run](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L610)
@andyv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/647ENH: turbulentMixingLengthDissipationRateInlet Cmu lookup for realizableKE2020-06-12T17:35:58ZAdminENH: turbulentMixingLengthDissipationRateInlet Cmu lookup for realizableKEIn turbulentMixingLengthDissipationRateInletFvPatchScalarField.C Cmu appears to be looked up or defaulted to a constant of 0.09...
```c
// Lookup Cmu corresponding to the turbulence model selected
const turbulenceModel& turbModel = ...In turbulentMixingLengthDissipationRateInletFvPatchScalarField.C Cmu appears to be looked up or defaulted to a constant of 0.09...
```c
// Lookup Cmu corresponding to the turbulence model selected
const turbulenceModel& turbModel = db().lookupObject<turbulenceModel>
(
IOobject::groupName
(
turbulenceModel::propertiesName,
internalField().group()
)
);
const scalar Cmu =
turbModel.coeffDict().lookupOrDefault<scalar>("Cmu", 0.09);
```
It looks like Cmu is being looked up from the turbulence dictionary in turbulenceProperties. However, for turbulence models like realizableKE where Cmu is not constant, I think Cmu should be looked up from the turbulence model itself. Am I reading this correctly? Thoughts?
\## Reattaching the author to the issue ticket: @graups ##v2006Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/648profiling improvements2017-12-18T05:05:42ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprofiling improvements- Would be nice for memory profiling to also record the free memory on each node. This determines when swapping is about to start.
E.g.
grep 'MemFree' /proc/meminfo- Would be nice for memory profiling to also record the free memory on each node. This determines when swapping is about to start.
E.g.
grep 'MemFree' /proc/meminfoMark OLESENMark OLESENhttps://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/650mergeMeshes does not issue warning when it merges two grids having patches wi...2018-11-29T23:04:07ZKutalmış BerçinmergeMeshes does not issue warning when it merges two grids having patches with the same name**Problem description**
Say, the user has two different grids which contains the following patches with these names:
*Grid 1:*
7( inlet outlet left right top bottom sameNamePatch)
*Grid 2:*
2( obstacle sameNamePatch)
The below comm...**Problem description**
Say, the user has two different grids which contains the following patches with these names:
*Grid 1:*
7( inlet outlet left right top bottom sameNamePatch)
*Grid 2:*
2( obstacle sameNamePatch)
The below command (OpenFOAM v1706) is then executed.
> mergeMeshes Grid1Path Grid2Path -overwrite
No warning messages were issued. Now, *merged grid* containing:
8( inlet outlet left right top bottom obstacle sameNamePatch)
Despite topologically different patches, *sameNamePatch* patches from the both grids were combined only based on their names. At times, this might be useful. Yet, IMHO, it might also be error-prone leaving the user unwarned about what has happened.https://develop.openfoam.com/Development/openfoam/-/issues/651bug : tutorial failure2018-01-08T15:19:52ZAdminbug : tutorial failuretutorials/heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
Failing in latest develop
[log.chtMultiRegionFoam](/uploads/454c0747c05d70b308d39da5fa7182d9/log.chtMultiRegionFoam)
@marktutorials/heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater
Failing in latest develop
[log.chtMultiRegionFoam](/uploads/454c0747c05d70b308d39da5fa7182d9/log.chtMultiRegionFoam)
@markMark OLESENMark OLESEN