[mwild]

That essentially means you're settings stored in ~/.config/ParaView are corrupt or just "strange". Is it possible to send your ~/.config/ParaView packed up to the Kitware people so they can investigate the problem? Because unless they can get hold of such "corrupt" settings, they won't be able to reproduce the problem easily. And not being able to reproduce a problem makes it virtually impossible to solve any non-trivial problem.

[musahossein]

Gentlemen:

I am running paraview 3.3.0 on OpenSuse 11.0 w/o any problems to date.
Now when I try to save a screen shot of a wire frame of the tank in
the 2dtank sloshing problem, ParaView crashes and issues numerous
errors. I am including a snippet of it below:

X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0ec68
libxcb: WARNING! Program tries to lock an already locked connection,
which indicates a programming error.
There will be no further warnings about this issue.
libxcb: WARNING! Program tries to unlock a connection without having
acquired
a lock first, which indicates a programming error.
There will be no further warnings about this issue.
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0001b
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0001b
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0001b
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0001b
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x2e0001b
X Error: GLXBadContext 154
Extension: 143 (Uknown extension)
Minor opcode: 5 (Unknown request)

Any thoughts, suggestions and prayers will be gratefully accepted. I noted some people talking about paraview 3.5.0. Would this take care of the problem? If yes, where can I download it from and is it compatible witb OpenFoam 1.5?

Musaddeque Hossein

[musahossein]

There is paraview 3.4.0 available for download at the paraview site. Can anyone tell me whether it is compatible with OpenFoam 1.5?

Thanks
Musaddeque Hossein

[7islands]

Hi Musaddeque Hossein,

Do not have a solution for your problem, but one of the followings might work:
1. search the forum with libxcb
2. refer to this thread
3. there has been instructions in this forum for installing and using ParaView 3.4.0
4. ParaView 3.5.0 is a development version available via CVS. You can see how to get it at the download page of the ParaView site.

Takuya

[podallaire]

Hi Takuya,

just a quick question / is the native reader compatible with Bernhar's new super groovyBC lib ?

Best regards,

PO

[7islands]

Hi Pierre-Olivier,

If you mean that you get an error with the wobbler case
ERROR: In /Volumes/RAID0data/paraview/ParaView3/VTK/IO/vtkOpenFOAMReader.cxx, line 6290
vtkOpenFOAMReaderPrivate (0x20a93ec0): Error reading line 23 of /Users/ohshima/OpenFOAM/ohshima-1.5.x/src/groovyBC/Demos/wobbler/0/D: Unexpected token name
, can you try replacing ParaView3/VTK/IO/vtkOpenFOAMReader.cxx with the one that can be checked out with
svn co https://of-interfaces.svn.sourceforge.net/svnroot/of-interfaces/branches/vtkPOpe nFOAMReader-r23-VTKcontrib/BSD
and recompile ParaView. If you have other problems, please let me know the details.

p.s. Please also note that the reader only sees value entries for BCs.

Takuya

[gschaider]

Hi!

I guess the problem is that the boundary condition introduces a sub-dictionary (which is not very common, but legal) and the parser of the native reader doesn't account for that. But I guess Takuya has already figured that out

Bernhard

[7islands]

Yes, that's precisely what I've corrected with the revision in the SVN repository.

T

[podallaire]

Thanks guys !

What would be the best way to verify the BCs created from groovyBC with ParaView and the native reader ?

Thanks

PO

[7islands]

Hi PO,
In other words: the reader does recognize value entries. As far as I understand groovyBC writes the value entries for calculated timesteps (timesteps other than the initial timestep), hence you can verify the boundary values as usual for such timesteps.

For the initial timestep, I haven't tried by myself, but e.g. running foamFormatConvert (so that the calculated values are written in the value entries) may be a workaround.

Takuya

[bastil]

Hi Takuya,

When running the current stable reader with OF1.5 (paraview 3.3-dev) i get the following error reported by Stefan Gerber some time ago.

Expected punctuation token ')', found ;

This only happens for decomposed but not for reconstructed cases.

Regards BastiL

[7islands]

Hi BastiL,
I appreciate if you send the problematic file to me (the address in my profile). You don't have to send all of your case, but just the problematic file should be fine.

Takuya

[bastil]

Takuya,

case is large - just the problematic data-file? I have these problems for all the scalar values (eg. p, k, epsilon...) on each processor? directory.

Regards

[7islands]

So I think I can do with just one of those files. If even each one is too large to be sent, and if it's in ascii format, you can cut the file at few lines below the problematic line (you should be seeing the problematic line number in the error message) and send the part until there. Anyway, there's nothing I can do if I cannot have a reproducing data.

T

[bastil]

Ok, so I got e.g.:

Error reading line 365 of /path/to/parallel/processor1/0/R: Expected punctuation token '(', found ;

## SNIP ## LINE 360 to line 368
360 inlet
361 {
362 type fixedValue;
363 value uniform (0 0 0 0 0 0);
364 }
365 outlet
366 {
367 type zeroGradient;
368 }

Hope this helps. Regards

[bastil]

Sorry, wrong file. It looks like this... (Not very nice but OF1.5.x decomposes it that way)

360 inlet
361 {
362 type fixedValue;
363 value nonuniform
364 0
365 ;
366 }

[7islands]

Ah OK I think I can fix the "Expected punctuation token '(', found ;" error.

Can you identify the suspicious part of the other error "Expected punctuation token ')', found ;" in your 02:43 post? (which expects a closing parenthesis, as opposed to an opening parenthesis)

T

[7islands]

BastiL,
Fixed the "Expected '('" problem, assuming the files are in binary format. Can you try replacing ParaView-(version)/VTK/IO/vtkOpenFOAMReader.cxx with the one that can be checked out with
svn co https://of-interfaces.svn.sourceforge.net/svnroot/of-interfaces/branches/vtkPOpe nFOAMReader-r23-VTKcontrib/BSD
and recompiling ParaView. Please let me know if there are still problems.

Takuya

[bastil]

Takuya,

I will try. Files are Binary, this is all right. The other problem ("Expected punctuation token ')', found ;") can not be reproduced at the moment. I will try the cvs-reader and see wht happens.

Regards BastiL

[bastil]

I can not get pvFoam to run with the new version:

ERROR: In /opt/OpenFOAM/ThirdParty/ParaView3.3-cvs/Servers/Common/vtkProcessModule.cxx, line 1010
vtkProcessModule (0x61cad0): Object type: vtkOpenFOAMReader, could not find requested method: "SetTimeStep"
or the method was called with incorrect arguments.

while processing
Message 0 = Invoke
Argument 0 = id_value {336}
Argument 1 = string_value {SetTimeStep}
Argument 2 = int32_value {0}



ERROR: In /opt/OpenFOAM/ThirdParty/ParaView3.3-cvs/Servers/Common/vtkProcessModule.cxx, line 1011
vtkProcessModule (0x61cad0): Aborting execution for debugging purposes.


/opt/OpenFOAM/OpenFOAM-1.5.x/bin/pvFoam: line 76: 6833 Aborted "${paraviewPath}" --data="${PWD}/system/controlDict.${ext}"

Maybe it is not sufficiant to change only thsifile but using all the other files from the current stable version?

Regards