Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-06-29T20:38:03Zhttps://develop.openfoam.com/Development/openfoam/-/issues/498COMP: 64 bit LABEL SIZE fails with segmentation fault2017-06-29T20:38:03ZPrashant SonakarCOMP: 64 bit LABEL SIZE fails with segmentation faultThe compiled binaries fail with "segmentation fault" error.
@MattijsThe compiled binaries fail with "segmentation fault" error.
@MattijsVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/499BUG? tutorials/heatTransfer/chtMultiRegionFoam/externalSolarLoad-parallel2017-06-19T19:43:57ZPrashant SonakarBUG? tutorials/heatTransfer/chtMultiRegionFoam/externalSolarLoad-parallelThe tutorial when tried in parallel failed attached script.
[Allrun](/uploads/135d01d12be71db5fd0b074c3ac48ddc/Allrun)
```
[1]
[1] --> FOAM FATAL IO ERROR:
[1] cannot find file
[1]
[1] file: /hosts/xxx/externalSolarLoad-parallel/proc...The tutorial when tried in parallel failed attached script.
[Allrun](/uploads/135d01d12be71db5fd0b074c3ac48ddc/Allrun)
```
[1]
[1] --> FOAM FATAL IO ERROR:
[1] cannot find file
[1]
[1] file: /hosts/xxx/externalSolarLoad-parallel/processor1/constant/air/mapDist at line 0.
```
@andyVersion v1706Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/500sampling the surface ('triSurfaceMesh') normal component not supported2017-06-29T20:38:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampling the surface ('triSurfaceMesh') normal component not supportedThere is the fieldValues with areaNormalAverage but that uses the regionType's (faceZone, patch) normal.There is the fieldValues with areaNormalAverage but that uses the regionType's (faceZone, patch) normal.Version v1706Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/501COMP: 64 bit label compilation - further updates2017-07-12T04:46:26ZPrashant SonakarCOMP: 64 bit label compilation - further updatesFurther compilation failure at
foamVtkLagrangianWriter.C:103:25: error: call of overloaded 'write(int)' is ambiguous
@markFurther compilation failure at
foamVtkLagrangianWriter.C:103:25: error: call of overloaded 'write(int)' is ambiguous
@markVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/502wallBoundedStreamline not robust for negative tet volume cells2017-06-29T20:38:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comwallBoundedStreamline not robust for negative tet volume cells[cavity.tgz](/uploads/251a2be487061449c069116dcaeb199d/cavity.tgz)
Creates a mesh with a neg-tet cell and attempts wall bounded streamlines.[cavity.tgz](/uploads/251a2be487061449c069116dcaeb199d/cavity.tgz)
Creates a mesh with a neg-tet cell and attempts wall bounded streamlines.Version v1706Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/503DOCU: inconsistent documentation for pressure FO2017-06-19T19:42:59ZPrashant SonakarDOCU: inconsistent documentation for pressure FOHeader file mentions keywords pRef optional with default value = 0.
However, this becomes compulsory with dictLookup entry.
Should either be modified to make it consistent (or state conditions when it is required)?
```
Property | ...Header file mentions keywords pRef optional with default value = 0.
However, this becomes compulsory with dictLookup entry.
Should either be modified to make it consistent (or state conditions when it is required)?
```
Property | Description | Required | Default value
pRef | Reference pressure | for total pressure | 0
pInf | Freestream pressure | for coefficient calculation |
```Version v1706AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/504BUG: failure in case multiphase/overInterDyMFoam/floatingBody/background2017-06-19T19:31:53ZPrashant SonakarBUG: failure in case multiphase/overInterDyMFoam/floatingBody/backgroundAttached log from the case file.[log.overInterDyMFoam](/uploads/e418d3a09bf3fe81967f541f09ac64b0/log.overInterDyMFoam)
@Pawan @SergioAttached log from the case file.[log.overInterDyMFoam](/uploads/e418d3a09bf3fe81967f541f09ac64b0/log.overInterDyMFoam)
@Pawan @SergioVersion v1706Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/505BUG: lagrangian/icoUncoupledKinematicParcelFoam/hopper/hopperInitialState2017-10-30T11:28:59ZPrashant SonakarBUG: lagrangian/icoUncoupledKinematicParcelFoam/hopper/hopperInitialStateThe tutorial fails with
```
Cloud: kinematicCloud injector: model1
Added 3300 new parcels
4 move-collide subCycles
[3]
[3] --> FOAM FATAL IO ERROR:
[3] Expected a '(' while reading VectorSpace<Form, Cmpt, Ncmpts>, found on line...The tutorial fails with
```
Cloud: kinematicCloud injector: model1
Added 3300 new parcels
4 move-collide subCycles
[3]
[3] --> FOAM FATAL IO ERROR:
[3] Expected a '(' while reading VectorSpace<Form, Cmpt, Ncmpts>, found on line 0 an error
```
@SergioVersion v1706AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/507overset incompressible solvers do not set reference cell for pcorr2021-07-06T10:06:01ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comoverset incompressible solvers do not set reference cell for pcorr- they currently analyse on a per overset 'zone' basis
- this should be any disconnected region instead (so also ones resulting from blocked cells)- they currently analyse on a per overset 'zone' basis
- this should be any disconnected region instead (so also ones resulting from blocked cells)Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/508BUG: Failure of multiphase/interDyMFoam/RAS/motorBike case2017-06-28T18:58:49ZPrashant SonakarBUG: Failure of multiphase/interDyMFoam/RAS/motorBike caseCase fails when doing
```
mpirun -np 5 redistributePar -parallel -decompose -latestTime
```Case fails when doing
```
mpirun -np 5 redistributePar -parallel -decompose -latestTime
```Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/509meanMomentumEnergyAndNMols.H bug?2017-06-29T20:38:03ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.commeanMomentumEnergyAndNMols.H bug?src/lagrangian/molecularDynamics/molecule/mdTools/meanMomentumEnergyAndNMols.H:85
const vector& molOmega(inv(molMoI) & mol().pi());src/lagrangian/molecularDynamics/molecule/mdTools/meanMomentumEnergyAndNMols.H:85
const vector& molOmega(inv(molMoI) & mol().pi());Version v1706https://develop.openfoam.com/Development/openfoam/-/issues/510ENH: Add warning/error message when input is incorrect2018-10-05T07:46:48ZPrashant SonakarENH: Add warning/error message when input is incorrectsolver hangs infinitely when input in fvSolution is
```
(U|k|epsilon|omega|f|v2)
```
instead of
```
"(U|k|epsilon|omega|f|v2)"
```
file to replicate on pitzDaily case [fvSolution](/uploads/d61cd6b4a8207555fdab282d49ac6ef2/fvSo...solver hangs infinitely when input in fvSolution is
```
(U|k|epsilon|omega|f|v2)
```
instead of
```
"(U|k|epsilon|omega|f|v2)"
```
file to replicate on pitzDaily case [fvSolution](/uploads/d61cd6b4a8207555fdab282d49ac6ef2/fvSolution)
@Mattijs @markhttps://develop.openfoam.com/Development/openfoam/-/issues/511mesa build failure in Ubuntu162017-06-29T08:14:56ZPawan Ghildiyalmesa build failure in Ubuntu16Hi Mark
I am compiling mesa in bash in Windows.
It has Ubuntu bash with following specification.
It fail at one point . See attached log .
Dstributor ID: Ubuntu.
Description: Ubuntu 16.04.2 LTS.
Release: 16.04 .
C...Hi Mark
I am compiling mesa in bash in Windows.
It has Ubuntu bash with following specification.
It fail at one point . See attached log .
Dstributor ID: Ubuntu.
Description: Ubuntu 16.04.2 LTS.
Release: 16.04 .
Codename: xenial
Some one too faced similar issue and provided work around ,
however I could not understand where to put it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528169Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/16makeParaView and makeVTK possibly assume lib64 for mesa libraries2017-09-28T12:04:04ZMark OLESENmakeParaView and makeVTK possibly assume lib64 for mesa librariesexchange platform https://exchange.openfoam.com/node/398
@Pawan @Prashantexchange platform https://exchange.openfoam.com/node/398
@Pawan @PrashantVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/512cleanup construction selectors2017-07-10T12:42:23ZMark OLESENcleanup construction selectorsCan use `auto` with that hashtable `cfind` for simpler looking code.Can use `auto` with that hashtable `cfind` for simpler looking code.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/513consolidate arch and version strings2017-07-08T09:16:54ZMark OLESENconsolidate arch and version stringsv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/514scale option for all geometry reading2017-12-18T23:20:04ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comscale option for all geometry reading- snappyHexMesh, foamyHexMesh, blockMesh all support scaling geometry upon reading.
- of the surface utilities only:
```
surfaceConvert
surfaceFeatureConvert
surfaceMeshConvert
surfaceMeshConvertTesting
surfaceMeshExport
surfaceMeshImpor...- snappyHexMesh, foamyHexMesh, blockMesh all support scaling geometry upon reading.
- of the surface utilities only:
```
surfaceConvert
surfaceFeatureConvert
surfaceMeshConvert
surfaceMeshConvertTesting
surfaceMeshExport
surfaceMeshImport
surfaceMeshInfo
surfaceTransformPoints
```
support it.
- can we extend all others to support it as well? Especially surfaceFeatureExtract.
- also e.g. BCs (pointDisplacement ones), postprocessingMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/515upgrade from NamedEnum to Enum2017-07-11T13:02:55ZMark OLESENupgrade from NamedEnum to EnumMore flexible and reduces chances of mistakes in the long-termMore flexible and reduces chances of mistakes in the long-termv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/516foamToVTK produces illegal (binary) files2017-07-04T13:08:27ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comfoamToVTK produces illegal (binary) files[fineMesh.tgz](/uploads/ed96068fdeb0d2f606129fdfdf5a321b/fineMesh.tgz)
I did
- lid driven cavity
- in setSet:
cellSet c0 new labelToCell ( 10 12 5)
cellSet c1 new cellToCell c0
cellSet c1 invert
- foamToVTK -cellSet c0
- foamToVTK -cel...[fineMesh.tgz](/uploads/ed96068fdeb0d2f606129fdfdf5a321b/fineMesh.tgz)
I did
- lid driven cavity
- in setSet:
cellSet c0 new labelToCell ( 10 12 5)
cellSet c1 new cellToCell c0
cellSet c1 invert
- foamToVTK -cellSet c0
- foamToVTK -cellSet c1
and VTK/c0_0.vtk is unreadable. c1_0 is fine.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/17improve support for non-system python locations2017-08-03T06:19:28ZMark OLESENimprove support for non-system python locationsMentioned in https://exchange.openfoam.com/node/424
@PrashantMentioned in https://exchange.openfoam.com/node/424
@PrashantMark OLESENMark OLESEN