It's available with git clone git://vtk.org/VTKLargeData.git VTKLargeData.
It's in the Data/WindBladeReader subdirectory there.
On Wed, Oct 3, 2012 at 6:27 PM, Sohail Shafii sohailsha...@yahoo.comwrote:
Which data set are you using for the test?
If it's the single turbine data set with the curvy terrain, I don't have
it (I use other data sets) so I can't do a similar test. Let me know where
I can download it.
Sohail
--
*From:* Andy Bauer andy.ba...@kitware.com
*To:* David E DeMarle dave.dema...@kitware.com
*Cc:* Sohail Shafii sohailsha...@yahoo.com; migic...@gmail.com
migic...@gmail.com; paraview@paraview.org paraview@paraview.org;
Woodring, Jonathan L woodr...@lanl.gov
*Sent:* Wednesday, October 3, 2012 3:16 PM
*Subject:* Re: [Paraview] ParaView thinks that it does not have a wind
blade reader
I finally got around to doing the VTK part of the WindBladeReader work.
It's on gerrit at http://review.source.kitware.com/#/c/7734/. It still
needs some cleanup but at least both the serial test and the parallel test
with a single process pass. For the serial test,
vtkIOGeometryCxx-TestWindBladeReader, I'm still getting the following
warning which needs to be fixed as well:
Warning: In /home/acbauer/CODE/VTK/VTK/IO/Geometry/vtkWindBladeReader.cxx,
line 568
vtkWindBladeReader (0x1373840): 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
Sohail, can you check this out and fix it?
Thanks,
Andy
On Fri, Jul 20, 2012 at 12:02 PM, David E DeMarle
dave.dema...@kitware.com wrote:
Thanks.
In today's git master it now sits in VTK/IO/Parallel/vtkWindbladeReader.
The serial version should go in VTK/IO/Geometry.
The MPI version should go in a new module VTK/IO/MPIParallel.
(VTK/IO/Parallel depends only on vtkSocketController now and should
not depend on vtkMPIController).
Finally when that is done we can remove the flag in paraview's xml
that prevents it from being used in serial.
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii sohailsha...@yahoo.com
wrote:
Well it seems like #1 and #2 can be solved by writing a new parallel wind
blade reader class. I had similar experience by creating distributed
versions of class that I created in other vtk directories. The normal
wind
blade reader would have no parallel calls, which would address #1.
What I find interesting is that in your directories, the wind blade
reader
is located in VTK/IO/Parallel. For the ParaView snapshot that I
downloaded,
as well as the 3.14 source, it's still in VTK/Parallel. No Parallel
folder
in VTK/IO. Is this a recent change?
So maybe the ideal folder layout would be:
VTK/IO/WindBladeReader.*
VTK/IO/Parallel/DistributedWindBladeReader.*
I can make changes to the WindBladeReader to remove the MPI-IO calls and
make a distributed wind blade reader class in case you want to add them
to
the repository. The one template I have for the parallel/serial split is
the
vtkStreamTracer and its distributed counterparts so I can use those as a
guide. If you have better recommendations please let me know.
Sohail
From: David E DeMarle dave.dema...@kitware.com
To: Sohail Shafii sohailsha...@yahoo.com
Cc: Andy Bauer andy.ba...@kitware.com; migic...@gmail.com
migic...@gmail.com; paraview@paraview.org paraview@paraview.org;
Woodring, Jonathan L woodr...@lanl.gov
Sent: Thursday, July 19, 2012 3:20 PM
Subject: Re: [Paraview] ParaView thinks that it does not have a wind
blade
reader
Two issues need to be fixed.
1) that behavior in 3.14 is there because of this fix which we had to
rush in just before the 3.14 release.
Committer: Utkarsh Ayachit utkarsh.ayac...@kitware.com 2012-02-08
17:12:18
Parent: e401d569f6e54c49c3497852463f6b13a01da8b6 (Update version after
3.14.0-RC1 tag.)
Child: 99fdb1aeb5997c29b43393f45a478c4b53a23109 (Merge topic
'fix_windblade_segfault')
Branches: many (31)
Follows: v3.14.0-RC1
Precedes: v3.14.0-RC2
Fix segfault with ParaView built with MPI when opening *.vtr files.
The problem was that vtkWindBlade reader was getting created to test
CanReadFile and that would cause segfault unless MPI was
initialized.
Solved the problem by added support to vtkSMReaderFactory to respect
the
ProcessSupport flag on SourceProxy and change windblade reader XML
to say that
it only works in parallel.
In other words, Windblade reader's Constructor should not take it upon
itself to initialize MPI.
Once that is fixed, we get to issue 2 before paraview 4.0
2) VTK's new modularization has the rule that no module can behave
differently with parallel (or most other
