View Issue Details

IDProjectCategoryView StatusLast Update
0002533OpenFOAMBugpublic2017-04-28 14:23
Reportershildenbrand Assigned Tohenry  
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformHP Z640OSDebianOS Version8.7
Product Versiondev 
Fixed in Versiondev 
Summary0002533: Cases with (new) particle tracking cannot be postprocessed with Paraview
DescriptionParaview can not read the new particle "positions" format. This happens in both cases, when using the Paraview native OpenFOAM reader as well as the Reader provided by OpenFOAM.
Old format was for example

(0.02641281071 -0.02402617481 0.02936163623) 4235

New format is

(0.1674858034 0.4225662228 0.4064526504 0.00349532343) 34844 100245 2

Error message (in case of *.OpenFOAM) is:
--> FOAM FATAL IO ERROR:
Expected a ')' while reading VectorSpace<Form, Cmpt, Ncmpts>, found on line 20 the doubleScalar 0.00349532343

file: /scratch/pc-cae3/shildenbrand/OpenFOAM/run/99_tutorials/lagrangian/reactingParcelFoam/verticalChannel/0.02/lagrangian/reactingCloud1/positions at line 20.

    From function Foam::Istream& Foam::Istream::readEnd(const char*)
    in file db/IOstreams/IOstreams/Istream.C at line 109.

FOAM exiting



Steps To ReproduceRun tutorial lagrangian/reactingParcelFoam/verticalChannel
After Time = 0.02 there are particles present.
TagsLagrangian

Activities

henry

2017-04-28 14:00

manager   ~0008052

I cannot reproduce this issue, the ParaFoam reader uses the Lagrangian library to read the data so should be fully consistent. Note:

    The particle positions file now contains particles' local coordinates
    and topology, rather than the global coordinates and cell. This change
    to the output format is not backwards compatible. Existing cases with
    Lagrangian data will not restart, but they will still run from time
    zero without any modification. This change was necessary in order to
    guarantee that the loaded particle is valid, and therefore
    fundamentally prevent "loss" and "search-failure" type bugs (e.g.,
    2517, 2442, 2286, 1836, 1461, 1341, 1097).

shildenbrand

2017-04-28 14:13

reporter   ~0008053

You are right. Sorry for the report - somehow the compilation of PVReaders has not worked. Starting with Paraview 5.3 this will lead to a problem in the current configuration, however.

Please close the report.

Issue History

Date Modified Username Field Change
2017-04-28 13:49 shildenbrand New Issue
2017-04-28 13:49 shildenbrand Tag Attached: Lagrangian
2017-04-28 14:00 henry Note Added: 0008052
2017-04-28 14:13 shildenbrand Note Added: 0008053
2017-04-28 14:23 henry Assigned To => henry
2017-04-28 14:23 henry Status new => closed
2017-04-28 14:23 henry Resolution open => no change required
2017-04-28 14:23 henry Fixed in Version => dev