Development issueshttps://develop.openfoam.com/groups/Development/-/issues2016-12-23T12:44:52Zhttps://develop.openfoam.com/Development/openfoam/-/issues/186BUG: runTimePostProcessing - glyphs on cutPlanes2016-12-23T12:44:52ZPrashant SonakarBUG: runTimePostProcessing - glyphs on cutPlanesAttached example replicating the issue.[pitzDaily-glyphOnCutPlane.tgz](/uploads/7ea764c6e64c8b122243c6f6e642f0d3/pitzDaily-glyphOnCutPlane.tgz)
Probably similar issue of handling PointData/CellData.Attached example replicating the issue.[pitzDaily-glyphOnCutPlane.tgz](/uploads/7ea764c6e64c8b122243c6f6e642f0d3/pitzDaily-glyphOnCutPlane.tgz)
Probably similar issue of handling PointData/CellData.Version v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/349BUG: Inconsistent library name in Header files2018-05-29T05:39:48ZPrashant SonakarBUG: Inconsistent library name in Header filesFollowing FO should have libfieldFunctionObjects.so in respective documentation header files.
- DESModelRegions/DESModelRegions.H
- PecletNo/PecletNo.H
- Q/Q.H
- vorticity/vorticity.H
- yPlus/yPlus.H
Similarly perhaps following also nee...Following FO should have libfieldFunctionObjects.so in respective documentation header files.
- DESModelRegions/DESModelRegions.H
- PecletNo/PecletNo.H
- Q/Q.H
- vorticity/vorticity.H
- yPlus/yPlus.H
Similarly perhaps following also need update
- src/functionObjects/lagrangian/cloudInfo/postProcessingDict
@andyVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/330periodic restart (eg, field-average) may exhibit odd behaviour when restartin...2018-05-29T05:39:48ZMark OLESENperiodic restart (eg, field-average) may exhibit odd behaviour when restarting a simulationThe constructor initializes with an index of 1, which is advanced by one during the calculation whenever a reset is triggered.
If the simulation is later restarted, the index 1 may not be appropriate - causing repeated resetting of the a...The constructor initializes with an index of 1, which is advanced by one during the calculation whenever a reset is triggered.
If the simulation is later restarted, the index 1 may not be appropriate - causing repeated resetting of the averaged values until the periodic interval 'catches up' to the current time.
@andy, @MattijsVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/188Generic patches are missing access to their actual underlying patch types2016-12-23T12:44:51ZMark OLESENGeneric patches are missing access to their actual underlying patch typesTrivial change.Trivial change.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/254cleanup/extend ostream to ease usage2017-01-02T12:25:13ZMark OLESENcleanup/extend ostream to ease usage*Many* places with things like this:
os.writeKeyword(key) << val << token::END_STATEMENT << nl;
Provide a single `os.writeEntry(key, val)` replacement.
The previously introduced `Ostream::beginBlock` and `Ostream::endBlock` should...*Many* places with things like this:
os.writeKeyword(key) << val << token::END_STATEMENT << nl;
Provide a single `os.writeEntry(key, val)` replacement.
The previously introduced `Ostream::beginBlock` and `Ostream::endBlock` should include a newline for convenience.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/226When using a custom GCC stack with binutils included, sometimes CMake will fa...2019-12-09T22:04:11ZMark OLESENWhen using a custom GCC stack with binutils included, sometimes CMake will fail to configure the PV*Readersreported by @wyldckat as http://bugs.openfoam.org/view.php?id=2233reported by @wyldckat as http://bugs.openfoam.org/view.php?id=2233Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/183ENH: extend coverage for wmUNSET2016-10-24T21:19:11ZPrashant SonakarENH: extend coverage for wmUNSETCertain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Certain variables could be added for further clearing of environment:
- FOAM_ETC
- WM_COMPILER_TYPE
- WM_LABEL_SIZE
- WM_LABEL_OPTION
@Roger @Pawan Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/200maxDeltaxyz changes missed in turbulence model upgrade2019-12-09T22:04:10ZAdminmaxDeltaxyz changes missed in turbulence model upgradeThe maxDeltaxyz LES delta behaviour was updated in version 2.3.x to correct excessive lengths being calculated at changes in mesh refinement, e.g. the 2:1 levels generated by snappyHexMesh. These changes were not included when moving to...The maxDeltaxyz LES delta behaviour was updated in version 2.3.x to correct excessive lengths being calculated at changes in mesh refinement, e.g. the 2:1 levels generated by snappyHexMesh. These changes were not included when moving to the templated turbulence structureVersion v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/359BUG: incorrect documentation2018-05-29T05:39:49ZPrashant SonakarBUG: incorrect documentationblendingFactor.H specifes
```
fieldName U;
```
but expects
```
field U;
```blendingFactor.H specifes
```
fieldName U;
```
but expects
```
field U;
```Version v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/222ENH: Warn if input geometry contains invalid data2019-12-09T22:04:11ZPrashant SonakarENH: Warn if input geometry contains invalid datasurfaceCheck failed with crash for attached case. [GitLab_Test.stl](/uploads/9bc0a53fa67c43645e27c0b980398b64/GitLab_Test.stl)
It would be desirable if the code gives warning like
- invalid normal (0 0 0) or
- degenerated triangles etcsurfaceCheck failed with crash for attached case. [GitLab_Test.stl](/uploads/9bc0a53fa67c43645e27c0b980398b64/GitLab_Test.stl)
It would be desirable if the code gives warning like
- invalid normal (0 0 0) or
- degenerated triangles etcVersion v1612Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/239BUG: mergeMeshes doesn't respect processor boundary ordering2016-11-15T06:10:20ZPrashant SonakarBUG: mergeMeshes doesn't respect processor boundary orderingAttached case replicating the issue.
[case-GLtest.tgz](/uploads/9d0932f2cfa2a4a9b391b4e8b9621a17/case-GLtest.tgz)Attached case replicating the issue.
[case-GLtest.tgz](/uploads/9d0932f2cfa2a4a9b391b4e8b9621a17/case-GLtest.tgz)Version v1612Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/396simpleFoam -postProcess not updating correctly2018-05-29T05:39:48ZRoger AlmenarsimpleFoam -postProcess not updating correctlyI have this case (straight duct), where I need to measure pressure drop between 2 faceZones. For this, I was interpolating pressure onto these faceZones.
When I try to run simpleFoam -postProcess to obtain pressure at these, I get diff...I have this case (straight duct), where I need to measure pressure drop between 2 faceZones. For this, I was interpolating pressure onto these faceZones.
When I try to run simpleFoam -postProcess to obtain pressure at these, I get different results if I run it at the last timestep or for all timesteps. For all timesteps it reports simply 0 (see pStart and pEnd from the log files below).
Version v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/228ENH: Add warning for missing points2016-11-10T07:02:11ZPrashant SonakarENH: Add warning for missing pointsIf cloud points method of sampling is used, the code outputs
- warning if no point is found (present case)
- valid data if at least one of the points is found (uncomment the second point from sampleDict)
It would be good if the method...If cloud points method of sampling is used, the code outputs
- warning if no point is found (present case)
- valid data if at least one of the points is found (uncomment the second point from sampleDict)
It would be good if the method warns for all missing points.
[GLtest-missingPoints.tgz](/uploads/deddc22a82f52a5af77f817acf0a878b/GLtest-missingPoints.tgz)Version v1612Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/322objectRegistry functionality2018-10-17T15:39:55ZMark OLESENobjectRegistry functionalityWhile attempting to use the subRegistry functionality to add extra information onto the mesh obr, I noticed some odd behaviour.
Delving into the code, it seems to be related to how the lookupObject works. It implicitly includes a upwards...While attempting to use the subRegistry functionality to add extra information onto the mesh obr, I noticed some odd behaviour.
Delving into the code, it seems to be related to how the lookupObject works. It implicitly includes a upwards recursion into the parent registry, only stopping when it hits Time. This means that adding subRegistry2("name=abc") to subRegistry1 will fail if the _parent_ of subRegistry1 already contained an objectRegistry with the name "abc". [Test-objectRegistry.C](/uploads/a900bca5989288cf211d5cefd70cefef/Test-objectRegistry.C)
I think we need to make this recursion an optional parameter (default = true for compatibility) to at least a few methods. It would also be a nice time to add this, for symmetry with dictionary lookupEntryPtr:
//- Lookup and return pointer to the object of the given Type,
// return nullptr if the object was not found or had the incorrect type
template<class Type>
const Type* lookupObjectPtr(const word& name, bool recursive=true) const;
//- Lookup and return the object of the given Type,
// return nullptr if the object was not found or had the incorrect type
template<class Type>
Type* lookupObjectPtr(const word& name, bool recursive=true) const;
Then use like this:
volScalarField* fieldPtr = mesh().lookupObjectPtr<volScalarField>("foo");
if (fieldPtr)
{
volScalarField& fld = *fieldPtr;
...
}
Instead of
if (mesh().foundObject<volScalarField>("foo"))
{
volScalarField& fld = const_cast<volScalarField&>(mesh().lookupObject<volScalarField>("foo"));
...
}
@andyVersion v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/256remove unneeded lines in list binary output.2017-07-03T07:20:58ZMark OLESENremove unneeded lines in list binary output.Writing an empty list in binary results in unnecessary newlines.Writing an empty list in binary results in unnecessary newlines.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/364lnInclude directory sometimes empty2018-05-29T05:39:49ZMark OLESENlnInclude directory sometimes emptyUncertain to the origins, but could be related to interrupted builds.
As discussed (@andy) probably reasonable to use '-u' whenever there is an explicit use of wmakeLnInclude.Uncertain to the origins, but could be related to interrupted builds.
As discussed (@andy) probably reasonable to use '-u' whenever there is an explicit use of wmakeLnInclude.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/220BUG: No default Allrun script2019-12-09T22:04:11ZPrashant SonakarBUG: No default Allrun script(develop branch)
incompressible/icoFoam/cavityMappingTest
contains Allrun-serial and Allrun-parallel
But Alltest routine needs one of them as native file.(develop branch)
incompressible/icoFoam/cavityMappingTest
contains Allrun-serial and Allrun-parallel
But Alltest routine needs one of them as native file.Version v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/289BUG: invalid type while accessing fields2016-11-11T12:55:22ZPrashant SonakarBUG: invalid type while accessing fieldsAttached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FO...Attached case which replicates issue while accessing pressure field (develop branch).
[pitzDaily-develop.tgz](/uploads/c2213bc9d7442d4e1e0d0b37974279c5/pitzDaily-develop.tgz)
fails with error
```
Reading p
--> FOAM Warning :
--> FOAM FATAL IO ERROR:
unexpected class name volScalarField expected volVectorField
while reading object p
file: /hosts/pnq073/home/sonakar/share/pitzDaily-develop/5/p at line 15.
From function Foam::Istream& Foam::regIOobject::readStream(const Foam::word&)
in file db/regIOobject/regIOobjectRead.C at line 295.
End
```Version v1612AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/331scaleFactor for fieldValue function-objects is 'sticky'2018-05-29T05:39:48ZMark OLESENscaleFactor for fieldValue function-objects is 'sticky'After removing a `scaleFactor` keyword from the dictionary, the previous scaling is retained. It is not reset to the default of 1.After removing a `scaleFactor` keyword from the dictionary, the previous scaling is retained. It is not reset to the default of 1.Version v1612Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/253ENH: provided a flexible string formatting2017-01-02T12:25:35ZMark OLESENENH: provided a flexible string formattingProvide the possibility of sprintf-style formatting for basic primitives (int, float) in the `Foam::name()` globals.
Example syntax,
word outname = name("%08d", intval);
instead of
std::ostringstream oss;
oss << std::setfi...Provide the possibility of sprintf-style formatting for basic primitives (int, float) in the `Foam::name()` globals.
Example syntax,
word outname = name("%08d", intval);
instead of
std::ostringstream oss;
oss << std::setfill('0') << std::setw(8) << intval;
word outname = oss.str();Version v1612Mark OLESENMark OLESEN