Development issueshttps://develop.openfoam.com/groups/Development/-/issues2016-04-21T14:11:48Zhttps://develop.openfoam.com/Development/openfoam/-/issues/91BUG: Missing integration to new TurbulenceModel structure (2)2016-04-21T14:11:48ZPrashant SonakarBUG: Missing integration to new TurbulenceModel structure (2)During some test it was reported by @Koushik
- rhoSimpleFoam reads only RASModel
Shouldn't this be generalized (and any other solvers which are still missed out)?
@andy During some test it was reported by @Koushik
- rhoSimpleFoam reads only RASModel
Shouldn't this be generalized (and any other solvers which are still missed out)?
@andy Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/589parse issues for nastran long format: triSurface2019-12-09T22:11:26ZMark OLESENparse issues for nastran long format: triSurfaceIncorrect field width for triSurface reading, but meshedSurface has correct field width.
Appears to have been introduced by 491b4ee290d2e37
Cross-reference EP#501
@PrashantIncorrect field width for triSurface reading, but meshedSurface has correct field width.
Appears to have been introduced by 491b4ee290d2e37
Cross-reference EP#501
@PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/394serious issue in interCondensingEvaporatingFoam or deeper2018-05-29T05:39:48ZAdminserious issue in interCondensingEvaporatingFoam or deeperDear Developers,
It seems that there is a serious issue in the interCondensingEvaporatingFoam (it can be hidden deeper than the solver). If you run the tutorial case: condensatingVessel, where the cooling wall is set on the left side:...Dear Developers,
It seems that there is a serious issue in the interCondensingEvaporatingFoam (it can be hidden deeper than the solver). If you run the tutorial case: condensatingVessel, where the cooling wall is set on the left side:
`left
{
type fixedValue;
value uniform 360;
}
right
{
type zeroGradient;
value $internalField;
}`
and compare its results to EXACTLY the same problem but with the definition of the cooling wall on the right side:
`right
{
type fixedValue;
value uniform 360;
}
left
{
type zeroGradient;
value $internalField;
}`
the results SHOULD be symmetric, a mirror image of eachother, but it is not the case...
Please see attached figures, which compare the results for time = 4.
they are even not close to be symmetric... it seems like a serious bug.
regards
JIM![U_BUG](/uploads/da361c03313145cfd8c2f8591ea9f128/U_BUG.jpg)![alpha_liquid_BUG](/uploads/e0c29d7fb72bfa50cc595ba8239e8b31/alpha_liquid_BUG.jpg)![T_BUG](/uploads/c13b211141172256cbf17dc3172d08ef/T_BUG.jpg)Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/1106volRegion does not support cellSet2018-12-05T22:17:16ZMark OLESENvolRegion does not support cellSetMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/727checkMesh report on volume of cellZones2020-01-03T14:14:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh report on volume of cellZonesCurrently checkMesh reports on bb of cellZone but not the volume. This would be nice to have. Attached a hack.[checkTopology.C](/uploads/6e375995442c91c5aa45f31290ac675c/checkTopology.C)
? For all zone types report:
cellZone : nCells + ...Currently checkMesh reports on bb of cellZone but not the volume. This would be nice to have. Attached a hack.[checkTopology.C](/uploads/6e375995442c91c5aa45f31290ac675c/checkTopology.C)
? For all zone types report:
cellZone : nCells + volume
faceZone : nFaces + area + signed area (i.e. closedness)
pointZone : nPoints
https://develop.openfoam.com/Development/openfoam/-/issues/327displacementMotionSolver on different mesh region2018-05-29T05:39:48ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdisplacementMotionSolver on different mesh regiondisplacementMotionSolvers access points0 through
IOobject io
(
"points0",
instance,
mesh.meshDir(),
mesh
);
This should be
IOobject io
(
...displacementMotionSolvers access points0 through
IOobject io
(
"points0",
instance,
mesh.meshDir(),
mesh
);
This should be
IOobject io
(
"points0",
instance,
polyMesh::meshSubDir,
mesh,
)
instead since the name of the mesh is already encoded in the mesh.name() and mesh.dbDir()https://develop.openfoam.com/Development/openfoam/-/issues/763checkMesh writing min tet volume and e.g. cellRegion2023-12-07T19:03:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh writing min tet volume and e.g. cellRegionUseful to have checkMesh also write the minimum tet volume per cell and cell region to e.g. detect shm problems.Useful to have checkMesh also write the minimum tet volume per cell and cell region to e.g. detect shm problems.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/731unphysical behavior of floatingObject in overInterDyMFoam2018-06-08T23:45:03ZAdminunphysical behavior of floatingObject in overInterDyMFoamI just copied floatingObject in overInterDyMFoam tutorial and edited decomposeParDict in background mesh case as follows:
numberOfSubdomains 16;
method scotch;
and set endTime to 10 in controlDict.
I found the floating object sink...I just copied floatingObject in overInterDyMFoam tutorial and edited decomposeParDict in background mesh case as follows:
numberOfSubdomains 16;
method scotch;
and set endTime to 10 in controlDict.
I found the floating object sinking to the domain bottom instead of floating with some rolling and pitching.https://develop.openfoam.com/Development/openfoam/-/issues/845handle double-dashed options2020-06-19T14:44:16ZMark OLESENhandle double-dashed optionsCan be useful when writing utilities that should mimic standard system utilities with `--option` conventions. Somewhat misleading, however, since the single-dash does not correspond to short option with bundling.
Note, in addition to equ...Can be useful when writing utilities that should mimic standard system utilities with `--option` conventions. Somewhat misleading, however, since the single-dash does not correspond to short option with bundling.
Note, in addition to equal treatment for single or double dashes, should also support `=` for option separation. For example,
decomposePar --decomposeParDict=system/mydecompDict
@andyMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/95is interFOAM restricted to certain length scales?2016-05-02T19:14:37ZAdminis interFOAM restricted to certain length scales?Hi Foam devs;
This is my 1st report and hope you guys help me out. I report this issue as I found nothing really related to this issue nor anyone could answer me in CFD online!!
I use interFOAM solver and using capillary-rise tutori...Hi Foam devs;
This is my 1st report and hope you guys help me out. I report this issue as I found nothing really related to this issue nor anyone could answer me in CFD online!!
I use interFOAM solver and using capillary-rise tutorial.
My problem is related to 2D usage of the capillary tube with an "empty" boundary condition. (I use g = 0m/s2).
I deal with micro-channels. So, I am usually dealing with length scales of 1e-6m and below.
As I understand from "empty" b.c. "nothing (no computation)" is being done along the empty dimension. What happens along other 2 axis is projected along the 3rd dimension.
As you see in the attached word doc, I performed several test cases over different length scales of the capillary tube and I see a severely diffused interface when I change my 3rd dimension. {Or to be more specific when the cross sectional area of the capillary tube is below 2e-10 m2}. Being an empty b.c., I would not expect this behavior and would expect a sharp interface for any value used in the 3rd dimension. Is there a limit based on length scales (or cross-sectional area of capillary) to which we can use interFoam? Important to mention that I tried even with a very small time step as well with no improvement of behavior. Also checked the case with a compression factor of 4 and grid refinement. Still the problem exists.
Really interested to know why this behavior is seen. As an example also attached a test case where the interface is getting diffused.
[interface_report..docx](/uploads/bdeb311b8168b6081f8e1bbc009aa8ee/interface_report..docx)
[interfaceSmaring3BbNum1we-8.zip](/uploads/2fa2df3583ff9dedd9a7180ffaed7fc2/interfaceSmaring3BbNum1we-8.zip)
Thanks and best;
SaideepSergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/347surfaceCheck - no outputThreshold option2017-12-22T15:34:47ZMatej FormansurfaceCheck - no outputThreshold optionThe source code of surfaceCheck lists the -outputThreshold option, but the utility is not compiled with the option available.
surfaceCheck returns: Invalid option: -outputThreshold
(both master and develop trees)The source code of surfaceCheck lists the -outputThreshold option, but the utility is not compiled with the option available.
surfaceCheck returns: Invalid option: -outputThreshold
(both master and develop trees)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/301update errors occur2016-11-29T16:01:24ZAdminupdate errors occurToday update errors occur in [foamToEnsight], [dataConversion] and [postProcessing].
I don't solve these errors.
[log.make-14.tar.gz](/uploads/48093b3461ce9de509a3259499546819/log.make-14.tar.gz)
---
Using: OpenFOAM-plus (see www.Ope...Today update errors occur in [foamToEnsight], [dataConversion] and [postProcessing].
I don't solve these errors.
[log.make-14.tar.gz](/uploads/48093b3461ce9de509a3259499546819/log.make-14.tar.gz)
---
Using: OpenFOAM-plus (see www.OpenFOAM.com)
Build: plus-73c5bd603f2cMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/249Field construct from indirect list2016-10-04T09:50:10ZMark OLESENField construct from indirect listCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsCurrently need two parameters to construct a field from indirect addressing. A constructor from UIndirectList for ease of use. Already filed upstream, but no activity there.
@MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/675Failures - collate fileHandler - 20.12.20172023-12-22T09:19:14ZPrashant SonakarFailures - collate fileHandler - 20.12.2017Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3line...Attached
- list of errors and 3 lines of text with error from log file. [listOfErrors.txt](/uploads/726ab37571d663fdca66149ac1df6594/listOfErrors.txt)[errorDetails-3lines.txt](/uploads/210e519f6929164ff8721094ea952146/errorDetails-3lines.txt)
- list of unconfirmed completions. [listOfUnconfirmedCompletion.txt](/uploads/4e87a9784b7354cd00da7cdc77cdfe83/listOfUnconfirmedCompletion.txt)
run with $FOAM_ETC/controlDict set to collated in
/hosts/punwor073/home/pss/OpenFOAM/compilations/ALPHA/centos6.6_compilation/OpenFOAM-plus.develop/tutorialsTest
@Mattijs @mark @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/113BUG/ENH: incomplete installtion check with foamInstallationTest2017-03-16T08:30:19ZPrashant SonakarBUG/ENH: incomplete installtion check with foamInstallationTestThe utility performs check for basic installation and confirms success.
However if some of the dependencies are not resolved (e.g. CGAL, boost,...) few utilities will not be installed (e.g. surfaceFeatureExtract, snappyHexMesh,...) bu...The utility performs check for basic installation and confirms success.
However if some of the dependencies are not resolved (e.g. CGAL, boost,...) few utilities will not be installed (e.g. surfaceFeatureExtract, snappyHexMesh,...) but rest would be OK
I think foamInstallationTest should check overall picture and report
- missing dependencies (including any third-party)
- failed libraries/applications
etc...
@Mattijs
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/402BUG: noise with -case and/or -dict option2019-12-09T21:29:27ZPrashant SonakarBUG: noise with -case and/or -dict optionThe input files read from the noiseDict must be absolute path or using environment variables like $FOAM_CASE
The relative path doesn't work.[Test_innerPath.tgz](/uploads/24d7858f28fe9f6cf4b7201d2438c654/Test_innerPath.tgz)
Ref: EP#338The input files read from the noiseDict must be absolute path or using environment variables like $FOAM_CASE
The relative path doesn't work.[Test_innerPath.tgz](/uploads/24d7858f28fe9f6cf4b7201d2438c654/Test_innerPath.tgz)
Ref: EP#338AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/658Feature: Possibility for Regular Expressions in snappyHexMeshDict, surfaceFea...2020-01-03T14:31:23ZKutalmış BerçinFeature: Possibility for Regular Expressions in snappyHexMeshDict, surfaceFeatureExtractDict etc. for File NamesA user is able to use POSIX regular expressions for OpenFOAM's **keywords** as well as **file names** for *some* entries: such as `refinementSurfaces` and `refinementRegions` entries in a `snappyHexMeshDict` as exemplified herein: https:...A user is able to use POSIX regular expressions for OpenFOAM's **keywords** as well as **file names** for *some* entries: such as `refinementSurfaces` and `refinementRegions` entries in a `snappyHexMeshDict` as exemplified herein: https://bugs.openfoam.org/view.php?id=527
Yet one currently cannot use this flexibility for **file names** in `surfaceFeatureExtractDict` and `geometry` entry of a `snappyHexMeshDict`. Might be useful to expand the above for the latter, I believe.
Kind regardsKutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/837PackedBoolList/bitSet has no ::set(const labelUList&)2018-06-07T05:57:54ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comPackedBoolList/bitSet has no ::set(const labelUList&)This has been renamed to 'setMany'. Is there a problem with ::set? Is there a clear distinction with single element setting?This has been renamed to 'setMany'. Is there a problem with ::set? Is there a clear distinction with single element setting?Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/709blended factor is written every time step2018-01-29T09:06:06Zvilfayeaublended factor is written every time stepHi,
When using
```
DebugSwitches
{
blendedSchemeBase 1;
}
```
The blended factor is printed every timestep instead of writeControl/Interval.
Best,
SebastienHi,
When using
```
DebugSwitches
{
blendedSchemeBase 1;
}
```
The blended factor is printed every timestep instead of writeControl/Interval.
Best,
Sebastienhttps://develop.openfoam.com/Development/openfoam/-/issues/843libFieldFunctionObjects writeInterval2018-06-01T13:04:49ZAdminlibFieldFunctionObjects writeIntervalIn the v1712 release the following libFieldFunctionObjects
dummy
{
type wallShearStress;
libs ("libfieldFunctionObjects.so")
writeControl timeStep;
writeInterval 1e+06;
writeFiel...In the v1712 release the following libFieldFunctionObjects
dummy
{
type wallShearStress;
libs ("libfieldFunctionObjects.so")
writeControl timeStep;
writeInterval 1e+06;
writeFields no;
patches ("board.*");
log no;
}
writes the wallShearStress field in the case directory every time step. The same controlDict sintax worked fine for the same case with the 2.4.0 version, with the field object written every specified write interval (using outputInterval in the old version).