openfoam issueshttps://develop.openfoam.com/Development/openfoam/-/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/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/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/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/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/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/892Incorrect order for 6-component VTK symmTensor2018-07-01T05:46:06ZMark OLESENIncorrect order for 6-component VTK symmTensor| | order | reference |
|----|----|---|
| OpenFOAM | XX, XY, XZ, YY, YZ, ZZ | [SymmTensor] |
| VTK | XX, YY, ZZ, XY, YZ, XZ | [vtkMath::TensorFromSymmetricTensor][vtkMath] |
The reordering is thus `(0 3 5 1 4 2)` in either di...| | order | reference |
|----|----|---|
| OpenFOAM | XX, XY, XZ, YY, YZ, ZZ | [SymmTensor] |
| VTK | XX, YY, ZZ, XY, YZ, XZ | [vtkMath::TensorFromSymmetricTensor][vtkMath] |
The reordering is thus `(0 3 5 1 4 2)` in either direction, or
```
swap(1, 3)
swap(2, 5)
```
[SymmTensor]: https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/src/OpenFOAM/primitives/SymmTensor/SymmTensor.H
[vtkMath]: https://www.vtk.org/doc/nightly/html/classvtkMath.htmlv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/890Style: overset - files2018-11-20T22:24:52ZPrashant SonakarStyle: overset - filesSolvers with corresponding file names:
1) solvers/incompressible/pimpleFoam/overPimpleDyMFoam
- solvers/incompressible/pimpleFoam/overPimpleDyMFoam/overPimpleDyMFoam.C -> OK
2) solvers/incompressible/simpleFoam/overSimpleFoam
- solve...Solvers with corresponding file names:
1) solvers/incompressible/pimpleFoam/overPimpleDyMFoam
- solvers/incompressible/pimpleFoam/overPimpleDyMFoam/overPimpleDyMFoam.C -> OK
2) solvers/incompressible/simpleFoam/overSimpleFoam
- solvers/incompressible/simpleFoam/overSimpleFoam/overSimpleFoam.C -> OK
3) solvers/multiphase/interFoam/overInterDyMFoam
- solvers/multiphase/interFoam/overInterDyMFoam/interDyMFoam.C -> Please check
4) solvers/basic/potentialFoam/overPotentialFoam
- solvers/basic/potentialFoam/overPotentialFoam/potentialFoam.C -> Please check
5) solvers/basic/laplacianFoam/overLaplacianDyMFoam
- solvers/basic/laplacianFoam/overLaplacianDyMFoam/overLaplacianDyMFoam.C -> OK
6) solvers/compressible/rhoPimpleFoam/overRhoPimpleDyMFoam
- solvers/compressible/rhoPimpleFoam/overRhoPimpleDyMFoam/rhoPimpleDyMFoam.C -> Please check
7) solvers/compressible/rhoSimpleFoam/overRhoSimpleFoam
- solvers/compressible/rhoSimpleFoam/overRhoSimpleFoam/rhoSimpleFoam.C-> Please check
@andy @Sergio @Mattijs @markv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/888bad indexing in regionSizeDistribution function object2018-06-20T12:06:29ZMark OLESENbad indexing in regionSizeDistribution function objectnoted by @Prashantnoted by @Prashantv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/885improve consistency of 'normal' methods2019-06-28T09:51:34ZMark OLESENimprove consistency of 'normal' methodsIn various places `normal()` can be a unit normal or an area normal. In places where there can be ambiguity, propose to provide explicit `areaNormal()` or `unitNormal()` methods. In the next version (1812), phase out `normal()` in favour...In various places `normal()` can be a unit normal or an area normal. In places where there can be ambiguity, propose to provide explicit `areaNormal()` or `unitNormal()` methods. In the next version (1812), phase out `normal()` in favour of these and deprecate `normal()`. In following version (1906), mark normal as `= delete` or otherwise tag its usage to finalize changeover.
For the first step, I propose adding these new names, but not yet changing code to use them. This will get them into place for early adopters and also make it easier with bugfixes/backports between 1806 and the 1812-develop.
@Nilsson @johan\_roenbyv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/884access to invalid coordinateRotation after move assignment2018-06-26T05:56:09ZMark OLESENaccess to invalid coordinateRotation after move assignmentThe coordinateSystem move assignment leaves the coordinateRotation undefined. This is OK, and consistent with various move semantics, but the transfer also forces a clear() on the old object. This causes an invalid access to the autoPtr.The coordinateSystem move assignment leaves the coordinateRotation undefined. This is OK, and consistent with various move semantics, but the transfer also forces a clear() on the old object. This causes an invalid access to the autoPtr.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/883major() / minor() conflicts with sys/sysmacros.h2018-06-20T00:04:13ZMark OLESENmajor() / minor() conflicts with sys/sysmacros.hmajor() and minor() are GNU macros in sys/sysmacros.h - generates warning on Ubuntu.major() and minor() are GNU macros in sys/sysmacros.h - generates warning on Ubuntu.v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/868fragile ensight surface reader2018-12-11T10:42:03ZMark OLESENfragile ensight surface readerexpects the following only:
model: 1 xxx.000.mesh
which means that any of the following (correct input) will break it:
model: xxx.000.mesh
model: data/000/geomexpects the following only:
model: 1 xxx.000.mesh
which means that any of the following (correct input) will break it:
model: xxx.000.mesh
model: data/000/geomv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/867Medium Test - 12.06.20182019-12-09T22:18:11ZPrashant SonakarMedium Test - 12.06.2018All cases could be accessed at: /home/alex4/prashant/SUPPORT/ESI/MEDIUM_TEST/tutorials_1806
- [x] DNS/dnsFoam/boxTurb16 - solver crash
- [x] IO/fileHandler/machineA/fileHandler - re-verify if we need `cp -r` while copying constant, line ...All cases could be accessed at: /home/alex4/prashant/SUPPORT/ESI/MEDIUM_TEST/tutorials_1806
- [x] DNS/dnsFoam/boxTurb16 - solver crash
- [x] IO/fileHandler/machineA/fileHandler - re-verify if we need `cp -r` while copying constant, line 36; 90 of Allrun
- [x] combustion/PDRFoam/flamePropagationWithObstacles - solver crash
- [x] mesh/foamyHexMesh/mixerVessel - solver crash
- [x] compressible/rhoSimpleFoam/gasMixing/injectorPipe - solver crash
- [x] compressible/sonicFoam/RAS/nacaAirfoil - solver crash
- [x] incompressible/pimpleFoam/LES/vortexShed - surface noise failed 'expected word error'
- [x] multiphase/compressibleInterFoam/laminar/climbingRod - solver failure
- [x] multiphase/driftFluxFoam/RAS/dahl - solver failure
- [x] multiphase/reactingTwoPhaseEulerFoam/RAS/LBend - solver failure
- [x] multiphase/compressibleInterFoam/laminar/depthCharge2D - solver failure
- [x] multiphase/interFoam/RAS/DTCHullMoving - solver failure
- [ ] ~~multiphase/interFoam/RAS/DTCHullWave - decomposePar failure 'missing entry value'~~ REMOVED
- [x] multiphase/interFoam/RAS/motorBike - rename solver in controlDict_nextWrite
- [x] multiphase/interFoam/laminar/vofToLagrangian/lagrangian* - both cases replace combustionModel type noCombustion to none
@andy @Mattijs @Sergio @markv1806https://develop.openfoam.com/Development/openfoam/-/issues/862segfault: sampling field transfer to triSurfaceMesh (as surfMesh)2018-07-02T09:35:28ZMark OLESENsegfault: sampling field transfer to triSurfaceMesh (as surfMesh)- in surfMeshSampleDiscrete, face/point ownership is transferred to surfMesh, but this means they are not available for discreteSurface when sampling
@Prashant @SonVo- in surfMeshSampleDiscrete, face/point ownership is transferred to surfMesh, but this means they are not available for discreteSurface when sampling
@Prashant @SonVov1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/861residual FO : DebugInfo2018-07-04T10:44:48ZPrashant Sonakarresidual FO : DebugInfoIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @MattijsIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @Mattijsv1806https://develop.openfoam.com/Development/openfoam/-/issues/860foamLog extract min, max, avg2021-07-06T12:57:16ZMark OLESENfoamLog extract min, max, avg- can currently only extract min value (EP 690), and foamLog is not sophisticated enough to handle arbitrary parsing.
- adjust AMI reporting as `min = ... max = ...` instead of `min/max/average = ...` for easier parsing.
@Prashant- can currently only extract min value (EP 690), and foamLog is not sophisticated enough to handle arbitrary parsing.
- adjust AMI reporting as `min = ... max = ...` instead of `min/max/average = ...` for easier parsing.
@Prashantv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/859STYLE: correct syntax in header file of noise.C2019-12-09T22:18:11ZvilfayeauSTYLE: correct syntax in header file of noise.CHi,
Could you update the syntax in the noise.C header file? Headerfile of noise.C and noiseDict should be consistent.
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/utilities/postProcessing/noise/noise...Hi,
Could you update the syntax in the noise.C header file? Headerfile of noise.C and noiseDict should be consistent.
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/utilities/postProcessing/noise/noise.C
`// Input file
inputFile "postProcessing/faceSource1/surface/patch/patch.case";
`
should be
`// Input file
files ( "postProcessing/faceSource1/surface/patch/patch.case");
`
Best,
Sebastienv1806https://develop.openfoam.com/Development/openfoam/-/issues/858swirlFanVelocity2018-06-11T14:48:02ZPrashant SonakarswirlFanVelocityoptional entry rEff is set to zero. Please reconsider division.optional entry rEff is set to zero. Please reconsider division.v1806Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/856Unit tests: 06-06-20182018-07-02T05:02:01ZPrashant SonakarUnit tests: 06-06-2018- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/rea...- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/reactingParcelFoam/verticalChannelLTS : solver exit with maxIter 100
unconfirmed completions
- compressible/rhoSimpleFoam/gasMixing/injectorPipe: solver
cases run at /home/alex2/prashant/OpenFOAM/OpenFOAM-plus.feature-xxx/tutorialsTest
@andy @Mattijs @mark @Sergiov1806