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/969decomposePar -verbose only works in combination with -dry-run2018-08-09T13:53:06ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdecomposePar -verbose only works in combination with -dry-runhttps://develop.openfoam.com/Development/openfoam/-/issues/993cannot have Function1<spatialVector>2018-09-03T12:18:55ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcannot have Function1<spatialVector>Complains about `pTraits .. nComponents`Complains about `pTraits .. nComponents`https://develop.openfoam.com/Development/openfoam/-/issues/997dynamicMultiMotionSolverFvMesh discussion2018-09-06T09:16:17ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdynamicMultiMotionSolverFvMesh discussion1. only provision is for motion on cellZone, not on cellSet
2. cellZone specification might easily be inconsistent with sub-motion solver (e.g. solidBodyMotionSolver) which looks for a cellZone or cellSet specification itself. (as long a...1. only provision is for motion on cellZone, not on cellSet
2. cellZone specification might easily be inconsistent with sub-motion solver (e.g. solidBodyMotionSolver) which looks for a cellZone or cellSet specification itself. (as long as this selection includes the multimotion cell selection it is ok)
3. output of solidBodyMotion might be confusing: e.g. `applying solid body motion to entire mesh` which then gets truncated by the dynamicMultiMotionSolverhttps://develop.openfoam.com/Development/openfoam/-/issues/999unavailable "timeExample" V&V testcase2023-05-17T15:57:13ZAdminunavailable "timeExample" V&V testcaseThe documentation describes an example of various time schemes (ref. 1) with a link to a V&V testcase, timeExample (ref. 2).
The specific case seem to be unavailable in the repository (when following the link I get error 404: The page c...The documentation describes an example of various time schemes (ref. 1) with a link to a V&V testcase, timeExample (ref. 2).
The specific case seem to be unavailable in the repository (when following the link I get error 404: The page could not be found or you don't have permission to view it.).
References:
1) https://openfoam.com/documentation/cpp-guide/html/guide-schemes-time-example.html
2) https://develop.openfoam.com/development/OpenFOAM-plus/tree/master/tutorials/verificationAndValidation/schemes/timeExample
\## Reattaching the author to the issue ticket: @michele ##v2012Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1005snappyHexMesh cannot refine existing patches2023-06-15T15:57:39ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh cannot refine existing patchessnappyHexMesh can only refine geometry, not existing patches. Would be nice if this was possible. Maybe have a searchableSurface which does the actual intersections on an existing patch?snappyHexMesh can only refine geometry, not existing patches. Would be nice if this was possible. Maybe have a searchableSurface which does the actual intersections on an existing patch?https://develop.openfoam.com/Development/openfoam/-/issues/1014intertia of triangle returns full tensor (instead of symmetric one)2022-04-26T16:11:09ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comintertia of triangle returns full tensor (instead of symmetric one)v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1016Paraview only reading cases with constant2019-12-11T12:31:11ZRoger AlmenarParaview only reading cases with constantHello,
I just came across an interesting case:
1) I create a blockMesh based on latestTime, hence mesh is located under results folder (like in 0.2/polyMesh).
2) I decompose that case. It creates the processorX folders, which contained 0...Hello,
I just came across an interesting case:
1) I create a blockMesh based on latestTime, hence mesh is located under results folder (like in 0.2/polyMesh).
2) I decompose that case. It creates the processorX folders, which contained 0.2/polyMesh but no constant/folders, as there is nothing there.
3) Paraview cannot read the case based on a "decomposed" input, because there are no processorX/constant folders.
The case is actually valid, just that it cannot be opened in Paraview.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/1029hole value zeroing gives problems in overRhoPimpleDyMFoam since solves for rho2021-07-08T20:28:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhole value zeroing gives problems in overRhoPimpleDyMFoam since solves for rhoZero rho gives sigFpe when e.g. calculating nu (mu/rho).Zero rho gives sigFpe when e.g. calculating nu (mu/rho).https://develop.openfoam.com/Development/openfoam/-/issues/1063reference cell issues2018-11-05T12:18:47ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comreference cell issues1) the getRefCellValue does a global distribution even when the reference value is only used on a single processor (or not used at all).
2) For certain bcs (e.g. fixedValue) the needReference() is always the same so this reduction could...1) the getRefCellValue does a global distribution even when the reference value is only used on a single processor (or not used at all).
2) For certain bcs (e.g. fixedValue) the needReference() is always the same so this reduction could be moved out of the simulation loop altogether.
3) in dynamic mesh simulations do we want to recalculate the reference cell? For some moving mesh cases we don't, for some e.g. refinement/unrefinement cases we might want to.https://develop.openfoam.com/Development/openfoam/-/issues/1067Problem with wave boundary conditions2024-03-08T22:57:31ZJohan RoenbyProblem with wave boundary conditionsThe wave boundary conditions are introducing a small fraction of air in the water phase. This is illustrated in the attached video:
![streamFunWaveProblem](/uploads/e4972a4f225032115a5583500e15852c/streamFunWaveProblem.mp4)
which shows...The wave boundary conditions are introducing a small fraction of air in the water phase. This is illustrated in the attached video:
![streamFunWaveProblem](/uploads/e4972a4f225032115a5583500e15852c/streamFunWaveProblem.mp4)
which shows the 0.99 and 0.9999 alpha contours of the $FOAM_TUTORIALS/multiphase/interFoam/laminar/waveExampleStreamFunction case.
The case was run as is.
If run with interIsoFoam instead of interFoam, isoAdvector collects the small amount of air in the water phase into bubbles that rise to the surface. A work around is to run interIsoFoam with surfCellTol = 1e-2 in fvSolution.solvers."alpha.water.*". But really this seems to be a problem with the wave BC's and not with isoAdvector.
A Paraview state file used to generate the movie is attached here: [state2.pvsm](/uploads/0ae150172498bbf215446260ada7e1e5/state2.pvsm)v1812Andrew HeatherAndrew Heatherhttps://develop.openfoam.com/Development/openfoam/-/issues/1089primitiveMesh::cells needed only from wall functions2018-11-21T15:38:46ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprimitiveMesh::cells needed only from wall functionsin simpleFoam only fvMatrix<Type>::setValuesFromList gets the cellList. Could this be rewritten to use face-based addressing and save memory? (but more runtime?)
But postprocessing/tracking needs cells so probably little effect for real...in simpleFoam only fvMatrix<Type>::setValuesFromList gets the cellList. Could this be rewritten to use face-based addressing and save memory? (but more runtime?)
But postprocessing/tracking needs cells so probably little effect for real cases.https://develop.openfoam.com/Development/openfoam/-/issues/1122snappyHexMesh automatic gap level refinement : 'small feature' phase should i...2020-09-10T14:39:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsnappyHexMesh automatic gap level refinement : 'small feature' phase should ignore min levelThe `Small surface feature refinement iteration` only works if minimum gap level is triggered. So if
- the specified min level is > 0
- and the geometry is inside a single cell
it will not do anything (since the initial cell level is zer...The `Small surface feature refinement iteration` only works if minimum gap level is triggered. So if
- the specified min level is > 0
- and the geometry is inside a single cell
it will not do anything (since the initial cell level is zero and never increases).
If we leave this behaviour the problem is that the behaviour depends on whether the geometry is fully inside a cell or does intersect. Which is illogical.
Or we fix and then ideally have a switch to bypass this behaviour (since it can be very slow on large cases). Maybe supply a 'maxIter' parameter for the snappyRefineDriver::smallFeatureRefine.
Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/1126function object properties can only handle a single output2018-12-14T18:18:56ZMark OLESENfunction object properties can only handle a single outputthe sampled surfaces function object can contain several surfaces, but when it only has a single property to save the information. Eg,
Input:
```
plane0
{
type surfaces;
...
surfaces
(
planeA { ... }
...the sampled surfaces function object can contain several surfaces, but when it only has a single property to save the information. Eg,
Input:
```
plane0
{
type surfaces;
...
surfaces
(
planeA { ... }
planeB { ... }
);
```
uniform/functionObjects/functionObjectProperties
```
plane0
{
U
{
file "<case>/postProcessing/plane0/0.03/U_planeB.vtk";
}
}
```
possibly relevant for #1091 @andyv1906https://develop.openfoam.com/Development/openfoam/-/issues/1133cyclic pathes converted into processorCyclic not handled in patch name lookups2018-12-20T14:33:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcyclic pathes converted into processorCyclic not handled in patch name lookupsdecomposePar can split a cyclic into processorCyclics. These then will not be picked up by user patch-selection (e.g. through `polyBoundaryMesh::patchSet`).
Add functionality to e.g. patchSet to support this transparently.decomposePar can split a cyclic into processorCyclics. These then will not be picked up by user patch-selection (e.g. through `polyBoundaryMesh::patchSet`).
Add functionality to e.g. patchSet to support this transparently.https://develop.openfoam.com/Development/openfoam/-/issues/1134sampledSets that sampled mesh points/faces/cells (e.g. reads pointSet, faceSe...2018-12-19T11:46:45ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampledSets that sampled mesh points/faces/cells (e.g. reads pointSet, faceSet, cellSet)Would be quite nice to sample selected mesh elements. We've got cellCentreSet but that samples all cells. There are probes but they only sample a single location.Would be quite nice to sample selected mesh elements. We've got cellCentreSet but that samples all cells. There are probes but they only sample a single location.https://develop.openfoam.com/Development/openfoam/-/issues/1140wmRefresh clears WM_NCOMPPROCS2024-01-15T10:07:55ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwmRefresh clears WM_NCOMPPROCSIf I do a wmRefresh (as advised by ./makeParaview) it resets the WM_NCOMPPROCS so it doesn't build in parallel anymore.If I do a wmRefresh (as advised by ./makeParaview) it resets the WM_NCOMPPROCS so it doesn't build in parallel anymore.https://develop.openfoam.com/Development/openfoam/-/issues/1161BUG: Memory leak when using runtime fieldExpression::grad(U) with cached grad(U)2022-04-26T16:11:08ZAdminBUG: Memory leak when using runtime fieldExpression::grad(U) with cached grad(U)This issue can be reproduced by running any tutorial where grad(U) is both cached in system/fvSolution (for example interFoam/RAS/DTChull) and computed using the fieldExpression:
test
{
functionObjectLibs ("libfieldFunctionObjec...This issue can be reproduced by running any tutorial where grad(U) is both cached in system/fvSolution (for example interFoam/RAS/DTChull) and computed using the fieldExpression:
test
{
functionObjectLibs ("libfieldFunctionObjects.so");
type grad;
field U;
outputControl writeTime;
}
The issue is likely related to line 42 and 51 in src/functionObjects/field/grad/gradTemplates.C
\## Reattaching the author to the issue ticket: @peltonp1 ##v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1168injectionModels: inconsistent keyword: UMag/Umag2022-04-26T16:11:08ZPrashant SonakarinjectionModels: inconsistent keyword: UMag/UmagconeNozzle injection seem to require UMag, while rest models need Umag.coneNozzle injection seem to require UMag, while rest models need Umag.v2206Kutalmış BerçinKutalmış Berçinhttps://develop.openfoam.com/Development/openfoam/-/issues/1187DOCU/ENH: lagrangian utilities2024-01-16T06:05:40ZPrashant SonakarDOCU/ENH: lagrangian utilities- [ ] particleTrack writes to processor0/VTK when run in parallel
- [x] $FOAM_APP/utilities/postProcessing/lagrangian/particleTracks/particleTrackProperties please correct cloudName->cloud
- [ ] ~~$FOAM_APP/utilities/postProcessing/lagra...- [ ] particleTrack writes to processor0/VTK when run in parallel
- [x] $FOAM_APP/utilities/postProcessing/lagrangian/particleTracks/particleTrackProperties please correct cloudName->cloud
- [ ] ~~$FOAM_APP/utilities/postProcessing/lagrangian/steadyParticleTracks/particleTrackDict please correct cloudName->cloud~~
- [ ] change alphaName->alpha in ParticleTrap.H
@andyv2206Kutalmış BerçinKutalmış Berçin