Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T22:04:15Zhttps://develop.openfoam.com/Development/openfoam/-/issues/265BUG: snappyHexMesh doesn't fully respect the -decomposeParDict option2019-12-09T22:04:15ZAdminBUG: snappyHexMesh doesn't fully respect the -decomposeParDict optionsnappyHexMesh doesn't fully respect the -decomposeParDict option. Crashes half way through when it starts looking for system/decomposeParDict. Looks like it occurs right after the castellation phase. In addition, the -decomposeParDict op...snappyHexMesh doesn't fully respect the -decomposeParDict option. Crashes half way through when it starts looking for system/decomposeParDict. Looks like it occurs right after the castellation phase. In addition, the -decomposeParDict option on snappyHexMesh doesn't appear to like relative paths (this works with other utilities though).
This is the command I used to run...
mpirun -np 4 snappyHexMesh -overwrite -decomposeParDict /home/graupjj/OpenFOAM/graupjj-plus/run/of/system/decomposeParDict1 -profiling -parallel
This is the error I got...
Doing final balancing
Found 0 zoned faces to keep together.
Found 0 separated coupled faces to keep together.
[0]
[0]
[0] --> FOAM FATAL IO ERROR:
[0] cannot find file
[0]
[0] file: /home/graupjj/OpenFOAM/graupjj-plus/run/of/processor0/system/decomposeParDict at line 0.
[0]
[0] From function regIOobject::readStream()
[0] in file db/regIOobject/regIOobjectRead.C at line 237.
[0]
FOAM parallel run exiting
Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/344renumberMesh twice in the same workflow2018-05-29T05:39:49ZvilfayeaurenumberMesh twice in the same workflowHi,
In some situation, you have to run renumberMesh twice in the same workflow. For example, if you run a coarse case, map to a fine mesh and run it.
This leads to a error message:
Reading volScalarField cellID
[3]
[3]
[3] --> FOAM ...Hi,
In some situation, you have to run renumberMesh twice in the same workflow. For example, if you run a coarse case, map to a fine mesh and run it.
This leads to a error message:
Reading volScalarField cellID
[3]
[3]
[3] --> FOAM FATAL IO ERROR:
[3] size 58624 is not equal to the given value of 58185
[3]
[3] file: /home/a45bwpq/OpenFOAM/1606+/a45bwpq-16.06plus/tutorials/incompressible/simpleFoam/motorBike/processor3/constant/cellID from line 18 to line 58953.
[3]
[3] From function Foam::Field<Type>::Field(const Foam::word&, const Foam::dictionary&, Foam::label) [with Type = double; Foam::label = int]
[3] in file /appl/openfoam/16.06plus/OpenFOAM-16.06plus/src/OpenFOAM/lnInclude/Field.C at line 295.
[3]
FOAM parallel run exiting
motorBike test case is attached to reproduce the error.
Best,
Sebastien
[motorBike.tgz](/uploads/67b76ae6ecde6bb5fb8a3fa1179fdc9d/motorBike.tgz)https://develop.openfoam.com/Development/openfoam/-/issues/369Incomplete cleanup of paraview environment2019-12-09T21:29:26ZMark OLESENIncomplete cleanup of paraview environment* LD_LIBRARY_PATH is not being cleaned at all when switching between paraview versions.
* PATH is being cleaned against the third-party `paraview-*`, although 3rd party paraview is installed as `ParaView-*`. The additional cleanup for Pa...* LD_LIBRARY_PATH is not being cleaned at all when switching between paraview versions.
* PATH is being cleaned against the third-party `paraview-*`, although 3rd party paraview is installed as `ParaView-*`. The additional cleanup for ParaView_DIR may not catch this (if it was unset elsewhere).Mark OLESENMark OLESEN2017-01-06https://develop.openfoam.com/Development/openfoam/-/issues/126oscillatingACMI tutorial reports open cells2016-06-16T13:17:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comoscillatingACMI tutorial reports open cellsThis is solved by commit 90ba6113b597880dd3200bd37284627302bf9cc7 from OpenFOAM-dev
This is solved by commit 90ba6113b597880dd3200bd37284627302bf9cc7 from OpenFOAM-dev
https://develop.openfoam.com/Development/openfoam/-/issues/797subTriSurfaceMesh does not work with distributedTriSurfaceMesh2018-06-08T22:52:16ZAdminsubTriSurfaceMesh does not work with distributedTriSurfaceMeshI'm testing out the feature "subTriSurfaceMesh" as described at: https://www.openfoam.com/releases/openfoam-v3.0+/meshing.php
The issue is that it does not work for distirbutedTriSurfaceMesh. I am not sure if it was intended to work wit...I'm testing out the feature "subTriSurfaceMesh" as described at: https://www.openfoam.com/releases/openfoam-v3.0+/meshing.php
The issue is that it does not work for distirbutedTriSurfaceMesh. I am not sure if it was intended to work with all triSurfaceMesh types; if the behavior is as intended I would suggest it as a feature request.https://develop.openfoam.com/Development/openfoam/-/issues/1274decomposePar -allRegions produces different results than decomposePar -region...2019-07-04T11:47:18ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar -allRegions produces different results than decomposePar -region XXX<!--
*** 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
-->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
heatTransfer/chtMultiRegionFoam/windshieldDefrost
Set system/decomposeParDict to scotch
```decomposePar -allRegions```
vs
```
decomposePar -region exterior
decomposePar -region ice
decomposePar -region cabin
```
- eg `simple` method produces exactly the same decompositions
- we compile scotch with `SCOTCH_DETERMINISTIC`
bug or feature of scotch?https://develop.openfoam.com/Development/openfoam/-/issues/1030Syntax error near unexpected token2018-10-16T05:59:30ZAdminSyntax error near unexpected token![issue](/uploads/25b3de515657517c15dc079eed035083/issue.PNG)
I installed OpenFOAM about a month ago, it worked very well. But from last week, these errors keep showing up when I just open the Ubuntu without doing any things.
Is there...![issue](/uploads/25b3de515657517c15dc079eed035083/issue.PNG)
I installed OpenFOAM about a month ago, it worked very well. But from last week, these errors keep showing up when I just open the Ubuntu without doing any things.
Is there anyone having the same problem? What should I do?
Thank you!Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/383Error sourcing etc/bashrc with relative path2018-05-29T05:39:49ZJohan RoenbyError sourcing etc/bashrc with relative pathIf I try to source the etc/bashrc file without specifying its full path I get "-bash: cd: etc/bashrc: Not a directory".
To reproduce do:
dhi@argos3:~$ cd /home/dhi/OpenFOAM/OpenFOAM-plus
dhi@argos3:~/OpenFOAM/OpenFOAM-plus$ source etc/...If I try to source the etc/bashrc file without specifying its full path I get "-bash: cd: etc/bashrc: Not a directory".
To reproduce do:
dhi@argos3:~$ cd /home/dhi/OpenFOAM/OpenFOAM-plus
dhi@argos3:~/OpenFOAM/OpenFOAM-plus$ source etc/bashrc
-bash: cd: etc/bashrc: Not a directory
dhi@argos3:~/OpenFOAM/OpenFOAM-plus$ source ~/OpenFOAM/OpenFOAM-plus/etc/bashrc
dhi@argos3:~/OpenFOAM/OpenFOAM-plus$
Same problem in v1612+Mark OLESENMark OLESENhttps://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.com