What is the class that is responsible for testing to reader to see if it can
open the .wind file?
Sohail
________________________________
From: Andy Bauer <andy.ba...@kitware.com>
To: Sohail Shafii <sohailsha...@yahoo.com>
Cc: "Woodring, Jonathan L" <woodr...@lanl.gov>; Sebastien Jourdain
<sebastien.jourd...@kitware.com>; "migic...@gmail.com" <migic...@gmail.com>;
"paraview@paraview.org" <paraview@paraview.org>
Sent: Wednesday, July 11, 2012 10:53 AM
Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade
reader
I was reluctant to enable the reader in serial (i.e. not using MPI IO which I
think is getting done by default with the parallel build) because of the
following warnings that I got:
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
I just assumed that it was getting bad results so I didn't check the serial
output with the parallel output. In either case the code should be changed
before enabling it in serial so that it reads the files correctly and doesn't
produce any warning messages.
Andy
On Wed, Jul 11, 2012 at 12:04 PM, Sohail Shafii <sohailsha...@yahoo.com> wrote:
I'm not aware of any option to build/link against mpi-io. This is just a
standard build with mpi support that suffers from this issue.
>
>
>
>The ParaView website's builds also have the same bug.
>
>
>
>
>________________________________
> From: "Woodring, Jonathan L" <woodr...@lanl.gov>
>To: Sohail Shafii <sohailsha...@yahoo.com>; Andy Bauer
><andy.ba...@kitware.com>; Sebastien Jourdain <sebastien.jourd...@kitware.com>
>Cc: "migic...@gmail.com" <migic...@gmail.com>; "paraview@paraview.org"
><paraview@paraview.org>
>Sent: Tuesday, July 10, 2012 10:06 AM
>
>Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade
>reader
>
>
>
>I added the MPI calls to be in sync with what was being added in the
>simulation.
>
>
>In the SuperComputing demo last year, we updated both the HiGrad FireTec to
>use MPI-IO and likewise ParaView to do the same thing.
>
>
>It was working when I last checked it in November. It could be that you
>didn't build or link against MPI-IO? It might require that the build needs to
>be guarded if you don't have MPI-IO.
>
>
>I thought I did that but it might have gotten changed during the VTK overhaul…
>That's the only thing that I can think of at the moment, because I'm pretty
>sure I had it working in serial with MPI-IO (it shouldn't matter.)
>
>From: Sohail Shafii <sohailsha...@yahoo.com>
>Reply-To: Sohail Shafii <sohailsha...@yahoo.com>
>Date: Tue, 10 Jul 2012 08:44:01 -0700
>To: Andy Bauer <andy.ba...@kitware.com>, Sebastien Jourdain
><sebastien.jourd...@kitware.com>
>Cc: "migic...@gmail.com" <migic...@gmail.com>, woodring <woodr...@lanl.gov>,
>"paraview@paraview.org" <paraview@paraview.org>
>Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade
>reader
>
>
>
>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.ba...@kitware.com>
>To: Sebastien Jourdain <sebastien.jourd...@kitware.com>
>Cc: Sohail Shafii <sohailsha...@yahoo.com>; "migic...@gmail.com"
><migic...@gmail.com>; "woodr...@lanl.gov" <woodr...@lanl.gov>;
>"paraview@paraview.org" <paraview@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.ba...@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.jourd...@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 <sohailsha...@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
>>>
>>
>
>
>
>
>
_______________________________________________
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
