Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-07-02T09:33:45Zhttps://develop.openfoam.com/Development/openfoam/-/issues/909improve robustness of cmake targets2018-07-02T09:33:45ZMark OLESENimprove robustness of cmake targetsAs note as a [catalyst issue](https://develop.openfoam.com/Community/catalyst/issues/5) some failures if WM_OSTYPE is not set.
Transfer some of the configuration setup from there.As note as a [catalyst issue](https://develop.openfoam.com/Community/catalyst/issues/5) some failures if WM_OSTYPE is not set.
Transfer some of the configuration setup from there.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/910controlDict libs entry can introduce unresolvable symbols2020-03-13T13:44:50ZMark OLESENcontrolDict libs entry can introduce unresolvable symbolsAs @andy encountered, the `libs` entry can impose new library dependencies. For utilities such as `foamListTimes` etc, we only wish to obtain a simple listing of time directories.
- Add an additional optional construction flag for the T...As @andy encountered, the `libs` entry can impose new library dependencies. For utilities such as `foamListTimes` etc, we only wish to obtain a simple listing of time directories.
- Add an additional optional construction flag for the Time constructor.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/911interIsoFoam crashes with nOuterCorrectors > 12018-12-20T18:06:59ZAdmininterIsoFoam crashes with nOuterCorrectors > 1Hello,
when using interIsoFoam (version OpenFOAM-plus develop-prerelease) with nOutercorrectors larger than 1, the solver crashes with the following error message:
> --> FOAM FATAL ERROR:
> previous iteration field
> IOobject: volSca...Hello,
when using interIsoFoam (version OpenFOAM-plus develop-prerelease) with nOutercorrectors larger than 1, the solver crashes with the following error message:
> --> FOAM FATAL ERROR:
> previous iteration field
> IOobject: volScalarField alpha.water readOpt: 0 writeOpt: 0 globalObject: 0 "/home/heinri8/OpenFOAM/OpenFOAM-plus/tutorials/multiphase/interIsoFoam/damBreak/0"
>
> not stored. Use field.storePrevIter() at start of iteration.
To reproduce this simply take the dambreak tutorial case and change nOuterCorrectors from 1 to 2 and start the Allrun script.
I assume there is a typo in the alphaEqn.H file on line 14. It states:
alpha1.prevIter();
It should probably be as following:
alpha.storePrevIter();
since the previous iteration is actually called later in the file on line 23.
Regards
MartinMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/912flag backwards compatibility for old dictionary keywords2018-12-21T18:06:52ZMark OLESENflag backwards compatibility for old dictionary keywords- redirectType : used by coded objects
- functionObjectLibs- redirectType : used by coded objects
- functionObjectLibsv1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/913reference point - on processor boundary!2020-01-03T14:16:37ZPrashant Sonakarreference point - on processor boundary!multiphase/interIsoFoam/sloshingTank2D
1) Please correct the decomposerParDict to (1 2 2) since 2D case.
2) With this correction, when solver is initiated, it fails with error
```
[3] --> FOAM FATAL IO ERROR:
[3] Unable to set referen...multiphase/interIsoFoam/sloshingTank2D
1) Please correct the decomposerParDict to (1 2 2) since 2D case.
2) With this correction, when solver is initiated, it fails with error
```
[3] --> FOAM FATAL IO ERROR:
[3] Unable to set reference cell for field p
Reference point pRefPoint (0 0 0.15) found on 2 domains (should be one)
```
@andy @Mattijs @mark @Sergiov1812https://develop.openfoam.com/Development/openfoam/-/issues/914reduce/remove the foamPackXXX scripts.2019-06-28T09:51:21ZMark OLESENreduce/remove the foamPackXXX scripts.- should remove all of the non-git elements, since it is unreliable to be packaging files from the working directory (which could contain extra rubbish) and not from the git repository.
- add support for add in submodules. cf #907- should remove all of the non-git elements, since it is unreliable to be packaging files from the working directory (which could contain extra rubbish) and not from the git repository.
- add support for add in submodules. cf #907v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/916aerofoilNACA0012_directionalRefinement : not visited by Allrun2018-07-03T04:19:19ZPrashant SonakaraerofoilNACA0012_directionalRefinement : not visited by AllrunPlease add the tutorial aerofoilNACA0012_directionalRefinement for execution in
mesh/snappyHexMesh/Allrun
@Mattijs @andyPlease add the tutorial aerofoilNACA0012_directionalRefinement for execution in
mesh/snappyHexMesh/Allrun
@Mattijs @andyv1812Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/918inconsistency in defining turbulence field "R"2018-10-09T08:55:44ZAdmininconsistency in defining turbulence field "R"Hello,
There is inconsistency in defining turbulence field "R". Webpage https://www.openfoam.com/documentation/cpp-guide/html/guide-fos-field-turbulence-fields.html#sec-fos-field-turbulence-fields-usage shows Fields stored on the mesh d...Hello,
There is inconsistency in defining turbulence field "R". Webpage https://www.openfoam.com/documentation/cpp-guide/html/guide-fos-field-turbulence-fields.html#sec-fos-field-turbulence-fields-usage shows Fields stored on the mesh database with the prefix ***turbulenceModel*** whereas it is stored with ***turbulenceProperties***
@Pawan @andyhttps://develop.openfoam.com/Development/openfoam/-/issues/919Ensight format for writing non-time based fields2019-07-11T22:15:57ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comEnsight format for writing non-time based fieldsSome surface utilities write ensight using the (sampled)surfaceWriters. These files do not have a time-directory in the name which upsets the extraction of the timename inside the ensightSurfaceWriterTemplates.CSome surface utilities write ensight using the (sampled)surfaceWriters. These files do not have a time-directory in the name which upsets the extraction of the timename inside the ensightSurfaceWriterTemplates.CMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/920checkMesh reports negative internal points2020-06-18T22:05:35ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcheckMesh reports negative internal points- take multiRegionHeater tutorial
- comment out regions in decomposeParDict, i.e. use scotch for decomposition
```mpirun -np 4 checkMesh -region heater -parallel```
produces
```
internal points: -2
--> FOAM Warning :
From fu...- take multiRegionHeater tutorial
- comment out regions in decomposeParDict, i.e. use scotch for decomposition
```mpirun -np 4 checkMesh -region heater -parallel```
produces
```
internal points: -2
--> FOAM Warning :
From function void Foam::printMeshStats(const Foam::polyMesh&, bool)
in file checkTools.C at line 66
```https://develop.openfoam.com/Development/openfoam/-/issues/921Restricted Geometry Decomposition2018-12-21T18:07:58ZMark OLESENRestricted Geometry DecompositionSupport for specifying geometric decomposition constraints. Cross-ref EP724.
For some simulations it is necessary to ensure that particular regions remain on the same process. These requirements should be describable via an enclosing ST...Support for specifying geometric decomposition constraints. Cross-ref EP724.
For some simulations it is necessary to ensure that particular regions remain on the same process. These requirements should be describable via an enclosing STL file, or some other description.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/922Add searchableSurface single point getVolumeType2018-07-10T16:07:40ZMark OLESENAdd searchableSurface single point getVolumeTypeFor #921 we need to cycle over potentially several surfaces and faces.
It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.For #921 we need to cycle over potentially several surfaces and faces.
It is too slow and costly to use the getVolumeType for the list of points - need the lowest level single point query.v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/923overPimpleDyMFoam does not satisfy the mass conservation betwee inlet and outlet2020-03-13T13:44:37ZAdminoverPimpleDyMFoam does not satisfy the mass conservation betwee inlet and outletHello,
I have a very simple test case. It is a 2D cylinder bounded by two fixed wall (top and bottom) and pressure inlet and outlet. The flow is laminar. When starting to move the cylinder periodically (the fluid is initially at rest) ...Hello,
I have a very simple test case. It is a 2D cylinder bounded by two fixed wall (top and bottom) and pressure inlet and outlet. The flow is laminar. When starting to move the cylinder periodically (the fluid is initially at rest) in direction of the inlet and outlet i realized by monitoring the mass fluxes at the inlet and the outlet that they are not equal in magnitude. So i was wondering if I have something wrong in the setup or there is an issue in the pressure equation (which should guarantee the mass conservation.
Please find attached the case. I made an Allrun command. Maybe someone can give me a hint what's going wrong. It was testes with the newest version 1806[OcilatingCylinderinFluidAtRestSend.tar.gz](/uploads/2beea06449f9cd405a84095a96190177/OcilatingCylinderinFluidAtRestSend.tar.gz)
\## Reattaching the author to the issue ticket: @HappyKiter ##https://develop.openfoam.com/Development/openfoam/-/issues/924redistributePar with numberOfSubdomains 1 in decomposeParDict2020-01-08T14:38:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar with numberOfSubdomains 1 in decomposeParDictRunning cht cases with in decomposeParDict:
```
regions
{
heater
{
numberOfSubdomains 1;
}
}
```
conflicts with the old way of doing reconstruction through this method. In earlier versions of redistributePar we used ...Running cht cases with in decomposeParDict:
```
regions
{
heater
{
numberOfSubdomains 1;
}
}
```
conflicts with the old way of doing reconstruction through this method. In earlier versions of redistributePar we used `numberOfSubdomains = 1` to indicate reconstruction mode. Now there is a `-reconstruct` option.
Choices:
- recognise multi-region cases and don't switch on reconstruction mode if numberOfSubdomains 1
- do not use numberOfSubdomains setting to indicate reconstruction mode
@markMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/925pimpleFoam uses non-native collectives2024-01-08T10:49:00ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.compimpleFoam uses non-native collectivesIn e.g. pimpleFoam it still uses the following non-native collectives:
- Pstream::scatter inside fileMonitor::updateStates (only if `runTimeModifiable`)
- Foam::gMax<double> (from Foam::reduce) in CourantNo determination
- bound() from ...In e.g. pimpleFoam it still uses the following non-native collectives:
- Pstream::scatter inside fileMonitor::updateStates (only if `runTimeModifiable`)
- Foam::gMax<double> (from Foam::reduce) in CourantNo determination
- bound() from RASModels::kEpsilon
- reduce<bool, Foam::andOp<bool> > from p.needReference()
(done by adding a `error::printStack(Pout)` to `UIPstream::read`)
These could optionally be converted to native MPI calls.https://develop.openfoam.com/Development/openfoam/-/issues/926Use vtm output for OpenFOAM to VTK translation2018-12-21T18:07:47ZMark OLESENUse vtm output for OpenFOAM to VTK translationThe current foamToVTK and vtkWrite (function object) write legacy files on a per-processor basis. This should be adjusted to use the vtm (multi-block) format that incorporates a vtu file for the internal mesh and vtp files for the bounda...The current foamToVTK and vtkWrite (function object) write legacy files on a per-processor basis. This should be adjusted to use the vtm (multi-block) format that incorporates a vtu file for the internal mesh and vtp files for the boundary patches.
The realization might entail collection on the master, or aggregates.
The output shall contain all relevant fields within each timestep file. v1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/927dry-run2024-01-16T05:32:45ZMatej Formandry-rundry-run option not always error free on tutorials.
So far found Error messages on: interFoam/laminar/damBreak/damBreak:
- problems with sampling
interFoam and interIsoFoam/RAS/sloshingTank2D
Error:
nCellsInCoarsestLevel is too hig...dry-run option not always error free on tutorials.
So far found Error messages on: interFoam/laminar/damBreak/damBreak:
- problems with sampling
interFoam and interIsoFoam/RAS/sloshingTank2D
Error:
nCellsInCoarsestLevel is too high (complains even when set to 1).
there might be other warnings in other tutorials as well.
ENHANCEMENT suggestion: when error reported, would be nice to point into particular dictionary in question,
not just the class reference where the trouble is.Prashant SonakarPrashant Sonakarhttps://develop.openfoam.com/Development/openfoam/-/issues/928Support user-independent build2020-03-16T14:24:57ZMark OLESENSupport user-independent buildWhen building for cluster installations the user prefs.sh and various config.sh/ files will be used, but this can lead to installations that are no longer properly portable.When building for cluster installations the user prefs.sh and various config.sh/ files will be used, but this can lead to installations that are no longer properly portable.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/929code cleanup for searchable surfaces2018-12-21T18:06:09ZMark OLESENcode cleanup for searchable surfacesIncrease strictness of dictionary inputs. Documentation, conveniences.Increase strictness of dictionary inputs. Documentation, conveniences.v1812Mark OLESENMark OLESEN