Development issueshttps://develop.openfoam.com/groups/Development/-/issues2021-07-06T13:11:43Zhttps://develop.openfoam.com/Development/openfoam/-/issues/962BUG: user specified field not taken into account : vorticity2021-07-06T13:11:43ZPrashant SonakarBUG: user specified field not taken into account : vorticityUser specified velocity field is override by default "U"
can we use following instead?
```
fieldExpression(name, runTime, dict, dict.lookupOrDefault<word>("U","U"))
```
@andy @mark
cross ref : EP#761User specified velocity field is override by default "U"
can we use following instead?
```
fieldExpression(name, runTime, dict, dict.lookupOrDefault<word>("U","U"))
```
@andy @mark
cross ref : EP#761Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/947tracking does not handle cells with inverted pyramids (it does handle inverte...2021-07-06T13:08:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comtracking does not handle cells with inverted pyramids (it does handle inverted cells with tets)This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.This is a bit extreme. Run motorBike tutorial with
[meshQualityDict](/uploads/7515102677f9410dea436685f611e583/meshQualityDict) to generate illegal (neg pyr vol, negative delta-coefficient) cells.
Now nearWallFields will hang.https://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/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/878basicThermo checks out 'p' upon destruction2021-07-06T13:00:52ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.combasicThermo checks out 'p' upon destructionSee commit 25c741880e. Is there another way?See commit 25c741880e. Is there another way?https://develop.openfoam.com/Development/openfoam/-/issues/874isoSurface on processor case (so not parallel) crashes since asks for patchNe...2021-07-06T13:00:29ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comisoSurface on processor case (so not parallel) crashes since asks for patchNeighbourFieldIf not running parallel should just use patchInternalField? Problem is that it also uses this routine to generate coordinates which then would be on top of each other.
See isoSurface::adaptPatchFields in sampling/surface/isoSurface/isoS...If not running parallel should just use patchInternalField? Problem is that it also uses this routine to generate coordinates which then would be on top of each other.
See isoSurface::adaptPatchFields in sampling/surface/isoSurface/isoSurfaceTemplates.Chttps://develop.openfoam.com/Development/openfoam/-/issues/872prescribed rotation restraint2021-07-06T12:58:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprescribed rotation restraintThe restraint currently
- does not use time step
- diverges if not underrelaxed
Ideas:
- under relax applied momentum
- do multiple iterations of motion system (nIter)The restraint currently
- does not use time step
- diverges if not underrelaxed
Ideas:
- under relax applied momentum
- do multiple iterations of motion system (nIter)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/839collated fileHandler writes to processor0/../postProcessing which create proc...2021-07-06T12:53:44ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcollated fileHandler writes to processor0/../postProcessing which create processor0 directoryEverywhere it uses (in parallel)
time().path()/".."
it should use
time().rootPath()/time().globalCaseName()
This will avoid the processor0/..
E.g. streamLineBase.C, writeFile.C
```
cd $FOAM_SRC
git grep '"postProcessing"'
```Everywhere it uses (in parallel)
time().path()/".."
it should use
time().rootPath()/time().globalCaseName()
This will avoid the processor0/..
E.g. streamLineBase.C, writeFile.C
```
cd $FOAM_SRC
git grep '"postProcessing"'
```https://develop.openfoam.com/Development/openfoam/-/issues/814snappyHexMesh under valgrind reports lots of uninitialised memory2021-07-06T12:52:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh under valgrind reports lots of uninitialised memory(unfinished) With 2a4ddaa9c6b0190e46493280d1f96218d3f242dd:
[processor0.log](/uploads/2bd561adf7957a5fd78a82a657f46fbb/processor0.log)
(unfinished) Under 1712:
[processor0.log](/uploads/1cd1f03b2b518904f4db9ca22f234ddf/processor0.log)(unfinished) With 2a4ddaa9c6b0190e46493280d1f96218d3f242dd:
[processor0.log](/uploads/2bd561adf7957a5fd78a82a657f46fbb/processor0.log)
(unfinished) Under 1712:
[processor0.log](/uploads/1cd1f03b2b518904f4db9ca22f234ddf/processor0.log)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/790BUG: singleCellFvMesh does not support disconnected regions (i.e. only does o...2021-07-06T12:34:35ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comBUG: singleCellFvMesh does not support disconnected regions (i.e. only does one cell)Not tested.Not tested.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/789BUG: distributedTriSurfaceMesh written to processor*/0/triSurface/2021-07-06T12:34:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comBUG: distributedTriSurfaceMesh written to processor*/0/triSurface/Runnning with distributedTriSurfaceMesh:
- runParallel surfaceRedistributePar independent
- rmpirun -np 6 snappyHexMesh -overwrite -parallel
and at end of run I discovered triSurface/ inside the 0/ folders. Don't know which one did it.Runnning with distributedTriSurfaceMesh:
- runParallel surfaceRedistributePar independent
- rmpirun -np 6 snappyHexMesh -overwrite -parallel
and at end of run I discovered triSurface/ inside the 0/ folders. Don't know which one did it.https://develop.openfoam.com/Development/openfoam/-/issues/768redistributePar does not do DimensionedFields2021-07-06T12:29:16ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comredistributePar does not do DimensionedFieldsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/564mismatch in send/receive sizes of int32/int642021-07-06T12:05:23ZMark OLESENmismatch in send/receive sizes of int32/int64I think the root cause for #505 could be how ints are being sent/received.
For example, an int32_t is sent with a LABEL tag and is 4 bytes. But a LABEL is received in UIPstream as a `label` and could be 32 or 64-bits (depending on WM_LAB...I think the root cause for #505 could be how ints are being sent/received.
For example, an int32_t is sent with a LABEL tag and is 4 bytes. But a LABEL is received in UIPstream as a `label` and could be 32 or 64-bits (depending on WM_LABEL_SIZE). It would seem to be the same for int64, but we probably haven't been sending those about too much in that form.
@andy @MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/756snappyHexMesh does not refine surface when geometry is small relative to doma...2021-07-06T11:51:35ZAdminsnappyHexMesh does not refine surface when geometry is small relative to domain sizeThis is occurring in 2.4.0 (2.4.0-dcea1e13ff76) as well as 1712.
This never occurs on our automotive cases, but only when we are building very coarse test cases to upload here. We have a volume refinement region of 16mm (refine level 6)...This is occurring in 2.4.0 (2.4.0-dcea1e13ff76) as well as 1712.
This never occurs on our automotive cases, but only when we are building very coarse test cases to upload here. We have a volume refinement region of 16mm (refine level 6) around a simple box and wheel geometry (image below from ANSA), on which we specify surface refinements of 8 and 4mm (levels 7 and 8). For some reason, these surface refinements never occur, with all surfaces only reaching 16mm (level 6) mesh size.
Only after adding more complex/larger geometry does the refinement occur. Not a huge problem as our standard cases are very large and complex, but for sending cases for bug reports, it would be nice to figure out the cause so that our test cases can be smaller :-) Not sure if the geometry being refined is considered "too small" relative to the domain size to be refined?
The case on which this is occurring is attached, all you would need to do is run snappyHexMesh.[test_case_refinement_issue_A_00020.zip](/uploads/39953de0d58b345eb357c6037d2192ab/test_case_refinement_issue_A_00020.zip)
![geom_image](/uploads/8562ebd0c151be532e2566dd424dd337/geom_image.png)
\## Reattaching the author to the issue ticket: @aerogt3 ##https://develop.openfoam.com/Development/openfoam/-/issues/747Additional time control to functionObjects2021-07-06T11:50:37ZAdminAdditional time control to functionObjectsHi,
I am missing a flavour of time control in the function objects, namely an approximate output interval. For some of the applications that I am running, it is restrictive to use adjustableRunTime, because it affects the execution too ...Hi,
I am missing a flavour of time control in the function objects, namely an approximate output interval. For some of the applications that I am running, it is restrictive to use adjustableRunTime, because it affects the execution too much and the time steps become integer ratios of the output interval, however, the timeStep output provides too much data. Often, I do not care that the output time axis is non-equidistant.
I have added a new flavour which I call "approximateFixedInterval" and it simply outputs the sampling, if the time is greater than or equal to an integer times the output interval (the integer being larger than the one at the previous output time). Could the addition be adopted (perhaps with a nicer name) in the next release? The required modifications to functionObjects/timeControl/timeControl.[C,H] is attached to this report.
Thank you
Niels
P.S. I know that it is not really an issue, but it seemed to be the only way of making a request.
[timeControl.H](/uploads/c49e31d1d8fda3eb9662f68ed05132b3/timeControl.H)
[timeControl.C](/uploads/f28679a18ddd72a438b6b5c6615dfd63/timeControl.C)
\## Reattaching the author to the issue ticket: @ngj ##https://develop.openfoam.com/Development/openfoam/-/issues/741AMR in interDyMFoam with CrankNicolson is buggy2021-07-06T11:49:38ZAdminAMR in interDyMFoam with CrankNicolson is buggyWhen using ddtSchemes "CrankNicolson 0.9" with AMR (dynamicRefineFvMesh), the solution does not make sense. Only the ddtSchemes "Euler" works fine.
A test case can be provided on demand.
Some hints below (these suggestions might not ...When using ddtSchemes "CrankNicolson 0.9" with AMR (dynamicRefineFvMesh), the solution does not make sense. Only the ddtSchemes "Euler" works fine.
A test case can be provided on demand.
Some hints below (these suggestions might not be right !!)
==========================================================
The problem might be linked to applications/solvers/multiphase/VoF/alphaEqn.H where there are these lines :
` 55 // Set the time blending factor, 1 for Euler
56 scalar cnCoeff = 1.0/(1.0 + ocCoeff);
57
[...]
91 tmp<surfaceScalarField> phiCN(phi);
92
93 // Calculate the Crank-Nicolson off-centred volumetric flux
94 if (ocCoeff > 0)
95 {
96 phiCN = cnCoeff*phi + (1.0 - cnCoeff)*phi.oldTime();
97 }
`
where ocCoeff seems to be the CrankNicolson coefficient entered by the user in the fvSchemes (e.g. 0.9).
The line 96 initializes phiCN with a linear combination of phi and phi.oldTime.
But, phi and phi.oldTime might correspond to a different number of mesh faces because of the AMR.
\#\# Reattaching the author to the issue ticket: @Lionel.Gamet \#\#https://develop.openfoam.com/Development/openfoam/-/issues/736oversetInterpolation method trakingInverseDistance is not working2021-07-06T11:45:55ZAdminoversetInterpolation method trakingInverseDistance is not workingHi, I am trying to run the overset solvers using the trakingInverseDistance method, but it seems that the method does not work. Just try to run the cylinder case using overPimpleDyMFoam and you will be able to reproduce the issue.
jg
...Hi, I am trying to run the overset solvers using the trakingInverseDistance method, but it seems that the method does not work. Just try to run the cylinder case using overPimpleDyMFoam and you will be able to reproduce the issue.
jg
\## Reattaching the author to the issue ticket: @jeogi ##https://develop.openfoam.com/Development/openfoam/-/issues/723Function1 missing Integrate function definition2021-07-06T11:44:45ZMatej FormanFunction1 missing Integrate function definitionOnly few functions from **Function1** has function **Integrate** implemented
(*table, CSV table, Polynomial and Zero/One*).
Those without the Integrate function definition cannot be used to specify the **motion function** for DyM.
Woul...Only few functions from **Function1** has function **Integrate** implemented
(*table, CSV table, Polynomial and Zero/One*).
Those without the Integrate function definition cannot be used to specify the **motion function** for DyM.
Would make sense to add the definition to others as well.https://develop.openfoam.com/Development/openfoam/-/issues/669reduce verbosity for decomposition methods2021-07-06T11:41:56ZMark OLESENreduce verbosity for decomposition methodsAs reported by @Prashant, causes unnecessarily noisy output and can be confused with SHM imbalance.As reported by @Prashant, causes unnecessarily noisy output and can be confused with SHM imbalance.v1806Mark OLESENMark OLESEN