[Doug68]

I’ve been running the motorbike tutorial and got to the point where the steps leading up to opening the case in ParaView have no obvious errors however when opening the case with ParaView I get the following:

ERROR: In ..\..\..\..\source\VTK\IO\vtkOpenFOAMReader.cxx, line 6481
vtkOpenFOAMReaderPrivate (000000000B293690): Error reading line 22 of C:\BlueCFD-2.1\msys\home\ofuser\0/U: Expected number, string or (, found flowVelocity

I get the same error for k, omega and p as well as an additional error:

ERROR: In ..\..\..\..\source\VTK\IO\vtkOpenFOAMReader.cxx, line 6882
vtkOpenFOAMReaderPrivate (000000000B293690): boundaryField motorBike_frt-fairing_001_1 not found in object nut at time = 0

Which I don’t think is related and I’m not focussing on at the moment.
The relevant line in U I think is:

internalField uniform $flowVelocity;

So I think it should be looking up the data in wherever $flowVelocity should be pointing at?
Is that the case? If so how have I stuffed it up?

The attached file shows I’ve got something happening at least in ParaView.

Thanks.

[Doug68]

Ok so now I think I get it. The files such as U or P get filed with the data directly so if they are still showing $Something then the process has not worked.

[lovecraft22]

I get the same error. Is not a big issue. Simply Paraview does not recognize something like:

internalField uniform $flowVelocity;

because he's expecting something like:

internalField uniform (20 0 0);

instead.

I don't think that's a big issue nor that this mean the solution encountered a problem.

[KateEisenhower]

Originally Posted by lovecraft22

I get the same error. Is not a big issue. Simply Paraview does not recognize something like:

internalField uniform $flowVelocity;

because he's expecting something like:

internalField uniform (20 0 0);

instead.

I don't think that's a big issue nor that this mean the solution encountered a problem.

I experienced the same problem. And I agree that it doesn't seem to be any trouble since the correct velocity obviously can be read by the solver and shows up correctly in ParaView at the following time steps.
But I am really wondering why they don't fix it in ParaView. I have always a very uneasy feeling when I'm ignoring error messages.
Does anyone know more about this problem? Any updates?

[rudolf.hellmuth]

Why wonder why people don't complain much about that, since the motorBike tutorial is one of the most popular because of snappyHexMesh. I wonder if not everybody have this problem, so there is a way of fixing it. I would prefer to have all my BC inputs in the single file "include/initialConditions" if possible.

I am also having trouble with the "code#{ ... #};" entry of codedFixedValue. Paraview can't read it. On this post it was said that this should not be an issue with paraview opening .OpenFOAM files, instead of .foam files. I don't have the option of .OpenFOAM files on Paraview 4.1.0 on Mac OS, so I could not test it...