Development issueshttps://develop.openfoam.com/groups/Development/-/issues2018-07-13T10:22:40Zhttps://develop.openfoam.com/Development/openfoam/-/issues/934Wrong sign in documentation of p_rgh2018-07-13T10:22:40ZAdminWrong sign in documentation of p_rghIn the documentation of the "p_rgh" the sign is wrong in some of the equations. All terms in the equations below the sentence "After the following substititions" should be negative in https://www.openfoam.com/documentation/cpp-guide/html...In the documentation of the "p_rgh" the sign is wrong in some of the equations. All terms in the equations below the sentence "After the following substititions" should be negative in https://www.openfoam.com/documentation/cpp-guide/html/guide-applications-solvers-variable-transform-p-rgh.html
In the second to last equation, the last term g*h*grad(rho) should be negative too. Compare for example with this:
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/solvers/heatTransfer/buoyantSimpleFoam/UEqn.H#L28https://develop.openfoam.com/Development/openfoam/-/issues/936coded functionObject ignores codeInclude and localCode sections2018-07-12T13:34:19ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comcoded functionObject ignores codeInclude and localCode sectionsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/ThirdParty-common/-/issues/38script error (makeOPENMPI, v1806)2018-07-05T12:13:02Zsariew8script error (makeOPENMPI, v1806)hi developer!
In $FOAM_ETC/bashrc, i changed L85 from 'SYSTEMOPENMPI' to 'OPENMPI'.
run the script makeOPENMPI but my term said the below
./makeOPENMPI: 60: /home/sariew9/OpenFOAM/OpenFOAM-v1806/etc/config.sh/mpi: _foamEtc: not found
...hi developer!
In $FOAM_ETC/bashrc, i changed L85 from 'SYSTEMOPENMPI' to 'OPENMPI'.
run the script makeOPENMPI but my term said the below
./makeOPENMPI: 60: /home/sariew9/OpenFOAM/OpenFOAM-v1806/etc/config.sh/mpi: _foamEtc: not found
What is the problem?
(under the ubuntu14.04LTS)Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/807processorField FO cannot be used with 'postProcess -func'2018-07-04T10:47:28ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprocessorField FO cannot be used with 'postProcess -func'Put attached
[processorField](/uploads/88917ae3ececefb3629b9dc576537eb3/processorField)
in etc/caseDicts/postProcessing/fields/processorField and you can do
```
mpirun -np 2 postProcess -func processorField -parallel
```
Ok?
Put attached
[processorField](/uploads/88917ae3ececefb3629b9dc576537eb3/processorField)
in etc/caseDicts/postProcessing/fields/processorField and you can do
```
mpirun -np 2 postProcess -func processorField -parallel
```
Ok?
https://develop.openfoam.com/Development/openfoam/-/issues/846BUG: redistributePar hangs with develop-pre-release2018-07-04T10:46:52ZPrashant SonakarBUG: redistributePar hangs with develop-pre-releasesteps to reproduce:
Case - motorbike
after snappyHexMesh is completed, try redistributing mesh using 6 CPUs
works in develop.
@mark @Mattijssteps to reproduce:
Case - motorbike
after snappyHexMesh is completed, try redistributing mesh using 6 CPUs
works in develop.
@mark @MattijsMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/852Feature: avoid meshing in given arbitrary region2018-07-04T10:46:04ZPrashant SonakarFeature: avoid meshing in given arbitrary regionRefer : EP#648
- capability to avoid meshing in given closed domain. this can help to use wrapped meshes to avoid leakRefer : EP#648
- capability to avoid meshing in given closed domain. this can help to use wrapped meshes to avoid leakMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/864refineWallLayer -useSet incorrect2018-07-04T10:45:24ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrefineWallLayer -useSet incorrectrefineWallLayer -useSet should limit the refinement to the specified set. Instead it does the opposite.refineWallLayer -useSet should limit the refinement to the specified set. Instead it does the opposite.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://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/703primitiveMesh cellEdges,cellPoints use same labelHashSet2018-07-04T09:18:21ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprimitiveMesh cellEdges,cellPoints use same labelHashSetHelper functions to calculate cellEdges, cellPoints use a DynamicList<label>& for the final result and a labelHashSet for intermediate calculations. It does not make sense to expose one but not the other - this leads to overwrites if bot...Helper functions to calculate cellEdges, cellPoints use a DynamicList<label>& for the final result and a labelHashSet for intermediate calculations. It does not make sense to expose one but not the other - this leads to overwrites if both are used.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/368OpenFOAMĀ® User Upgrade Guide - Missing entries2018-07-04T09:07:03ZAdminOpenFOAMĀ® User Upgrade Guide - Missing entriesI know that this page is still being written: http://openfoam.com/documentation/user-upgrade-guide.php - but I've stumbled upon an _annoying_ situation which lead me to report it now, before you guys forget to document it ;)
Utility u...I know that this page is still being written: http://openfoam.com/documentation/user-upgrade-guide.php - but I've stumbled upon an _annoying_ situation which lead me to report it now, before you guys forget to document it ;)
Utility updates
============
* `changeDictionaryDict` no longer needs the `dictionaryReplacement`master block. In v1606+ it was for example:
```
dictionaryReplacement
{
U
{
internalField uniform (0.001 0 0);
}
}
```
As of v1612+, it's simply:
```
U
{
internalField uniform (0.001 0 0);
}
```AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/447Lagrangian: problematic tracking with dynamic meshes2018-07-03T10:45:44ZAdminLagrangian: problematic tracking with dynamic meshesWhen using a dynamic mesh solver, the tracking of a particle may be wrong: the particle may not cross an internal face when it is moving parallel to other one. Particle rescues are not enough.
I attach a solver "dMeshSprayFoam" (based...When using a dynamic mesh solver, the tracking of a particle may be wrong: the particle may not cross an internal face when it is moving parallel to other one. Particle rescues are not enough.
I attach a solver "dMeshSprayFoam" (based on sprayDyMFoam but it only updates the mesh and evolved the particles) and a simple case named "EjemploMM". I also attach a video which shows the particle tracking problem.
After investigating the problem I found that it starts in line 175 of particleI.H: "tetPointRef tet00 = tetIs.oldTet(mesh_)". This tetrahedron has a problem in its first point which is an oldCellCenter calculated in line 89 of tetIndicesI.H.
I think that there is an issue with the memory reference of this point.
[ProblematicTracking.tar.gz](/uploads/72931680ec544f389a19e302882321a9/ProblematicTracking.tar.gz)![Injection](/uploads/2b61edcd19ff3b30d5d5b63fb9c09e82/Injection.ogv)https://develop.openfoam.com/Development/openfoam/-/issues/489sphereDrop testcase; -postProcess option for time list2018-07-03T10:43:48ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsphereDrop testcase; -postProcess option for time listRunning:
1) compressibleInterDyMFoam -postProcess -time 0.003
This works
2) compressibleInterDyMFoam -postProcess
This crashes at time 0.0003
Something does not get updated in looping over the time ('Reading thermophysical propertie...Running:
1) compressibleInterDyMFoam -postProcess -time 0.003
This works
2) compressibleInterDyMFoam -postProcess
This crashes at time 0.0003
Something does not get updated in looping over the time ('Reading thermophysical properties')? Attached both files.[log.compressibleInterDyMFoam_postProcess2](/uploads/89cc9fdfa1bb219aba2764f7471ca788/log.compressibleInterDyMFoam_postProcess2)[log.compressibleInterDyMFoam_postProcess1](/uploads/1f13654600e4b3fab85c6eb268ff5e59/log.compressibleInterDyMFoam_postProcess1)https://develop.openfoam.com/Development/openfoam/-/issues/469DTCHull fails on various number of domains in parallel2018-07-03T10:43:06ZMatej FormanDTCHull fails on various number of domains in parallel$FOAM_TUTORIALS/multiphase/interDyMFoam/ras/DTCHull run on centOS (vanilla 1612+ compiled with all default options).
runs fine on 16 and 32 CPUs
fails on 4 and 8 CPUs.
case on 4CPUs on k growing out of bounds:
[log_interDyMFoam_4](/u...$FOAM_TUTORIALS/multiphase/interDyMFoam/ras/DTCHull run on centOS (vanilla 1612+ compiled with all default options).
runs fine on 16 and 32 CPUs
fails on 4 and 8 CPUs.
case on 4CPUs on k growing out of bounds:
[log_interDyMFoam_4](/uploads/f6e2af364a76f0f11ab862f95e658e77/log_interDyMFoam_4)
case on 8 CPUs suddenly with SigSev on pressure equation.
[log_interDyMFoam_8](/uploads/49d6b19325216b4a30686d11081d8952/log_interDyMFoam_8)
See logs attached.Prashant SonakarPrashant Sonakarhttps://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/749potential memory leak with HashPtrTable2018-07-03T05:52:29ZMark OLESENpotential memory leak with HashPtrTableSince the `insert()` method is directly inherited from the underlying HashTable, there is no special treatment for any failure. Eg,
T* ptr = new ...;
table.insert(existingKey, ptr);
Since the insert failed, the ptr becomes unma...Since the `insert()` method is directly inherited from the underlying HashTable, there is no special treatment for any failure. Eg,
T* ptr = new ...;
table.insert(existingKey, ptr);
Since the insert failed, the ptr becomes unmanaged.v1806Mark 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/615rhoCentralDyMFoam with Tadmor scheme crashes on orientedType2018-07-02T16:19:42ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrhoCentralDyMFoam with Tadmor scheme crashes on orientedTypecompressible/rhoCentralFoam/obliqueShock with Tadmor flux scheme crashes.compressible/rhoCentralFoam/obliqueShock with Tadmor flux scheme crashes.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/670bug : refineMesh fails with attached Allrun2018-07-02T16:18:50ZAdminbug : refineMesh fails with attached Allrunerror -
[0] --> FOAM FATAL ERROR:
[0] Cut (77039 18800) on face (9.5246807 -8.8045243 1.7253121) of coupled patch procBoundary0to1 is not consistent with coupled cut (1099 77039)
[0]
[0] From function void Foam::cellCuts::syncProc()...error -
[0] --> FOAM FATAL ERROR:
[0] Cut (77039 18800) on face (9.5246807 -8.8045243 1.7253121) of coupled patch procBoundary0to1 is not consistent with coupled cut (1099 77039)
[0]
[0] From function void Foam::cellCuts::syncProc()
[0] in file meshCut/cellCuts/cellCuts.C at line 256.
[0]
FOAM parallel run exiting
[Allrun](/uploads/cbcf69aba24b5d0f865b0a038e7b4f27/Allrun)
Case - $FOAM_TUTORIALS/mesh/refineMesh/refineFieldDirshttps://develop.openfoam.com/Development/openfoam/-/issues/707BUG: Not function timeVaryingMappedFixedValue patch for compressibleInterFoam2018-07-02T16:18:04ZAdminBUG: Not function timeVaryingMappedFixedValue patch for compressibleInterFoamI'm testing timeVaryingMappedFixedValue using several VOF model solvers. I noticed that this patch does not function in compressibleInterFoam.
If you run one case I uploaded, you know that the alpha.water does not flow at all.
[sample...I'm testing timeVaryingMappedFixedValue using several VOF model solvers. I noticed that this patch does not function in compressibleInterFoam.
If you run one case I uploaded, you know that the alpha.water does not flow at all.
[sampleGood.tar.gz](/uploads/1529b87ee03fbead542e3a26cfd286fa/sampleGood.tar.gz)
[sampleNotGood.tar.gz](/uploads/ee1de4cefa2ba435d2c5f34c10c1e8e5/sampleNotGood.tar.gz)