[pici]

Hi to everybody,
sometime, when I use a variable speed like this (in 0/U.air file):

 boundaryField
{    
Bocca   
    {
        type                  uniformFixedValue;
        uniformValue     table (
            (0 (0 0 0))
            (0.1 (0 0 12))
            (3.5 (0 0 12))
            (4 (0 0 0))
            );
        phi                    phi.air;
        alpha                 alpha.air; 
    }
etc...

it happens that openFOAM solver (in my case is DMPFoam) works without any formatting error, but paraview 4.3.1 isn't able to read, showing this error code in Output Message Window:

ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 6467
 vtkOpenFOAMReaderPrivate (0x40c36b0): Error reading line 39 of /media/piero/ExpansionDrive/Root/CMS_oF_2015/oF_cfd/CFL_test/0/U.air:
Expected a number, found (

It seems that paraview is unable to read vectors, in this situation.
Can someone suggest a solution?
Many thanks

Piero

[alexeym]

Hi,

It is not paraview and vectors. It is native paraview OpenFOAM reader and uniformFixedValue (table). So either you ignore error for 0 time (first save will just write value in file, which paraview reads quite successfully), or use OpenFOAM file reader (i.e. compile plugin, use OpenFOAM extension).

[pici]

Originally Posted by alexeym

Hi,

It is not paraview and vectors. It is native paraview OpenFOAM reader and uniformFixedValue (table). So either you ignore error for 0 time (first save will just write value in file, which paraview reads quite successfully), or use OpenFOAM file reader (i.e. compile plugin, use OpenFOAM extension).

Hi Alexey,
I tried you first suggestion (to ignore time 0 errors), but it doesn't work:
in fact, also the second time-step is written as the first, and Paraview 4.3.1 reports the same (=previous) error. The second time step 0.002/U.air is written as quoted:

internalField   nonuniform List<vector> 
11343
(
(-0.00154137 -0.0263397 -0.000788795)
(-0.00271444 -0.0279804 6.3755e-05)

So, my feeling is that Paraview is going wrong to read vectors. I will try to send a bug-report to Kitware.
About you second suggestion (compile plugin, use OpenFOAM extension), I have no time in this moment, by I will do a.s.a.p.
Thank you for your help.

[alexeym]

Hi,

Originally Posted by pici

I tried you first suggestion (to ignore time 0 errors), but it doesn't work:
in fact, also the second time-step is written as the first, and Paraview 4.3.1 reports the same (=previous) error. The second time step 0.002/U.air is written as quoted:

internalField   nonuniform List<vector> 
11343
(
(-0.00154137 -0.0263397 -0.000788795)
(-0.00271444 -0.0279804 6.3755e-05)

Well, yes, you are partly right (I have confused error message with the one, which usually appears in case of #incude statements in boundary conditions). Yet still, the reason for the error is this

...
        uniformValue     table (
            (0 (0 0 0))
            (0.1 (0 0 12))
            (3.5 (0 0 12))
            (4 (0 0 0))
            );
...

part of BC file, as you have got scalar/vector tuples, and Paraview does not like these things. Fortunately Paraview reads pure vectors quite successfully.

[pici]

Originally Posted by alexeym

Hi,
Well, yes, you are partly right (I have confused error message with the one, which usually appears in case of #incude statements in boundary conditions). Yet still, the reason for the error is this

...
        uniformValue     table (
            (0 (0 0 0))
            (0.1 (0 0 12))
            (3.5 (0 0 12))
            (4 (0 0 0))
            );
...

part of BC file, as you have got scalar/vector tuples, and Paraview does not like these things. Fortunately Paraview reads pure vectors quite successfully.

So, Alexey, I rest of my opinion: some Paraview developer does not like these things, but, because this things are standard in openFOAM and they work fine . . . . .

Well, this is my actual workaround:
- reconstructPar (if run was parallelized)
- foamToEnsight -nodeValues
At this point, paraView reads perfectly Ensight case
Thanks of your interest

Piero