Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-12-05T22:17:32Zhttps://develop.openfoam.com/Development/openfoam/-/issues/1102foamCleanPath may be too aggressive2018-12-05T22:17:32ZMark OLESENfoamCleanPath may be too aggressiveIt only does what it is told to, but while experimenting with different things I hit this interesting one.
With paraview installed by the operating system, it resided under '/usr/bin/paraview` and `/usr/lib64/` and has `/usr/include/par...It only does what it is told to, but while experimenting with different things I hit this interesting one.
With paraview installed by the operating system, it resided under '/usr/bin/paraview` and `/usr/lib64/` and has `/usr/include/paraview`.
Setting 'ParaView_DIR=/usr' to find this version didn't work immediately. But after cleaning out my OpenFOAM environment, everything was from the PATH.
The foamCleanPath used on exit has `$ParaView_DIR` inside of it. Since this was `/usr`, my `/usr/bin? was removed from the PATH.
It should modified never to clean out standard system paths
- /bin, /sbin, /usr/bin, /usr/sbin, /usr/local/bin, /lib, /lib64, /usr/lib, /usr/lib64v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/917naming inconsistency (UName, pName, ...)2020-01-30T08:25:03ZMark OLESENnaming inconsistency (UName, pName, ...)Previously we had "UName", "pName"..., which have mostly be changed to "U", "p" .. for dictionary inputs.
Ones still using the older names:
* [ ] solvers/basic/potentialFoam/createFields.H
* [ ] solvers/basic/potentialFoam/overPotential...Previously we had "UName", "pName"..., which have mostly be changed to "U", "p" .. for dictionary inputs.
Ones still using the older names:
* [ ] solvers/basic/potentialFoam/createFields.H
* [ ] solvers/basic/potentialFoam/overPotentialFoam/createFields.H
* [ ] solvers/basic/potentialFoam/overPotentialFoam/overPotentialFoam.C
* [ ] solvers/basic/potentialFoam/potentialFoam.C
* [ ] fvOptions/constraints/derived/velocityDampingConstraint/velocityDampingConstraint.C
* [ ] fvOptions/sources/derived/acousticDampingSource/acousticDampingSource.Cv1812https://develop.openfoam.com/Development/openfoam/-/issues/1113invertAlpha switch in setAlphaField2018-12-11T12:27:28ZJohan RoenbyinvertAlpha switch in setAlphaFieldFor simulating rising bubbles etc it is convenient to be able to invert alpha so e.g. the sphere/disc formed with setAlphaField has alpha = 0 inside and is surrounded by alpha = 1.
In the attached file setAlphaField is the version from ...For simulating rising bubbles etc it is convenient to be able to invert alpha so e.g. the sphere/disc formed with setAlphaField has alpha = 0 inside and is surrounded by alpha = 1.
In the attached file setAlphaField is the version from v1806 where I have added this functionality.
A discInConstantFlow case is added to verify that it works as intended.
Best regards,
Johan
[invertAlphaSwitchInSetAlphaField.tar.gz](/uploads/c9f69df6b0580bb60e120f106c1766df/invertAlphaSwitchInSetAlphaField.tar.gz)v1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1019New patches allowed in subsetMesh2018-12-21T18:03:00ZRoger AlmenarNew patches allowed in subsetMeshUtility subsetMesh assigns all (old) internal faces to a new patch called "oldInternalFaces". When using the option -patch, it only allows existing patches.
Would it be possible to allow a new patch being introduced with the -patch opti...Utility subsetMesh assigns all (old) internal faces to a new patch called "oldInternalFaces". When using the option -patch, it only allows existing patches.
Would it be possible to allow a new patch being introduced with the -patch option? Just specifying a non-existent name, the utility would create the patch as new, with the corresponding information in the log.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1105require function object for swirling flows2018-12-05T22:17:24ZMark OLESENrequire function object for swirling flows- as discussed on EP829, the angular momentum associated with swirling flows can be an important analysis criterion.
- Required output is linear/angular momentum, angular velocity components, angular positions.- as discussed on EP829, the angular momentum associated with swirling flows can be an important analysis criterion.
- Required output is linear/angular momentum, angular velocity components, angular positions.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1082Medium Test Loop : v18122020-01-06T06:11:19ZPrashant SonakarMedium Test Loop : v1812As of 19 Nov
- [ ] combustion/reactingFoam/RAS/SandiaD_LTS - Solver failure
- [x] combustion/fireFoam/LES/compartmentFire - Please fix decomposition for panel and main domain
- [ ] mesh/foamyHexMesh/mixerVessel - Solver failure
- [ ] mu...As of 19 Nov
- [ ] combustion/reactingFoam/RAS/SandiaD_LTS - Solver failure
- [x] combustion/fireFoam/LES/compartmentFire - Please fix decomposition for panel and main domain
- [ ] mesh/foamyHexMesh/mixerVessel - Solver failure
- [ ] multiphase/overInterDyMFoam/boatAndPropeller - Solver failure
@Developmentv1812https://develop.openfoam.com/Development/openfoam/-/issues/1017Hard-coded viscosity fields names2019-12-09T22:22:47ZAdminHard-coded viscosity fields namesViscosity models that store a local viscosity field should name the viscosity field using the constructor argument `name`, e.g. as done by the `Newtonian`, `HerschelBulkley` and `CrossPowerLaw` models; the `BirdCarreau` and `Casson` mode...Viscosity models that store a local viscosity field should name the viscosity field using the constructor argument `name`, e.g. as done by the `Newtonian`, `HerschelBulkley` and `CrossPowerLaw` models; the `BirdCarreau` and `Casson` models use a hard-coded `nu` which can result in database conflicts for multiphase cases.v1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1115Residuals function object - extend output2018-12-10T09:43:57ZAdminResiduals function object - extend outputCurrently the residuals function object only writes the initial residual to file. Forwarding on user request to output solver, initial and final residuals, and number of iterations per field.Currently the residuals function object only writes the initial residual to file. Forwarding on user request to output solver, initial and final residuals, and number of iterations per field.v1812AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1072externalCoupled uses wall temperature instead of fluid temperature2019-01-24T10:51:56ZMark OLESENexternalCoupled uses wall temperature instead of fluid temperatureAs noted in EP854, since the htc is output, the corresponding temperature should be the fluid temperature, not the wall temperature.
- make this configurable within the specification of the BC. Leaving the old behaviour (wall temperatur...As noted in EP854, since the htc is output, the corresponding temperature should be the fluid temperature, not the wall temperature.
- make this configurable within the specification of the BC. Leaving the old behaviour (wall temperature) as the default so as not to change results.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1302interIsoFoam with morphing meshes2019-07-02T09:26:33ZJohan RoenbyinterIsoFoam with morphing meshesSo far isoAdvector has not worked with morphing meshes.
A version of isoAdvection/interIsoFoam that works with morphing meshes has now been committed in the new branch feature-isoAdvectorWithMorphingMeshes
A test case demonstrating th...So far isoAdvector has not worked with morphing meshes.
A version of isoAdvection/interIsoFoam that works with morphing meshes has now been committed in the new branch feature-isoAdvectorWithMorphingMeshes
A test case demonstrating that it works can be found here:
[sphereInSqueezedMesh.tar.gz](/uploads/68d31fde5a917760b7a0a0bc852b97bd/sphereInSqueezedMesh.tar.gz)
Will someone with merge privilege look at this (@andy ,@mark )?v1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1073change internal dictionary separator2024-01-10T19:58:42ZMark OLESENchange internal dictionary separatorPropose for **1906**, we could adjust the internal dictionary separator from a dot (.) to a comma (,) separator.
The change in output appearance would be minimal. Eg,
```
/path/dictionary/subdict1,subdict2,entry
```
But by using a comma,...Propose for **1906**, we could adjust the internal dictionary separator from a dot (.) to a comma (,) separator.
The change in output appearance would be minimal. Eg,
```
/path/dictionary/subdict1,subdict2,entry
```
But by using a comma, which is rarely if ever used within a keyword, we could have things like this
```
file.obj
{
type xxx;
}
```
And now be able to recover the keyword `file.obj` from the dictionary dictName() method. At the moment the dictName() parses based on dot and would return `obj` instead.
@Developmentv1906Mark OLESENMark OLESEN2019-02-01https://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/1184turbulentDFSEM hangs at first PIMPLE iteration.2019-01-28T11:05:17ZAdminturbulentDFSEM hangs at first PIMPLE iteration.Hi,
I am trying to run with turbulentDFSEM boundary condition. I used the channel395DFSEM tutorial and modified the case.
First I tried to run with channel height for 0.8m with experimental data. The case didn't work and hangs at fir...Hi,
I am trying to run with turbulentDFSEM boundary condition. I used the channel395DFSEM tutorial and modified the case.
First I tried to run with channel height for 0.8m with experimental data. The case didn't work and hangs at first PIMPLE iteration. After many tries, It worked when I added boundary data for the whole height of the inlet.
Then I copied the same running case and modified for a channel height of 0.6m with different data. Even if I give boundary data for the whole height of the inlet, the case hangs at first PIMPLE iteration.
Both the cases can be found here.
[dfsem.zip](/uploads/8945d3bb7a778c518a58d7359353afab/dfsem.zip)
run blockMesh and then pimpleFoam to reproduce.
I am using OpenFOAM v1812. I tried running in serial and parallel. both didn't work for channel height of 0.6m.
This is similar to https://develop.openfoam.com/Development/OpenFOAM-plus/issues/894v1906Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1224DES hybrid : error when using negative velocity input2019-03-01T11:34:11ZPrashant SonakarDES hybrid : error when using negative velocity input<!--
*** 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
<!-- Summarize the bug encountered concisely -->
When using DEShybrid scheme, if the input velocity is negative (according to co-ordinate system used), the case exit with error
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
Use dummy negative x component of velocity for internalField (attached case, simply run Allrun)
### Example case
<!--
If possible, please create a SMALL example and attach it to your report
If you are using an older version of OpenFOAM this will also determine
whether the bug has been fixed in a more recent version
-->
[annularThermalMixer.tgz](/uploads/6ca79f1b6aa5773a35875cb26706b92e/annularThermalMixer.tgz)
### What is the current *bug* behaviour?
<!-- What actually happens -->
```
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2 ? in /lib64/libc.so.6
#3 Foam::sqrt(Foam::Field<double>&, Foam::UList<double> const&) at ??:?
#4 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> >
#5 Foam::DEShybrid<Foam::Vector<double> >::calcBlendingFactor(
```
### What is the expected *correct* behavior?
<!-- What you should see instead -->
### Relevant logs and/or images
<!--
Paste any relevant logs - please use code blocks (```) to format console
output, logs, and code as it's very hard to read otherwise.
-->
### 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 : v1812
Operating system : centos
Compiler : gcc
### Possible fixes
<!--
If you can, link to the line of code that might be responsible for the
problem
-->
magnitude or absolute value instead?v1906AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/1225update compilation flags for ARM2019-12-09T22:37:28ZMark OLESENupdate compilation flags for ARMAs advised by Nathan, use consistent compilation and linkage flagsAs advised by Nathan, use consistent compilation and linkage flagsv1906Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1245ENH: add function1 support for rpm in swirl fan velocity2019-03-26T05:50:05ZPrashant SonakarENH: add function1 support for rpm in swirl fan velocity### Functionality to add/problem to solve
Function1 type for rpm (e.g. table) in swirl fan velocity
### Target audience
General capability
### Links / references
Cross ref: EP#949### Functionality to add/problem to solve
Function1 type for rpm (e.g. table) in swirl fan velocity
### Target audience
General capability
### Links / references
Cross ref: EP#949v1906Prashant SonakarPrashant Sonakarhttps://develop.openfoam.com/Development/openfoam/-/issues/1124ENH: Warning/Error Message for Reynolds Stress Tensor Input - DFSEM2019-09-05T11:51:18ZKutalmış BerçinENH: Warning/Error Message for Reynolds Stress Tensor Input - DFSEM### Summary
DFSEM requires Reynolds stress tensor as input. Nonetheless, the tensor values need to be constrained in few ways in order to avoid *mathematical domain errors*, which is currently absent.
### Steps to reproduce
Assume a u...### Summary
DFSEM requires Reynolds stress tensor as input. Nonetheless, the tensor values need to be constrained in few ways in order to avoid *mathematical domain errors*, which is currently absent.
### Steps to reproduce
Assume a user inputs this: `R uniform (1 1 1 0.1 1 0.1);`
However, for example, R11*R22 - (R21)^2 > 0 should be held, which is negative with the particular setting above.
Consequently, the relevant case hangs at the outset of the first iteration without raising any warning/error message (Observed in v1712, v1806, and development-branch).
### What is the expected correct behavior?
The user should be accordingly informed, and directed to the correct usage with a warning message; and computation should be ceased.v1906Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1107BUG: turbulentDFSEMInlet; Option = planarInterpolation; decomposePar causes F...2019-11-06T18:38:30ZKutalmış BerçinBUG: turbulentDFSEMInlet; Option = planarInterpolation; decomposePar causes Floating Point Exception for Fields R/L/U### Summary
When `turbulentDFSEMInlet` with `planarInterpolation` option is ON, `decomposePar` causes FPE with the following error message:
```
Time = 0
Turbulent DFSEM patch inlet: interpolating field R from "/home/snoopy2/kuta/OpenFO...### Summary
When `turbulentDFSEMInlet` with `planarInterpolation` option is ON, `decomposePar` causes FPE with the following error message:
```
Time = 0
Turbulent DFSEM patch inlet: interpolating field R from "/home/snoopy2/kuta/OpenFOAM/kuta-v1806/run/channel395DFSEM/constant/boundaryData/inlet/0/R"
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigFpe::sigHandler(int) at ??:?
#2 ? in /lib64/libc.so.6
#3 Foam::pointToPointPlanarInterpolation::calcCoordinateSystem(Foam::Field<Foam::Vector<double> > const&) const at ??:?
#4 Foam::pointToPointPlanarInterpolation::pointToPointPlanarInterpolation(Foam::Field<Foam::Vector<double> > const&, Foam::Field<Foam::Vector<double> > const&, double, bool) at ??:?
#5 Foam::turbulentDFSEMInletFvPatchVectorField::patchMapper() const at ??:?
#6 Foam::tmp<Foam::Field<Foam::SymmTensor<double> > > Foam::turbulentDFSEMInletFvPatchVectorField::interpolateBoundaryData<Foam::SymmTensor<double> >(Foam::word const&) const at ??:?
#7 Foam::turbulentDFSEMInletFvPatchVectorField::turbulentDFSEMInletFvPatchVectorField(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#8 Foam::fvPatchField<Foam::Vector<double> >::adddictionaryConstructorToTable<Foam::turbulentDFSEMInletFvPatchVectorField>::New(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#9 Foam::fvPatchField<Foam::Vector<double> >::New(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#10 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::Boundary::readField(Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&) at ??:?
#11 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::readFields(Foam::dictionary const&) at ??:?
#12 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::readFields() at ??:?
#13 Foam::GeometricField<Foam::Vector<double>, Foam::fvPatchField, Foam::volMesh>::GeometricField(Foam::IOobject const&, Foam::fvMesh const&, bool) at ??:?
#14 ? at ??:?
#15 ? at ??:?
#16 __libc_start_main in /lib64/libc.so.6
#17 ? at /home/abuild/rpmbuild/BUILD/glibc-2.18/csu/../sysdeps/x86_64/start.S:125
Floating point exception
```
### Steps to reproduce
Please consider `tutorials/incompressible/pimpleFoam/LES/channel395DFSEM` case.
Change the following under `0/U`:
```
inlet
{
type turbulentDFSEMInlet;
...
mapMethod nearestCell;
...
}
```
to
```
inlet
{
type turbulentDFSEMInlet;
...
mapMethod planarInterpolation;
...
}
```
Then execute the following respectively:
`blockMesh`
`decomposePar`
PS: `scotch` and `hierarchial` were tested with various numbers of `numberOfSubdomains`.
@andyv1906Kutalmış BerçinKutalmış Berçinhttps://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/1300Bug in interIsoFoam with nAlphaSubCycles > 1 and nOuterCorrectors > 12019-05-20T12:44:38ZJohan RoenbyBug in interIsoFoam with nAlphaSubCycles > 1 and nOuterCorrectors > 1Bug found and fixed by Henning Scheufler from DLR Bremen.
An illustration of the wrong behaviour and correct behaviour after the fix can be found here:
![bugFixIllustration](/uploads/c10f4c2f09f9e33c779ea0d31aaa2265/bugFixIllustration.p...Bug found and fixed by Henning Scheufler from DLR Bremen.
An illustration of the wrong behaviour and correct behaviour after the fix can be found here:
![bugFixIllustration](/uploads/c10f4c2f09f9e33c779ea0d31aaa2265/bugFixIllustration.png)
The damBreak case for generating the above figure can be found here:
[damBreak-plus.tar.gz](/uploads/1a9c8216ed241eccba4819ada863ed40/damBreak-plus.tar.gz)
Solution committed in new branch from develop: bugfix-isoAdvectorSubCyclingOuterCorr
I tried to merge this into develop and push to remote develop but was not allowed to do so.
So someone with the right privilege needs to do this (@andy @mark ).v1906Mark OLESENMark OLESEN