Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-12-21T15:59:45Zhttps://develop.openfoam.com/Development/openfoam/-/issues/678fftw compile problem in single-precision2017-12-21T15:59:45ZMark OLESENfftw compile problem in single-precisionv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/672regression on arglist handling2017-12-20T11:09:34ZMark OLESENregression on arglist handlingreported by @Sergio for reconstructPar - I'm on it
@andy @Prashantreported by @Sergio for reconstructPar - I'm on it
@andy @Prashantv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/661surfaceFieldValue with faceZone restricted to boundary faces2017-12-20T09:40:03ZMark OLESENsurfaceFieldValue with faceZone restricted to boundary facesWas discussing this with @landmann - any reason not to simply use a owner/neighbour average value for internal faces?
@andy, @MattijsWas discussing this with @landmann - any reason not to simply use a owner/neighbour average value for internal faces?
@andy, @MattijsMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/628Crash when directory contains files with spaces or other odd characters in th...2017-12-19T10:50:58ZAdminCrash when directory contains files with spaces or other odd characters in their filenamesparaFoam crash on start with the following error:
`
Created temporary 'run407.OpenFOAM'
I/O : uncollated
fileName::stripInvalid() called for invalid fileName tot6.7kn.0032.jpg
For debug level (= 2) > 1 this is considered fatal
Abo...paraFoam crash on start with the following error:
`
Created temporary 'run407.OpenFOAM'
I/O : uncollated
fileName::stripInvalid() called for invalid fileName tot6.7kn.0032.jpg
For debug level (= 2) > 1 this is considered fatal
Aborted (core dumped)
`
When the current directory contains the files:
`
tot 6.7kn.0000.jpg
tot 6.7kn.0001.jpg
tot 6.7kn.0002.jpg
tot 6.7kn.0003.jpg
etc.
`
(the files where generated by the paraFoam File -> save animation)
When the files are renamed to use underscores, paraFoam starts normally:
`
tot_6.7kn.0000.jpg
tot_6.7kn.0001.jpg
tot_6.7kn.0002.jpg
tot_6.7kn.0003.jpg
etc.
`
When a new animation is made by clicking File -> save animation -> ok
the file name selection dialog correctly merges the image files to: "[+]tot_6.7kn...jpg"
I don't know if this is a recent problem since I normally don't use spaces in filenames. It was found by someone else.
The obvious workaround is to not uses spaces in animation filenames, or deleting old images before starting paraFoam.
`
paraview 5.4.0
OS: Ubuntu 16.04.3 LTS (64 bit)
compiler: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609 [CORRECTED]
build command: ./makeParaView PARAVIEW_QT_VERSION=4
`
I looked at Development/ThirdParty-plus but i'm not sure if paraFoam is a third party build script and neither project readme's mention paraFoam. Please let me know if this issue should be in ThirdParty-plus.
small detail:
I have 63 images, named 0..62. I don't know why the error is for image 32, it could be the order in which the OS lists the file names but (after renaming to underscores) ls -u *.jpg also lists image 32 somewhere in the middle of the file list.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/587mirrorMesh seems to fail in parallel2017-12-19T06:29:50ZAdminmirrorMesh seems to fail in parallelThe below dummy case seems to work fine in serial (./Allrun) but when using mirrorMesh in parallel (./Allrun.parallel) on a decomposed case mirrorMesh gives a warning:
> Mirroring faces on coupled patches destroys the ordering. This mi...The below dummy case seems to work fine in serial (./Allrun) but when using mirrorMesh in parallel (./Allrun.parallel) on a decomposed case mirrorMesh gives a warning:
> Mirroring faces on coupled patches destroys the ordering. This might be fixed by running a dummy createPatch afterwards.
However, running createPatch yields
> ***Inconsistent patches across processors, processor 0 has patch names:
and then it runs forever.
If the parallel option is given I would think it should work in principal, but I have not been able to get it to work in any parallel case, so I would consider it a bug... Or is there a work around?
Thanks,
Pal
[case.tgz](/uploads/3943f1c356bef25aca1c341cdf6abb55/case.tgz)https://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/204Simplify, cleanup mesh conversion infrastructure2017-12-18T23:19:31ZMark OLESENSimplify, cleanup mesh conversion infrastructureWill continue for 1706 as wellWill continue for 1706 as wellVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/429Support dictionary scoping as lvalue2017-12-18T23:19:00ZMark OLESENSupport dictionary scoping as lvalueCurrently can use `${:subdict.name}` as rvalue substitution - using the `:` to denote an absolute location, but it is not possible to use this type of notation as a lvalue. For example `:subdict.name` as a name, since `:` is a punctuatio...Currently can use `${:subdict.name}` as rvalue substitution - using the `:` to denote an absolute location, but it is not possible to use this type of notation as a lvalue. For example `:subdict.name` as a name, since `:` is a punctuation token. It might be possible to add additional quoting etc, but could also make sense just to allow another character for denoting an absolute location. I would propose allowing `^` as an absolute position anchor. This is a one-line change in dictionary::lookupScopedEntryPtr()
if (keyword[0] == ':' || keyword[0] == '^')
Once this is in place, I could rework the `removeEntry` function entry to handle scoped names and eliminate the current restriction:
> The removal only occurs in the current context.
> Removing sub-entries or parent entries is not supported.
@andy @Mattijsv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/558need settings for cray compilers and cray-mpich2017-12-18T23:18:22ZMark OLESENneed settings for cray compilers and cray-mpichMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/294simplify, cleanup surface handling infrastructure2017-12-18T23:17:41ZMark OLESENsimplify, cleanup surface handling infrastructureVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/115Need leaner methods than currently provided by the string-stream classes2017-12-18T23:17:16ZMark OLESENNeed leaner methods than currently provided by the string-stream classesCurrently no simple means to reuse buffer space with the string-stream classes, nor is there a simple means of just counting how many bytes a streamed representation requires.Currently no simple means to reuse buffer space with the string-stream classes, nor is there a simple means of just counting how many bytes a streamed representation requires.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/114Could/should use more compact file output when writing to third-party output.2017-12-18T23:16:54ZMark OLESENCould/should use more compact file output when writing to third-party output.Field output is currently geared to being human readable. The extra spacing and newlines add unnecessary bulk when generating output that should only be read by other programs.Field output is currently geared to being human readable. The extra spacing and newlines add unnecessary bulk when generating output that should only be read by other programs.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/625single precision reading does not handle 1e-39 or lower2017-12-18T23:14:30ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsingle precision reading does not handle 1e-39 or lowerin v1706 this does work - it underflows and truncates to 0.
This is used when generating meshes in double precision but then running with single precision.
Replicate: change on e.g. cavity one of the points in constant/polyMesh/points ...in v1706 this does work - it underflows and truncates to 0.
This is used when generating meshes in double precision but then running with single precision.
Replicate: change on e.g. cavity one of the points in constant/polyMesh/points to
(0.01 1e-39 0)
and run e.g. checkMesh. Will produce error
```
--> FOAM FATAL IO ERROR:
Attempt to get back from bad stream
file: /home/preston2/mattijs/OpenFOAM/OpenFOAM-plus.develop/tutorials/incompressible/icoFoam/cavity/cavity/constant/polyMesh/points at line 23.
From function bool Foam::Istream::getBack(Foam::token&)
in file db/IOstreams/IOstreams/Istream.C at line 56.
FOAM aborting (FOAM_ABORT set)
```Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/608stitchMesh doesn't work with restart2017-12-18T23:12:46ZMark OLESENstitchMesh doesn't work with restartCross-reference EP#313. EP#444Cross-reference EP#313. EP#444v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/645-decomposeParDict invokes MPI2017-12-18T23:12:32ZMark OLESEN-decomposeParDict invokes MPIIt looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel r...It looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel run](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L610)
@andyv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/28no mpicc on cray2017-12-18T10:05:26ZMark OLESENno mpicc on cray- the cray `cc` handles mpi paths- the cray `cc` handles mpi pathsv1712Mark OLESENMark OLESEN2017-12-18https://develop.openfoam.com/Development/openfoam/-/issues/596sampling with plane (cuttingPlane) produces excessive warning messages.2017-12-18T05:23:49ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comsampling with plane (cuttingPlane) produces excessive warning messages.It will print "Did not find closed walk .."
and then a list of 1001 numbers.It will print "Did not find closed walk .."
and then a list of 1001 numbers.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/604BUG: class header incorrect for writeObject - anywrite2017-12-18T05:20:13ZPrashant SonakarBUG: class header incorrect for writeObject - anywriteRefer EP#516Refer EP#516v1712AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/609I/O problem on cluster with multiple nods2017-12-18T05:18:24ZAdminI/O problem on cluster with multiple nodsHi,
I want to report some error connected with the parallel running of fireFoam on salomon cluster (https://docs.it4i.cz/salomon/introduction). When I am using fireFoam (10M of cells) in parallel mode on one node everything is OK. But w...Hi,
I want to report some error connected with the parallel running of fireFoam on salomon cluster (https://docs.it4i.cz/salomon/introduction). When I am using fireFoam (10M of cells) in parallel mode on one node everything is OK. But when I try to run the same case on multiple nodes I get following error
[288] --> FOAM FATAL IO ERROR:
[288] error in IOstream "IOstream" for operation Foam::Istream &Foam::operator>>(Foam::Istream &, Foam::List<T> &) [with T = Foam::Vector<double>]
[288]
[288] file: IOstream at line 0.
[288]
[288] From function void Foam::IOstream::fatalCheck(const char *) const
[288] in file db/IOstreams/IOstreams/IOstream.C at line 109.
[288]
FOAM parallel run exiting
[288]
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 288
The error message usually depends on number of nodes. I am using OpenFOAM-v1706 translated with intel compiler 2017 and intel mpi library.
I want to ask you if you have met similar error.
With regards
Vojtech Betakhttps://develop.openfoam.com/Development/openfoam/-/issues/626restart snappyHexMesh not possible after snapping2017-12-18T05:15:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrestart snappyHexMesh not possible after snappingshm insists on running at least one iteration of e.g. interface refinement so if you are running shm with patch-face merging (= changes hexes into other shapes) it might crash if this triggers refinement of those cells.shm insists on running at least one iteration of e.g. interface refinement so if you are running shm with patch-face merging (= changes hexes into other shapes) it might crash if this triggers refinement of those cells.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.com