Development issueshttps://develop.openfoam.com/groups/Development/-/issues2019-06-28T09:51:21Zhttps://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/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/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/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/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/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/908Possible issue with reactionI.H2018-06-26T12:36:39ZMark OLESENPossible issue with reactionI.HCompile problem fedora28 reported
https://www.cfd-online.com/Forums/openfoam-installation/203125-openfoam-1712-build-error.htmlCompile problem fedora28 reported
https://www.cfd-online.com/Forums/openfoam-installation/203125-openfoam-1712-build-error.htmlMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/907provide separate source tar files for modules2021-07-06T13:05:03ZMark OLESENprovide separate source tar files for modulesSimone @sbna is working with packaging our catalyst module with spack. It is very useful to have the the catalyst adaptor reside outside of the main OpenFOAM source tree and thus be able to combine one particular installation of OpenFOAM...Simone @sbna is working with packaging our catalyst module with spack. It is very useful to have the the catalyst adaptor reside outside of the main OpenFOAM source tree and thus be able to combine one particular installation of OpenFOAM with various ParaView and Catalyst flavours (mpi, mesa, gpu rendering, etc).
For this to package smoothly in spack, EasyBuilder etc, there should be a downloadable tar file to be used when packaging.
I think that Modules-v1806.tar.gz with the identical contents of the `modules/` tree (avalanche, catalyst, cfmesh), would be quite useful. I think that is OK to bundle the three together and have the packager decide which sub-directory is relevant.
@Pawanv1806Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/906AMIInterpolation uses non-assigned magSf in parallel2018-07-03T10:40:07ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comAMIInterpolation uses non-assigned magSf in parallelMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/905solid thermo (heSolidThermo) initialisation of psi, mu2020-01-08T14:41:37ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsolid thermo (heSolidThermo) initialisation of psi, muheSolidThermo does not initialise or update the psi,mu of the base class (rhoThermo). This shows up when calculating turbulence for multi-phase systems (e.g. icoReactingMultiPhaseInterFoam) when accessing divDevRhoReff.
The underlying p...heSolidThermo does not initialise or update the psi,mu of the base class (rhoThermo). This shows up when calculating turbulence for multi-phase systems (e.g. icoReactingMultiPhaseInterFoam) when accessing divDevRhoReff.
The underlying problem is that the solid transportModels do not implement mu(), psi() functionality. See #856. The current solution is to explicitly set the mu, psi to 0 in the multi-phase system constructor.Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/904hard-coded name separators in foamCreateVideo2018-07-02T09:39:22ZMark OLESENhard-coded name separators in foamCreateVideo- looks for things like `image.0001.png`, but default Catalyst scripts will generate `image_0001.png`, and with additional amounts of padding (eg, `pressure_00020056.png`) which are needed when generating a higher time resolution visuali...- looks for things like `image.0001.png`, but default Catalyst scripts will generate `image_0001.png`, and with additional amounts of padding (eg, `pressure_00020056.png`) which are needed when generating a higher time resolution visualization.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/903ensight case with multiple clouds2021-07-06T13:18:34ZMark OLESENensight case with multiple cloudsensight only supports a single set of measured values. Outputting multiple clouds for a case is an error.
Could remedy by only emitting the first cloud and either ignore any others or creating separate case files for each of them.
The ...ensight only supports a single set of measured values. Outputting multiple clouds for a case is an error.
Could remedy by only emitting the first cloud and either ignore any others or creating separate case files for each of them.
The only problem with this approach is that we still need a `model:` entry in the case. The mesh bounding box would be a reasonable thing to generate.
@graupsv1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/902BUG: foamToEnsight replaces ":" with "_" for Lagrangian file names but retain...2020-06-22T15:13:04ZAdminBUG: foamToEnsight replaces ":" with "_" for Lagrangian file names but retains ":" in .case filefoamToEnsight replaces ":" with "_" when writing out Lagrangian file names. However, the .case file retains the ":" when listing the filenames for ensight to read. This results in a file read error when reading into EnSight.
[simple_spr...foamToEnsight replaces ":" with "_" when writing out Lagrangian file names. However, the .case file retains the ":" when listing the filenames for ensight to read. This results in a file read error when reading into EnSight.
[simple_spray_steady_good.case](/uploads/e5f3eb73f8b14dff94bcb333b019e50b/simple_spray_steady_good.case)
\#\# Reattaching the author to the issue ticket: @graups \#\#Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/901system command swallows first argument2018-06-22T14:14:19ZMark OLESENsystem command swallows first argumentThe multi-argument version of Foam::system() inadvertently swallows the first argument.
- Affects dumping of rays (uses objToVTK)
- doxygen browser
- dynamic code (swallows the leading `-s`, meaning that there is additional verbosity)The multi-argument version of Foam::system() inadvertently swallows the first argument.
- Affects dumping of rays (uses objToVTK)
- doxygen browser
- dynamic code (swallows the leading `-s`, meaning that there is additional verbosity)v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/900cleanCase deletes blockMeshDict2018-07-01T05:46:07ZJohan RoenbycleanCase deletes blockMeshDictMany OpenFOAM users still use older OF version. When they eventually try to port their older OpenFOAM cases to newer OpenFOAM versions it can be quite annoying that the cleanCase function in bin/tools/CleanFunctions deletes the constant/...Many OpenFOAM users still use older OF version. When they eventually try to port their older OpenFOAM cases to newer OpenFOAM versions it can be quite annoying that the cleanCase function in bin/tools/CleanFunctions deletes the constant/polyMesh, where their blockMeshDict may still reside.
I suggest introducing a check in cleanCase, so that it moves an existing blockMeshDict (or any *Dict in polyMesh for that matter) from constant/polyMesh to the system folder before deleting polyMesh.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/899Allrun-*2021-07-06T13:04:11ZPrashant SonakarAllrun-*We have following with Allrun-*
- ./incompressible/icoFoam/cavityMappingTest/Allrun-parallel
- ./incompressible/pimpleFoam/RAS/oscillatingInletACMI2D/Allrun-parallel
- ./multiphase/interIsoFoam/damBreak/Allrun-parallel
- ./lagrangian/coa...We have following with Allrun-*
- ./incompressible/icoFoam/cavityMappingTest/Allrun-parallel
- ./incompressible/pimpleFoam/RAS/oscillatingInletACMI2D/Allrun-parallel
- ./multiphase/interIsoFoam/damBreak/Allrun-parallel
- ./lagrangian/coalChemistryFoam/simplifiedSiwek/Allrun-parallel
- ./lagrangian/simpleReactingParcelFoam/verticalChannel/Allrun-parallel
- ./lagrangian/reactingParcelFoam/hotBoxes/Allrun-parallel
- ./mesh/foamyHexMesh/mixerVessel/Allrun-`pre`
- ./mesh/foamyHexMesh/mixerVessel/Allrun-`simulation`
- ./mesh/foamyHexMesh/blob/Allrun-parallel
- ./mesh/foamyHexMesh/flange/Allrun-parallel
- ./mesh/stitchMesh/simple-cube1/Allrun-`args`
- ./mesh/foamyQuadMesh/OpenCFD/Allrun-`rhoCentralFoam`
- ./heatTransfer/chtMultiRegionSimpleFoam/heatExchanger/Allrun-parallel
- ./heatTransfer/chtMultiRegionSimpleFoam/jouleHeatingSolid/Allrun-parallel
- ./heatTransfer/chtMultiRegionSimpleFoam/multiRegionHeaterRadiation/Allrun-parallel
- ./heatTransfer/chtMultiRegionFoam/windshieldCondensation/Allrun-parallel
- ./heatTransfer/chtMultiRegionFoam/snappyMultiRegionHeater/Allrun-`serial`
- ./heatTransfer/chtMultiRegionFoam/snappyMultiRegionHeater/Allrun-parallel
- ./heatTransfer/chtMultiRegionFoam/windshieldDefrost/Allrun-parallel
- ./heatTransfer/chtMultiRegionFoam/externalSolarLoad/Allrun-parallel
- ./finiteArea/sphereSurfactantFoam/sphereTransport/Allrun-parallel
And many formats with Allrun.*
While the foamRunTutorials contain call to
- Allrun
- Alltest
- Allrun-parallel
- Allrun-optional (no such file nor doing anything at the moment!)
Can we formalize the names and give priority to Allrun-parallel than Allrun (serial version) ?
@andy @Mattijs @mark @Sergiohttps://develop.openfoam.com/Development/openfoam/-/issues/898Adjust derived fields for incompressible2018-07-02T09:33:34ZMark OLESENAdjust derived fields for incompressibleAs tagged on EP645 by @SonVo and discussed with @Prashant - could/should have a `rhoRef` for derived fields in the surfMesh sampler so that `pTotal` and `rhoU` have more physical meanings.As tagged on EP645 by @SonVo and discussed with @Prashant - could/should have a `rhoRef` for derived fields in the surfMesh sampler so that `pTotal` and `rhoU` have more physical meanings.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/897floating point exception in external routines can kill OpenFOAM2018-07-20T13:59:34ZMark OLESENfloating point exception in external routines can kill OpenFOAMAlready needed a workaround in runTimePostProcessing to avoid this issue. Now found that some bad catalyst pipelines can also trigger floating point exceptions. For example, extracting a contour from a field that does not yet exist.
The ...Already needed a workaround in runTimePostProcessing to avoid this issue. Now found that some bad catalyst pipelines can also trigger floating point exceptions. For example, extracting a contour from a field that does not yet exist.
The sigFpe trapping cascades this through and ends the OpenFOAM job.
Ideally we'd instead like to ensure that any catalyst failures cannot pull down the simulation.
@acbauer, @sbnaMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/896Prevent removal of .foam cases with cleanCase function2018-07-02T09:33:55ZRoger AlmenarPrevent removal of .foam cases with cleanCase functionRight now, when executing any of the ./Allclean sripts, a cleanCase function is called deleting also any files with extension .foam.
These files are used for ParaView to read OpenFOAM cases, and is quite handy to keep them when debuggin...Right now, when executing any of the ./Allclean sripts, a cleanCase function is called deleting also any files with extension .foam.
These files are used for ParaView to read OpenFOAM cases, and is quite handy to keep them when debugging OpenFOAM runs. Is it possible to prevent the deletion of these files?
I understand ParaFoam creates files .OpenFOAM, but we are talking about .foam files.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/895cellSet labelToCell (and labelToFace, labelToPoint) should check validity2018-07-22T16:58:47ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcellSet labelToCell (and labelToFace, labelToPoint) should check validityThe only manual input for sets (labelToXXX) should check for validity.The only manual input for sets (labelToXXX) should check for validity.