Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-12-09T21:29:27Zhttps://develop.openfoam.com/Development/openfoam/-/issues/371STYLE: Correct documentation vector field2019-12-09T21:29:27ZPrashant SonakarSTYLE: Correct documentation vector fieldvalue should be vector input at
src/finiteVolume/lnInclude/pressureInletOutletVelocityFvPatchVectorField.H
@Mattijsvalue should be vector input at
src/finiteVolume/lnInclude/pressureInletOutletVelocityFvPatchVectorField.H
@MattijsVersion v1706AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/204Simplify, cleanup mesh conversion infrastructure2017-12-18T23:19:31ZMark OLESENSimplify, cleanup mesh conversion infrastructureWill continue for 1706 as wellWill continue for 1706 as wellVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/352cleanup noFunctionObjects vs withFunctionObjects etc2018-08-09T10:21:58ZMark OLESENcleanup noFunctionObjects vs withFunctionObjects etcpotentialFoam is the only solver or application to use `-withFunctionObjects`, all others have an implicit `-noFunctionObjects`. This exception does make sense, but opens questions about the general handling of function-objects. There ar...potentialFoam is the only solver or application to use `-withFunctionObjects`, all others have an implicit `-noFunctionObjects`. This exception does make sense, but opens questions about the general handling of function-objects. There are a number of utilities (conversion, blockMesh, etc) without a time-loop and thus it doesn't make much sense to even provide a `-noFunctionObjects` option for them.
Propose adding a argList::noFunctionObjects() method - similar to the argList::noParallel() method - to remove the availability of the `-noFunctionObjects` option and adjust Time accordingly.
Currently:
functionObjects_
(
*this,
argList::validOptions.found("withFunctionObjects")
? args.optionFound("withFunctionObjects")
: !args.optionFound("noFunctionObjects")
)
Proposed:
functionObjects_
(
*this,
argList::validOptions.found("withFunctionObjects")
? args.optionFound("withFunctionObjects")
: argList::validOptions.found("noFunctionObjects")
? !args.optionFound("noFunctionObjects")
: false
)
For potentialFoam it also doesn't make sense to provide the `-noFunctionObjects` option at all. It adds clutter and will always be ignored anyhow.
@andy @Mattijs @PrashantVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1071MeshObject uses objectRegistry foundObject followed by lookupObject2018-11-20T14:12:38ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMeshObject uses objectRegistry foundObject followed by lookupObjectSmall optimisation.Small optimisation.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1145dictionary closing scope does flush2021-07-06T14:54:59ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdictionary closing scope does flushWriting a subdictionary using dictionary::write causes a flush of the underlying stream. Ideally we would only flush at IOdictionary closing.Writing a subdictionary using dictionary::write causes a flush of the underlying stream. Ideally we would only flush at IOdictionary closing.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/209Environment variables in libs not handled2016-12-20T17:10:25ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comEnvironment variables in libs not handledlibs entries are not expanded.
libs ("$FOAM_USER_LIBSRC/libbla.so");
libs entries are not expanded.
libs ("$FOAM_USER_LIBSRC/libbla.so");
https://develop.openfoam.com/Development/openfoam/-/issues/488functionObjects - on-the-fly usage of cuttingPlane with ACMI.2017-06-29T20:12:21ZAdminfunctionObjects - on-the-fly usage of cuttingPlane with ACMI.functionObjects (cuttingPlane) used on the fly.
cuttingPlane seems to fail when using ACMI (and/or AMI?) with a pimpleDymFoam derived solver. Error message includes: "not implemented"... The issue should be reproducible with ACMI tutoria...functionObjects (cuttingPlane) used on the fly.
cuttingPlane seems to fail when using ACMI (and/or AMI?) with a pimpleDymFoam derived solver. Error message includes: "not implemented"... The issue should be reproducible with ACMI tutorial (extended to 3D).https://develop.openfoam.com/Development/openfoam/-/issues/590inconsistencies in parsing primitives from strings2017-10-02T07:48:47ZMark OLESENinconsistencies in parsing primitives from stringsParsing from something like `" 123 "` behaves differently if tokenizer is used or readScalar.Parsing from something like `" 123 "` behaves differently if tokenizer is used or readScalar.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/158uniform/functionObjects/functionObjectProperties gets written even if no func...2020-01-03T09:58:37ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/functionObjects/functionObjectProperties gets written even if no functionObjectsE.g. icoFoam/cavity case
E.g. icoFoam/cavity case
Version v1612https://develop.openfoam.com/Development/openfoam/-/issues/511mesa build failure in Ubuntu162017-06-29T08:14:56ZPawan Ghildiyalmesa build failure in Ubuntu16Hi Mark
I am compiling mesa in bash in Windows.
It has Ubuntu bash with following specification.
It fail at one point . See attached log .
Dstributor ID: Ubuntu.
Description: Ubuntu 16.04.2 LTS.
Release: 16.04 .
C...Hi Mark
I am compiling mesa in bash in Windows.
It has Ubuntu bash with following specification.
It fail at one point . See attached log .
Dstributor ID: Ubuntu.
Description: Ubuntu 16.04.2 LTS.
Release: 16.04 .
Codename: xenial
Some one too faced similar issue and provided work around ,
however I could not understand where to put it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528169Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/109provide parcel property type information2019-08-02T13:33:39ZMark OLESENprovide parcel property type informationThe property names from a parcel/parcel are known from PropertyList, but not their data types.The property names from a parcel/parcel are known from PropertyList, but not their data types.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/304BUG : foamToEnsight -nodeValues places an extra space in the .case file2016-11-28T23:37:04ZAdminBUG : foamToEnsight -nodeValues places an extra space in the .case fileWhen the -nodeValues option is used in foamToEnsight, it places an extra space in the .case file for each variable (see attached pic).
![ensight_error](/uploads/b1a128b351eb5ab7bdc4f528ea11145e/ensight_error.PNG)
This causes ensi...When the -nodeValues option is used in foamToEnsight, it places an extra space in the .case file for each variable (see attached pic).
![ensight_error](/uploads/b1a128b351eb5ab7bdc4f528ea11145e/ensight_error.PNG)
This causes ensight to fail when trying to open the case. There is no issue when -nodeValues isn't used.https://develop.openfoam.com/Development/openfoam/-/issues/148Inconsistent/incorrect build environment2023-12-07T19:01:57ZMark OLESENInconsistent/incorrect build environmentthird-party settings may be inconsistent with the OF settings.
Using lib instead of lib64 for 3rd-party gmp paths etc.third-party settings may be inconsistent with the OF settings.
Using lib instead of lib64 for 3rd-party gmp paths etc.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/568implicit conversion of string to switch2017-08-11T16:07:11ZMark OLESENimplicit conversion of string to switchThe Switch constructors (from string) allows this sort of thing:
Switch sw;
sw = "none";
these seems to be too much automatic conversion - constructor should be explicit.The Switch constructors (from string) allows this sort of thing:
Switch sw;
sw = "none";
these seems to be too much automatic conversion - constructor should be explicit.v1712Mark OLESENMark OLESENhttps://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/484PackedList is sometimes non-lazy2017-06-29T20:38:04ZMark OLESENPackedList is sometimes non-lazyThe `unset()` method never auto-vivifies, whereas the `set()` method *always* auto-vivifies. In the case where `set()` is called with a zero for its argument - eg, `set(index, 0)` - this should behave identically to an `unset()` and not ...The `unset()` method never auto-vivifies, whereas the `set()` method *always* auto-vivifies. In the case where `set()` is called with a zero for its argument - eg, `set(index, 0)` - this should behave identically to an `unset()` and not auto-vivify out-of-range entries.Version v1706Mark OLESENMark OLESENhttps://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/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/1498BUG: reading a labelList preceded by its size in a binary-format dictionary t...2020-01-23T12:35:17ZKutalmış BerçinBUG: reading a labelList preceded by its size in a binary-format dictionary throws FatalError<!--
*** 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
You can see how your report will be ...<!--
*** 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
You can see how your report will be rendered on the platform by using the
"preview" tab above
-->
<!--
All text between these markers are comments and will not be present in the
report
-->
### Summary
<!-- Summarize the bug encountered concisely -->
When `FoamFile.format` is `binary` in a dictionary, a labelList keyword preceded by its size, e.g. `labelList 1(1);` is not read, and `FatalError` is thrown due to [operator>>](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/OpenFOAM-v1906/src/OpenFOAM/containers/Lists/UList/UListIO.C#L201). The problem in practice is that [CSV.C](https://develop.openfoam.com/Development/OpenFOAM-plus/blame/master/src/OpenFOAM/primitives/functions/Function1/CSV/CSV.C#L281) writes out a labelList entry with its size at writeTime. When a restart is needed, the simulation fails.
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
`tutorials/combustion/reactingFoam/RAS/chokedNozzle`
Make the following changes thereat:
```
format binary;
```
```
componentColumns 1( 2 );
```
`./Allrun`
### 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 : dev-13Nov
- Operating system : osuse 15.1
- Compiler : gcc
cross-ref EP[#1176](https://exchange.openfoam.com/node/1176)
@markMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/376meshToMesh - incorrect cutting patch addressing2019-12-09T22:04:15ZAdminmeshToMesh - incorrect cutting patch addressingcutting patches indices are derived by finding the patch name on the tgtRegion - this should be performed on the srcRegion. Also, there is no protection for the case that the patch is not found, where the patch index is set to -1.cutting patches indices are derived by finding the patch name on the tgtRegion - this should be performed on the srcRegion. Also, there is no protection for the case that the patch is not found, where the patch index is set to -1.Version v1706