Development issueshttps://develop.openfoam.com/groups/Development/-/issues2015-12-18T05:11:41Zhttps://develop.openfoam.com/Development/openfoam/-/issues/41BUG: Combustion: Case hungup2015-12-18T05:11:41ZPrashant SonakarBUG: Combustion: Case hungup/home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop-16Dec/tutorials/combustion/XiDyMFoam/annularCombustorTurbine
@Mattijs /home/alex2/prashant/OpenFOAM/OpenFOAM-dev-OpenCFD.develop-16Dec/tutorials/combustion/XiDyMFoam/annularCombustorTurbine
@Mattijs Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/698checkMesh does not report on processor patches2023-06-26T13:01:00ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh does not report on processor patchesWe currently suppress info on processor patches. I would like to change this to only suppress -if running parallel- so we can use
checkMesh -case processorXXX
to find out number of points/edges on the processor patches.We currently suppress info on processor patches. I would like to change this to only suppress -if running parallel- so we can use
checkMesh -case processorXXX
to find out number of points/edges on the processor patches.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/991flowRateOutletVelocity not suitable for unsteady cases (pisoFoam)2019-07-03T20:05:15ZAdminflowRateOutletVelocity not suitable for unsteady cases (pisoFoam)Dear all,
I believe that the boundary condition flowRateOutletVelocity is not suitable for unsteady cases (pisoFoam).
The way it is written (proportional correction) allows convergence to be reached while iterating, but for piso algorith...Dear all,
I believe that the boundary condition flowRateOutletVelocity is not suitable for unsteady cases (pisoFoam).
The way it is written (proportional correction) allows convergence to be reached while iterating, but for piso algorithm you have to converge at each time step. Proportional correction can eventually be in contrast with CFL limitations as well.
What do you think?
Best regards
MNhttps://develop.openfoam.com/Development/openfoam/-/issues/686distributedTriSurfaceMesh hangs with motorBike2019-01-09T09:06:50ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdistributedTriSurfaceMesh hangs with motorBikeChange motorBike tutorial to use distributedTriSurfaceMesh (see attached snappyHexMeshDict)
[snappyHexMeshDict](/uploads/92dd12940023efa4669d8d5c98d4bb74/snappyHexMeshDict)
- hangs in surfaceRedistributePar when using collated format
-...Change motorBike tutorial to use distributedTriSurfaceMesh (see attached snappyHexMeshDict)
[snappyHexMeshDict](/uploads/92dd12940023efa4669d8d5c98d4bb74/snappyHexMeshDict)
- hangs in surfaceRedistributePar when using collated format
- hangs in snappyHexMesh when using uncollated formatMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/707BUG: Not function timeVaryingMappedFixedValue patch for compressibleInterFoam2018-07-02T16:18:04ZAdminBUG: Not function timeVaryingMappedFixedValue patch for compressibleInterFoamI'm testing timeVaryingMappedFixedValue using several VOF model solvers. I noticed that this patch does not function in compressibleInterFoam.
If you run one case I uploaded, you know that the alpha.water does not flow at all.
[sample...I'm testing timeVaryingMappedFixedValue using several VOF model solvers. I noticed that this patch does not function in compressibleInterFoam.
If you run one case I uploaded, you know that the alpha.water does not flow at all.
[sampleGood.tar.gz](/uploads/1529b87ee03fbead542e3a26cfd286fa/sampleGood.tar.gz)
[sampleNotGood.tar.gz](/uploads/ee1de4cefa2ba435d2c5f34c10c1e8e5/sampleNotGood.tar.gz)https://develop.openfoam.com/Development/openfoam/-/issues/931sampled extraction for cloud information2018-07-18T12:38:22ZMark OLESENsampled extraction for cloud information@Roger would like to extract cloud positions and some parcel characteristic (eg, diameter) into a simple list.
If we have a sampledSet type that works directly/indirectly with cloud positions we could reuse the set writers for CSV output...@Roger would like to extract cloud positions and some parcel characteristic (eg, diameter) into a simple list.
If we have a sampledSet type that works directly/indirectly with cloud positions we could reuse the set writers for CSV output etc.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1043logical ops with odd return values.2018-10-17T15:40:45ZMark OLESENlogical ops with odd return values.In ops.H we have various operations defined, but things like `andOp`, `lessOp` etc should be returning bool.In ops.H we have various operations defined, but things like `andOp`, `lessOp` etc should be returning bool.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/510ENH: Add warning/error message when input is incorrect2018-10-05T07:46:48ZPrashant SonakarENH: Add warning/error message when input is incorrectsolver hangs infinitely when input in fvSolution is
```
(U|k|epsilon|omega|f|v2)
```
instead of
```
"(U|k|epsilon|omega|f|v2)"
```
file to replicate on pitzDaily case [fvSolution](/uploads/d61cd6b4a8207555fdab282d49ac6ef2/fvSo...solver hangs infinitely when input in fvSolution is
```
(U|k|epsilon|omega|f|v2)
```
instead of
```
"(U|k|epsilon|omega|f|v2)"
```
file to replicate on pitzDaily case [fvSolution](/uploads/d61cd6b4a8207555fdab282d49ac6ef2/fvSolution)
@Mattijs @markhttps://develop.openfoam.com/Development/openfoam/-/issues/689overPimpleDyMFoam with pressure reference2018-06-08T23:51:12ZAdminoverPimpleDyMFoam with pressure referenceWhile running the tutorial case simpleRotor I noticed an issue with the pressure reference for closed domains. It is clearly visible which point is chosen as the reference point. A velocity which should not exist appears in that corner. ...While running the tutorial case simpleRotor I noticed an issue with the pressure reference for closed domains. It is clearly visible which point is chosen as the reference point. A velocity which should not exist appears in that corner. Also the pressure fluctuates like crazy. Turning on adjustPhi or oversetAdjustPhi did not help. Tested with v1706 and v1712.https://develop.openfoam.com/Development/openfoam/-/issues/1258SurfaceFeatureExtract cannot handle filenames starting with numerals.2019-03-29T07:59:34ZAdminSurfaceFeatureExtract cannot handle filenames starting with numerals.<!--
*** 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
When the filename of the geometry file in surfaceFeatureExtractDict starts with numerals, the applications quits with an error. However, filenames starting with numerals are legitimate filenames.
### Steps to reproduce
The issue can be reproduced by renaming the name of the geometry file to be processed to one starting with numerals, and making the corresponding change in the surfaceFeatureExtractDict.
### Example case
A simple example case has been added to this bug report.
[001_surfaceFeatureExtract_FileName_Bug.tar.gz](/uploads/a3892b7d3455cbb041dcf4ff382b2dc6/001_surfaceFeatureExtract_FileName_Bug.tar.gz)
### What is the current *bug* behaviour?
When surfaceFeatureExtract is run, and the name of the geometry file starts with numerals, surfaceFeatureExtract quits with the following error:
```
--> FOAM FATAL IO ERROR:
Expected a '(' or a '{' while reading List, found on line 17: word '_cfdValidation_8mm_15deg_001.stl'
file: /home/simuser001/OpenFOAM/simuser001-plus/run/RJ990_Issue_Testing/001_surfaceFeatureExtract_FileName_Bug/system/surfaceFeatureExtractDict at line 17.
From function char Foam::Istream::readBeginList(const char*)
in file db/IOstreams/IOstreams/Istream.C at line 134.
FOAM exiting
```
### What is the expected *correct* behavior?
The expectation is that the application surfaceFeatureExtract find the geometry file specified in the dict, extracts the edges, and quits without any error.
### Relevant logs and/or images
```
-NA-
```
### Environment information
<!--
Providing details of your set-up can help us identify any issues, e.g.
OpenFOAM version : v1806|v1812|v1906 etc
Operating system : ubuntu|openSUSE|centos etc
Hardware info : any info that may help?
Compiler : gcc|intel|clang etc
-->
OpenFOAM version : 1812
Operating system : CentOS 7
Compiler : GCC 4.8.5
### Possible fixes
None so far.https://develop.openfoam.com/Development/openfoam/-/issues/900cleanCase deletes blockMeshDict2018-07-01T05:46:07ZJohan RoenbycleanCase deletes blockMeshDictMany OpenFOAM users still use older OF version. When they eventually try to port their older OpenFOAM cases to newer OpenFOAM versions it can be quite annoying that the cleanCase function in bin/tools/CleanFunctions deletes the constant/...Many OpenFOAM users still use older OF version. When they eventually try to port their older OpenFOAM cases to newer OpenFOAM versions it can be quite annoying that the cleanCase function in bin/tools/CleanFunctions deletes the constant/polyMesh, where their blockMeshDict may still reside.
I suggest introducing a check in cleanCase, so that it moves an existing blockMeshDict (or any *Dict in polyMesh for that matter) from constant/polyMesh to the system folder before deleting polyMesh.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/806redistributePar does not work with collated I/O format2022-05-07T08:43:37ZAdminredistributePar does not work with collated I/O formatHi, it seems that the redistributePar Tool is only written for uncollated format. Using collated format is not possible. Process stucks - see logfile. For reproducing I run the cavitiy mesh/parallel case
controlDict adds:
OptimisationS...Hi, it seems that the redistributePar Tool is only written for uncollated format. Using collated format is not possible. Process stucks - see logfile. For reproducing I run the cavitiy mesh/parallel case
controlDict adds:
OptimisationSwitches
{
//- Parallel IO file handler
// collated (default), collated or masterUncollated
fileHandler collated;
maxThreadFileBufferSize 0; -> this is set to zero by purpose for cluster setup!
maxMasterFileBufferSize 2e9;
}
[log.redistributePar.decompose](/uploads/9226895799c39911aa7529d4754ed860/log.redistributePar.decompose)
\#\# Reattaching the author to the issue ticket: @hxaxtma \#\#Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/84timeVaryingMappedFixedValue uses linear extrapolation if outside triangulation2019-12-11T16:52:37ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtimeVaryingMappedFixedValue uses linear extrapolation if outside triangulationtimevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest...timevaryingMappedFixedValue creates a triangulation 'under the hood'. It then uses bilinear interpolation for all sample points inside a triangle. For sample points outside all triangles it uses a bilinear interpolation using the nearest triangle. This is generally not ideal and especially very high aspect ratio triangles it gives problems (e.g. interpolation weights (23937.3 -48293 24356.7)
I think we should use zero-gradient outside triangles.
https://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.com