Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T22:18:11Zhttps://develop.openfoam.com/Development/openfoam/-/issues/829foamToVTK -poly produces unreadable vtk file2019-12-09T22:18:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamToVTK -poly produces unreadable vtk file[polyMesh.tgz](/uploads/1ab421bc84de37ab82d0bbd87f419124/polyMesh.tgz)
If you run
foamToVTK -poly
on attached mesh the resulting vtk file cannot be read by paraview (tried 5.5.0 and 5.4.1): "vtkUnstructuredGridReader (0x350e130): Un...[polyMesh.tgz](/uploads/1ab421bc84de37ab82d0bbd87f419124/polyMesh.tgz)
If you run
foamToVTK -poly
on attached mesh the resulting vtk file cannot be read by paraview (tried 5.5.0 and 5.4.1): "vtkUnstructuredGridReader (0x350e130): Unrecognized keyword: 6"Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1280inconsistent emissivity for externalWallHeatFluxTemperatureFvPatchScalarField2019-12-09T22:37:28ZMark OLESENinconsistent emissivity for externalWallHeatFluxTemperatureFvPatchScalarField- emissivity is partly ignored (hpTa) when there is no solid resistance- emissivity is partly ignored (hpTa) when there is no solid resistanceMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/947tracking does not handle cells with inverted pyramids (it does handle inverte...2021-07-06T13:08:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtracking does not handle cells with inverted pyramids (it does handle inverted cells with tets)This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.https://develop.openfoam.com/Development/openfoam/-/issues/155BUG: runTimePostProcessing with sampledPatches2023-12-07T19:02:01ZPrashant SonakarBUG: runTimePostProcessing with sampledPatchesExtended #97
The coloring by field/color works for isoSurface
But the same failed for sampled patch. (attached example for motorBike case)
[postProcessingDict_iso_usingFunctionObject](/uploads/c7ee499a8760984aef87131184456004/p...Extended #97
The coloring by field/color works for isoSurface
But the same failed for sampled patch. (attached example for motorBike case)
[postProcessingDict_iso_usingFunctionObject](/uploads/c7ee499a8760984aef87131184456004/postProcessingDict_iso_usingFunctionObject)AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/740isoAdvector : Wrong parameter read in fvSolution. vof2IsoTol is expected by t...2019-12-09T22:18:10ZAdminisoAdvector : Wrong parameter read in fvSolution. vof2IsoTol is expected by the sources. isoFaceTol is used in all tutorials.In the source file ./finiteVolume/fvMatrices/solvers/isoAdvection/isoAdvection/isoAdvection.C, the parameter vof2IsoTol is read in fvSolution dictionary. See line 83 :
78 // Interpolation data
79 ap_(mesh_.nPoints()),
...In the source file ./finiteVolume/fvMatrices/solvers/isoAdvection/isoAdvection/isoAdvection.C, the parameter vof2IsoTol is read in fvSolution dictionary. See line 83 :
78 // Interpolation data
79 ap_(mesh_.nPoints()),
80
81 // Tolerances and solution controls
82 nAlphaBounds_(dict_.lookupOrDefault<label>("nAlphaBounds", 3)),
83 vof2IsoTol_(dict_.lookupOrDefault<scalar>("vof2IsoTol", 1e-8)),
84 surfCellTol_(dict_.lookupOrDefault<scalar>("surfCellTol", 1e-8)),
85 gradAlphaBasedNormal_
86 (
87 dict_.lookupOrDefault<bool>("gradAlphaNormal", false)
88 ),
However, in all tutorials in $FOAM_TUTORIALS/multiphase/interIsoFoam, the parameter "isoFaceTol" is specified in fvSolution files, instead of vof2IsoTol.
The consequence of this bug is that the parameter "isoFaceTol" specified in fvSolution of the tutorials cases is never used.
The vof2IsoTol expected by the sources (instead of "isoFaceTol") is always taken at its default value, so 1.e-8.
The correction is simple :
- Either correct all tutorials and replace isoFaceTol by vof2IsoTol, and leave the sources unchanged
- Or correct the sources to replace vof2IsoTol by isoFaceTol, and leave the tutorials unchanged
Regards
Lionel GAMEThttps://develop.openfoam.com/Development/openfoam/-/issues/76BUG: yPlus utility and FO doesn't work properly with SA model2016-03-01T04:57:48ZPrashant SonakarBUG: yPlus utility and FO doesn't work properly with SA modelAttached case illustrates the issue.[pitzDaily-yPlus-SA.tgz](/uploads/c6e40fc73ab815c732f9ab7ebf80ed80/pitzDaily-yPlus-SA.tgz)
When turbulence model is changed to e.g. kEpsilon, it works.
Probably due to missing nut reference.
@...Attached case illustrates the issue.[pitzDaily-yPlus-SA.tgz](/uploads/c6e40fc73ab815c732f9ab7ebf80ed80/pitzDaily-yPlus-SA.tgz)
When turbulence model is changed to e.g. kEpsilon, it works.
Probably due to missing nut reference.
@Sergio AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/111data alignment cause gap in particle binary representation2016-06-30T22:09:37ZMark OLESENdata alignment cause gap in particle binary representationReplacing the bool 'active' with an int value uses the same space and provides a more predictable layout in memory, which is useful when working directly with the binary chunks.
Changing to int also permits future uses to mark different...Replacing the bool 'active' with an int value uses the same space and provides a more predictable layout in memory, which is useful when working directly with the binary chunks.
Changing to int also permits future uses to mark different states.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1273odd timeset for ensight collated output2019-12-09T22:37:28ZMark OLESENodd timeset for ensight collated outputAs noted by @Prashant - there seem to be too many timesets when sampling.As noted by @Prashant - there seem to be too many timesets when sampling.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/46ENH: Upgrade case/Allrun with -decomposeParDict option2016-04-25T10:53:07ZPrashant SonakarENH: Upgrade case/Allrun with -decomposeParDict optionNew feature -decomposeParDict could be used to update tutorial
incompressible/pisoFoam/les/motorBike/motorBike/
@Sergio @Mattijs New feature -decomposeParDict could be used to update tutorial
incompressible/pisoFoam/les/motorBike/motorBike/
@Sergio @Mattijs AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/924redistributePar with numberOfSubdomains 1 in decomposeParDict2020-01-08T14:38:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar with numberOfSubdomains 1 in decomposeParDictRunning cht cases with in decomposeParDict:
```
regions
{
heater
{
numberOfSubdomains 1;
}
}
```
conflicts with the old way of doing reconstruction through this method. In earlier versions of redistributePar we used ...Running cht cases with in decomposeParDict:
```
regions
{
heater
{
numberOfSubdomains 1;
}
}
```
conflicts with the old way of doing reconstruction through this method. In earlier versions of redistributePar we used `numberOfSubdomains = 1` to indicate reconstruction mode. Now there is a `-reconstruct` option.
Choices:
- recognise multi-region cases and don't switch on reconstruction mode if numberOfSubdomains 1
- do not use numberOfSubdomains setting to indicate reconstruction mode
@markMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/72ENH: Add keepPatches as example2016-03-28T04:31:46ZPrashant SonakarENH: Add keepPatches as exampleAdd keepPatches and explanaton for using "old" behavior of SHM in
$FOAM_APP/utilities/mesh/generation/snappyHexMesh/snappyHexMeshDict
@andy @Sergio Add keepPatches and explanaton for using "old" behavior of SHM in
$FOAM_APP/utilities/mesh/generation/snappyHexMesh/snappyHexMeshDict
@andy @Sergio Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1199premature short-circuit in components functionObject2019-02-14T21:55:35ZMark OLESENpremature short-circuit in components functionObject@andy - can't see why the write() and clear() methods should short-circuit on failure.
Surely we'd want to have this instead?
```
forAll(resultNames_, i)
{
written = writeObject(resultNames_[i]) && written;
}
```@andy - can't see why the write() and clear() methods should short-circuit on failure.
Surely we'd want to have this instead?
```
forAll(resultNames_, i)
{
written = writeObject(resultNames_[i]) && written;
}
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/93singleCellFvMesh writes polyMesh to 0/ directory and not time2020-01-08T14:30:18ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsingleCellFvMesh writes polyMesh to 0/ directory and not timesingleCellMesh
- polyMesh is in 0/ directory (tested in parallel but universal I guess)
- system/fv* are illegal links when running in parallelsingleCellMesh
- polyMesh is in 0/ directory (tested in parallel but universal I guess)
- system/fv* are illegal links when running in parallelhttps://develop.openfoam.com/Development/openfoam/-/issues/591Missing write action in DESModelRegions function object2019-12-09T22:11:26ZAdminMissing write action in DESModelRegions function objectIn `DESModelRegions.C` at `Foam::functionObjects::DESModelRegions::write()`:
isn't a line
```
DESModelRegions.write();
```
missing after line 173?In `DESModelRegions.C` at `Foam::functionObjects::DESModelRegions::write()`:
isn't a line
```
DESModelRegions.write();
```
missing after line 173?AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1229Fan : cyclic: pressure vs velocity curve using csv file : syntax issue2019-03-26T09:52:49ZPawan GhildiyalFan : cyclic: pressure vs velocity curve using csv file : syntax issueHello
I am trying to define , pressure drop vs velocity curve (to define a pressure curve for fan)using following syntax
as mentioned here in
> https://openfoam.com/documentation/guides/latest/api/fanFvPatchField_8H_source.html
> p...Hello
I am trying to define , pressure drop vs velocity curve (to define a pressure curve for fan)using following syntax
as mentioned here in
> https://openfoam.com/documentation/guides/latest/api/fanFvPatchField_8H_source.html
> patchName>
>
> {
> type fan;
> patchType cyclic;
> jumpTable csvFile;
> csvFileCoeffs
> {
> nHeaderLine 1;
> refColumn 0;
> componentColumns 1(1);
> separator ",";
> mergeSeparators no;
> file "<constant>/pressureVsU";
> } value uniform 0;
> }
However , while running it throws error
> Entry 'nHeaderLine' not found in dictionary "/
However if change it to following i.e put all information inside csvFileCoeff dict outside
> cyclicFaces_master
> {
> type fan;
> patchType cyclic;
> jumpTable csvFile;
>
> // csvTableCoeffs
> // {
> nHeaderLine 0;
> refColumn 0;
> componentColumns (1);
> separator ",";
> mergeSeparators no;
> file "<constant>/pressureVsU";
> outOfBounds clamp;
> // }
> }
I have attached case here [TJunctionFan-fancurve.tgz](/uploads/d8beaa65de3436c989ce8fa982a3e7ee/TJunctionFan-fancurve.tgz)https://develop.openfoam.com/Development/openfoam/-/issues/455an inconsistence of gamma in nacaAirfoil tutorial of sonicFoam2019-12-09T21:29:28ZAdminan inconsistence of gamma in nacaAirfoil tutorial of sonicFoam`// caseDir/0/p
// gamma = 1.3
...
"outlet.*"
{
type waveTransmissive;
field p;
psi thermo:psi;
gamma 1.3;
fieldInf $pressure;
lIn...`// caseDir/0/p
// gamma = 1.3
...
"outlet.*"
{
type waveTransmissive;
field p;
psi thermo:psi;
gamma 1.3;
fieldInf $pressure;
lInf 1;
value $internalField;
}
...
`
However, in the thermophysical file, gamma = 1.4 which can be calculated by molecular weight and Cp.https://develop.openfoam.com/Development/openfoam/-/issues/57Strange typos in "blockMeshDict" at "tutorials/combustion/XiDyMFoam/annularCo...2016-01-18T09:02:47ZAdminStrange typos in "blockMeshDict" at "tutorials/combustion/XiDyMFoam/annularCombustorTurbine"File: `tutorials/combustion/XiDyMFoam/annularCombustorTurbine/constant/polyMesh/blockMeshDict`
Sentence "Uhe Open Source CFD Uoolbox" should be "The Open Source CFD Toolbox".
File: `tutorials/combustion/XiDyMFoam/annularCombustorTurbine/constant/polyMesh/blockMeshDict`
Sentence "Uhe Open Source CFD Uoolbox" should be "The Open Source CFD Toolbox".
AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/887thermo sharing temperature2018-07-01T05:46:06ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comthermo sharing temperatureExplicitly use T. @Sergio Explicitly use T. @Sergio Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1022Mistake in build guide2018-10-09T08:33:10ZJohan RoenbyMistake in build guideIn https://www.openfoam.com/code/build-guide.php
it should say
$WM_THIRD_PARTY_DIR/BUILD.md
instead of
$WM_PROJECT_DIR/ThirdParty-v1806/BUILD.mdIn https://www.openfoam.com/code/build-guide.php
it should say
$WM_THIRD_PARTY_DIR/BUILD.md
instead of
$WM_PROJECT_DIR/ThirdParty-v1806/BUILD.mdhttps://develop.openfoam.com/Development/openfoam/-/issues/56Typo in the Build Guide instructions2016-01-14T10:29:47ZAdminTypo in the Build Guide instructionsIn the page http://www.openfoam.com/code/build-guide.php - section **Post-compilation steps** - there are two places stating `simpleFOAM` and should be `simpleFoam`.In the page http://www.openfoam.com/code/build-guide.php - section **Post-compilation steps** - there are two places stating `simpleFOAM` and should be `simpleFoam`.AdminAdmin