Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-04-04T01:40:40Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1215develop branch blockMesh creates bad 1D meshes (but not master)2019-04-04T01:40:40ZAdmindevelop branch blockMesh creates bad 1D meshes (but not master)### Summary
It seems that the current develop branch generates a blockMesh which differs from the current master branch. For me, I found that this was causing 1D evaporation problems' pressure solves to fail.
### Steps to reproduce
C...### Summary
It seems that the current develop branch generates a blockMesh which differs from the current master branch. For me, I found that this was causing 1D evaporation problems' pressure solves to fail.
### Steps to reproduce
Check out master, compile, make a simple 1D mesh. Rename the polyMesh to polyMesh.bak, checkout develop, compile, now make the blockMesh again. Not only are the meshes different, the one on develop causes 1D apps to fail. I imagine it doesn't have issues with higher dimensional meshes, otherwise someone would have caught this. Also, I cannot pinpoint which commit did this. I tried cherry picking 22891065698f3793033862c7c3031b43241df595 thinking that seemed suspect, but it seems to not be it.
This is the kind of thing which unit tests could catch. From what I read online, your all's sentiment on that is that you don't have the time to write these, right? That's understandable in every way. If given the opportunity, I would absolutely write some unit tests and make a merge request.https://develop.openfoam.com/Development/openfoam/-/issues/1214new surface writer losing serial/parallel preference2019-02-22T17:42:17ZMark OLESENnew surface writer losing serial/parallel preference- as noted in nightly by @Prashant- as noted in nightly by @PrashantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1212surfaceFieldValue with sampled surface and interpolation could be simplified2020-05-08T08:41:31ZMark OLESENsurfaceFieldValue with sampled surface and interpolation could be simplifiedIf the sampled surface has `interpolate()` on, the face value is obtained by using a cellPoint interpolation to the surface vertices, which are then averaged for each face. It would likely make more sense to simply use a cellPoint interp...If the sampled surface has `interpolate()` on, the face value is obtained by using a cellPoint interpolation to the surface vertices, which are then averaged for each face. It would likely make more sense to simply use a cellPoint interpolation to the face centre.
Any opinions? @andy @Mattijs @SergioMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1211performance improvements for redistributePar2021-07-29T13:58:15ZMark OLESENperformance improvements for redistributeParEP-901 @MattijsEP-901 @MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1209twoPhaseMixtureEThermo has pDivU optional in constructor but mandatory in read2019-02-21T06:54:16ZMark OLESENtwoPhaseMixtureEThermo has pDivU optional in constructor but mandatory in readMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1208dpdt uninitialized in basicThermo2024-01-11T16:59:35ZMark OLESENdpdt uninitialized in basicThermo- one constructor ignores the "dpdt" entry- one constructor ignores the "dpdt" entryMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1207scotch, ptscotch input checking2020-01-08T14:37:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscotch, ptscotch input checking<!--
*** 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
scotch, ptscotch do not check processorWeights inputMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1206updates for run-time post-processing2022-03-10T19:03:27ZMark OLESENupdates for run-time post-processing- add parallel rendering
- additional volume filters (eg, isosurface, cutting plane) and other direct simulation data
- avoid write/read file for exchanging information (hold in memory)
Cross-ref: EP719- add parallel rendering
- additional volume filters (eg, isosurface, cutting plane) and other direct simulation data
- avoid write/read file for exchanging information (hold in memory)
Cross-ref: EP719v1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1204renaming of residuals to solverInfo2019-02-14T21:54:35ZMark OLESENrenaming of residuals to solverInfo```
--> FOAM Warning :
Unknown function type residuals
```
Could resolve compatibility by adding an addNamed... lookup, but may also need symlink the etc/caseDicts/../numerical/residuals* files```
--> FOAM Warning :
Unknown function type residuals
```
Could resolve compatibility by adding an addNamed... lookup, but may also need symlink the etc/caseDicts/../numerical/residuals* filesAdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1203change of name for functionObject: motorbike pisoFoam2019-07-03T19:32:56ZPawan Ghildiyalchange of name for functionObject: motorbike pisoFoam<!---
Please read this!
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
--->
### Summary
(Summarize the bug encountered concisely)...<!---
Please read this!
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
--->
### Summary
(Summarize the bug encountered concisely)
residual functionObjects is not found while running simpleFoam
### Steps to reproduce
(How one can reproduce the issue - this is very important)
run case by All run scripts.
### Example case
**Motorbike case: ** tutorials/incompressible/pisoFoam/LES/motorBike/motorBike/system/stabilizationSchemes
tutorials/compressible/rhoSimpleFoam/aerofoilNACA0012
tutorials/heatTransfer/buoyantBoussinesqPimpleFoam/BenardCells
tutorials/incompressible/pimpleFoam/laminar/planarPoiseuille
tutorials/incompressible/simpleFoam/bump2D
### What is the current *bug* behaviour?
residual functionObjects is not found while running simpleFoam
### What is the expected *correct* behavior?
Name of functionObject need to be changed to new name which is
solverInfo
### Relevant logs and/or images
"--> FOAM Warning :"
Unknown function type residuals
Valid function types :
"
### Environment information
(OpenFOAM version : develop
(Operating system : redhat
(Hardware info : XXX)
https://develop.openfoam.com/Development/openfoam/-/issues/1202writeFileHeader and initialise occurs before first execution (surfaceFieldVal...2021-07-06T15:24:28ZMark OLESENwriteFileHeader and initialise occurs before first execution (surfaceFieldValues)The initialisation and writing of file header occurs immediately upon construction. For sampled surfaces (for example), this means that a surface is being generated and updated immediately. However, this surface may not be valid until mu...The initialisation and writing of file header occurs immediately upon construction. For sampled surfaces (for example), this means that a surface is being generated and updated immediately. However, this surface may not be valid until much later when the surfaceFieldValue should actually be executed (eg, an iso-surface of a field that is created later).Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1200Function1::New input checking2020-01-08T14:49:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comFunction1::New input checking### Summary
Function1::New produces not very good error messages if the dictionary entry does not exist.### Summary
Function1::New produces not very good error messages if the dictionary entry does not exist.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/1197Add grids to foamMonitor (gnuplot)2019-12-18T16:20:34ZRoger AlmenarAdd grids to foamMonitor (gnuplot)It would be good to add an option to foamMonitor, like "-g|--grid", to plot the background grid to the monitoring plots, so that it is easier to identify the trends and values.
In gnuplot, it is enough to add a "set grid" line to the gnu...It would be good to add an option to foamMonitor, like "-g|--grid", to plot the background grid to the monitoring plots, so that it is easier to identify the trends and values.
In gnuplot, it is enough to add a "set grid" line to the gnuplot file.v1912Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1196paraFoam -block2019-07-11T22:09:51ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comparaFoam -block`paraFoam -block` has a button to display patch names. It does not seem to do anything.`paraFoam -block` has a button to display patch names. It does not seem to do anything.https://develop.openfoam.com/Development/openfoam/-/issues/1195'FOAM FATAL IO ERROR' in tut externalSolarLoad2019-12-09T22:37:28ZAdmin'FOAM FATAL IO ERROR' in tut externalSolarLoad<!---
Please read this!
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
--->
### Summary
In externalSolarLoad, when i turn on the ...<!---
Please read this!
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
--->
### Summary
In externalSolarLoad, when i turn on the DebugSwitches (faceShading and solarCalculator), a solver returns "FOAM FATAL IO ERROR" in the process of calculation.
### Steps to reproduce
As mentioned the above Summary, see a logfile.
[logOnDebugSwitches](/uploads/744fecbabb8f11d15d7388d77d3f25f5/logOnDebugSwitches)
### Example case
tutorial case 'externalSolarLoad'
### What is the current *bug* behaviour?
(What actually happens)
### What is the expected *correct* behavior?
(What you should see instead)
### Relevant logs and/or images
--> FOAM FATAL IO ERROR:
Bad token - could not get word
file: input at line 0.
From function Foam::Istream& Foam::operator>>(Foam::Istream&, Foam::word&)
in file primitives/strings/word/wordIO.C at line 45.
FOAM exiting
### Environment information
(OpenFOAM version : v1812)
(Operating system : ubuntu18.04)
(Hardware info : intel x86_64)
### Possible fixes
(If you can, link to the line of code that might be responsible for the problem)https://develop.openfoam.com/Development/openfoam/-/issues/1194volRegion and momentum do not handle moving meshes well2021-07-06T15:22:55ZMark OLESENvolRegion and momentum do not handle moving meshes well- changes made in develop branch (eg, dc1446d6c515), but cached values not being updated- changes made in develop branch (eg, dc1446d6c515), but cached values not being updatedMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1193Parser does not read nans2019-03-16T18:35:30ZAdminParser does not read nansNANs are printed as "-nan" is ASCII format, and the parser cannot read them back.
The specific error message is:
```
--> FOAM FATAL IO ERROR:
wrong token type - expected Scalar, found on line 24216: punctuation '-'
file: <...> at lin...NANs are printed as "-nan" is ASCII format, and the parser cannot read them back.
The specific error message is:
```
--> FOAM FATAL IO ERROR:
wrong token type - expected Scalar, found on line 24216: punctuation '-'
file: <...> at line 24216.
From function Foam::Istream& Foam::operator>>(Foam::Istream&, Foam::doubleScalar&)
in file lnInclude/Scalar.C at line 160.
```
The content of the mentioned line is
-nanhttps://develop.openfoam.com/Development/openfoam/-/issues/1192Incorrect re-reading of time-based function objects2019-07-03T19:34:29ZAdminIncorrect re-reading of time-based function objects### Summary
Time control -based function objects do not re-read correctly
### Steps to reproduce
Try adding a FO, e.g.
DESModelRegions
{
type DESModelRegions;
libs ("libfieldFunctionObje...### Summary
Time control -based function objects do not re-read correctly
### Steps to reproduce
Try adding a FO, e.g.
DESModelRegions
{
type DESModelRegions;
libs ("libfieldFunctionObjects.so");
}
During the run, change to:
DESModelRegions
{
type DESModelRegions;
libs ("libfieldFunctionObjects.so");
writeControl writeTime;
}
and the new write settings are not enforced and data is still written at every time step (default behaviour)
### What is the current *bug* behaviour?
Function objects created as `timeControl` hold a local reference to the actual/desired FO. When the FO is re-read, the high-level FO is read and bypasses any time-based settings.v1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1190create module ignores -output option2019-12-09T22:37:28ZMark OLESENcreate module ignores -output optionalso no easy way to pass in preferences
@ivanspissoalso no easy way to pass in preferences
@ivanspissoMark OLESENMark OLESEN