Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-08-02T13:33:39Zhttps://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 v1706https://develop.openfoam.com/Development/openfoam/-/issues/1511ensightReadFile ignores string limits2019-12-09T22:37:29ZMark OLESENensightReadFile ignores string limitsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1132rotorDisk tutorial uses 'slip' patch type2018-12-24T08:58:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrotorDisk tutorial uses 'slip' patch typeMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1472dynamicCode should use polling instead of re-checking only once2020-06-05T08:12:26ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdynamicCode should use polling instead of re-checking only once### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' secon...### Functionality to add/problem to solve
db/dynamicLibrary/dynamicCode/dynamicCode.C in parallel can have that the library does not exist on all slave processors. It first checks at beginning and then waits 'fileModificationSkew' seconds and rechecks. If this fails the code will fail. Nicer if the check gets done multiple times before failing.
Alternatively send over the library (is this possible? is it cross-node compatible?)https://develop.openfoam.com/Development/openfoam/-/issues/1510support specified time for transformPoints2019-12-15T21:09:38ZPrashant Sonakarsupport specified time for transformPoints### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constant### Functionality to add/problem to solve
transformPoints reads time from points instance. But it might be nice to operate on given time.
### Proposal
As discussed with @mark Use given time or default to constantMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1001IOstream uses pointer instead of bool operator2018-09-11T12:16:52ZMark OLESENIOstream uses pointer instead of bool operatorMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1341Improve lumped point functionality2020-06-19T14:38:04ZMark OLESENImprove lumped point functionality- Alternative euler orders for lumped point definitions
- with the more recent changes to quaternion and euler coordinate rotations we can now also support rotations
beyond the standard 'ZXZ' euler intrinsic rotations.
- cross ref: E...- Alternative euler orders for lumped point definitions
- with the more recent changes to quaternion and euler coordinate rotations we can now also support rotations
beyond the standard 'ZXZ' euler intrinsic rotations.
- cross ref: EP 1008
- Support multiple controllers (not just a single axis)
- Enable VTK output in parallel
Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1014intertia of triangle returns full tensor (instead of symmetric one)2022-04-26T16:11:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comintertia of triangle returns full tensor (instead of symmetric one)v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/983BUG: externalWallHeatFluxTemperatureFvPatchScalarField crashes on reconstruct...2019-12-09T22:22:46ZAdminBUG: externalWallHeatFluxTemperatureFvPatchScalarField crashes on reconstructPar when qrName != nonev1812https://develop.openfoam.com/Development/openfoam/-/issues/1140wmRefresh clears WM_NCOMPPROCS2024-01-15T10:07:55ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwmRefresh clears WM_NCOMPPROCSIf I do a wmRefresh (as advised by ./makeParaview) it resets the WM_NCOMPPROCS so it doesn't build in parallel anymore.If I do a wmRefresh (as advised by ./makeParaview) it resets the WM_NCOMPPROCS so it doesn't build in parallel anymore.https://develop.openfoam.com/Development/openfoam/-/issues/1429Suggestions for the Submitting Issues page2019-11-12T14:37:03ZAdminSuggestions for the Submitting Issues page# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fix...# Problem
During the OpenFOAM Workshop 2019, it was noted that several people are not sure how to submit (good) bug reports, mainly due to not knowing how to report system-related technical information. @bgschaid @mark
# Suggested fixes
## Patches for page "Submitting Issues"
I had a look into the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues) and I added a bit more information, trying to keep the text short and the instructions precise and platform-independent. Since I cannot open merge requests or even fork the repository, I attach a set of patches here (they are for the Wiki repository, anyway). These patches are based on d8c4d7 and I have tested them locally.
[wiki_Submitting-Issues_patches.tar.gz](/uploads/3ad5ce768f455724b1077150d59c21ab/wiki_Submitting-Issues_patches.tar.gz)
<p>
<details>
<summary>Here is a preview:</summary>
![Screenshot_from_2019-09-05_16-40-55](/uploads/422c9f0ab4f069a1bdbc713814bc87fb/Screenshot_from_2019-09-05_16-40-55.png)
</details>
</p>
## Add link on openfoam.com
A link to the page [Bug Reporting](https://www.openfoam.com/code/bug-reporting.php) is very prominent both in the side menu and in the "Code" drop-down. :+1:
However, the statement:
> Bug and issue reporting is provided via the repository hosting site https://develop.openfoam.com described [here](https://www.openfoam.com/code/repositories.php)
leads to a generic page, while it should lead to the page [Submitting Issues](https://develop.openfoam.com/Development/OpenFOAM-plus/wikis/page-submitting-issues).