[Paraview] ParaView thinks that it does not have a wind blade reader
Sohail Shafii
sohailshafii at yahoo.com
Tue Jul 10 11:44:01 EDT 2012
I'm afraid my knowledge here is a bit limited. All of my edits have been in relation to loading the blade data. The MPI calls were put in by someone else.
By the way, is the wind blade reader updated in VTK as well? (i.e. the VTK package) I remember downloading VTK a while ago and there was a mismatch between that windbladereader and the one in ParaView.
Sohail
________________________________
From: Andy Bauer <andy.bauer at kitware.com>
To: Sebastien Jourdain <sebastien.jourdain at kitware.com>
Cc: Sohail Shafii <sohailshafii at yahoo.com>; "migichen at gmail.com" <migichen at gmail.com>; "woodring at lanl.gov" <woodring at lanl.gov>; "paraview at paraview.org" <paraview at paraview.org>
Sent: Tuesday, July 3, 2012 11:54 AM
Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Hi Sohail,
I went through the code and it jogged my memory about previous problems with it. It had an explicit MPI call in the constructor that would cause problems when paraview wasn't getting built with MPI. Any time a user tried to open an unknown file it would try to create a windblade reader to see if the reader could handle the file and this would cause a crash. If you launch a separate pvserver the wind blade reader will be available in the gui.
If someone fixes this problem in the reader we can enable it properly through the gui. Right now though I'm getting a bunch of warnings when running in serial like:
Warning: In /home/acbauer/CODE/ParaView/ParaView/VTK/IO/Parallel/vtkWindBladeReader.cxx, line 942
vtkWindBladeReader (0x3a0c800): WindBladeReader error reading file: /home/acbauer/DATA/VTKLargeData/Data/WindBladeReader/test1_topo.wind Premature EOF while reading block of data. Expected 896000 but got 0
Andy
On Tue, Jul 3, 2012 at 12:09 PM, Andy Bauer <andy.bauer at kitware.com> wrote:
I get the same problem in both 3.14.1 and master. The reader is still available but just not conveniently through the GUI. To access it though you can bring up the python shell and do the following:
>
>>>> w = WindBladereader()
>>>> w.Filename = "<path>/test1_topo.wind"
>>>> Show()
>>>> Render()
>
>This shouldn't be too hard of a fix for ParaView. I'll let you know when it's done.
>
>Andy
>
>
>
>On Mon, Jul 2, 2012 at 6:03 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>
>Hi Sohail,
>>
>>a similar bug was fixed in master not so long ago. Could you try
>>master to see if the issue remains ?
>>
>>Thanks,
>>
>>Seb
>>
>>
>>On Mon, Jul 2, 2012 at 5:36 PM, Sohail Shafii <sohailshafii at yahoo.com> wrote:
>>> Hi,
>>>
>>> We are trying to open a .wind data set. In the open file menu, ParaView
>>> lists the .wind format as a possible option. Once we click open, however,
>>> it complains that a reader for that data format cannot be found. This is
>>> true for the compiled-from-source and pre-compiled versions of ParaView
>>> 3.14.1. The wind blade source still exists in the VTK/Parallel folder and it
>>> is referenced in the corresponding CMakeLists.txt file. Any thoughts?
>>>
>>> Thanks, Sohail
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>_______________________________________________
>>Powered by www.kitware.com
>>
>>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>>Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>>
>>Follow this link to subscribe/unsubscribe:
>>http://www.paraview.org/mailman/listinfo/paraview
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120710/8dcbbea7/attachment-0001.htm>
More information about the ParaView
mailing list