[Paraview] ParaView thinks that it does not have a wind blade reader
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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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 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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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 = "/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 > 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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Jimmy said that it works. Thanks. Sohail From: Andy Bauer To: Sebastien Jourdain Cc: Sohail Shafii ; "migic...@gmail.com" ; "woodr...@lanl.gov" ; "paraview@paraview.org" Sent: Tuesday, July 3, 2012 10:09 AM Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade reader 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 = "/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 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 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
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 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 = "/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 >> 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
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 To: Sebastien Jourdain Cc: Sohail Shafii ; "migic...@gmail.com" ; "woodr...@lanl.gov" ; "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 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 = "/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 > 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 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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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" To: Sohail Shafii ; Andy Bauer ; Sebastien Jourdain Cc: "migic...@gmail.com" ; "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 Reply-To: Sohail Shafii Date: Tue, 10 Jul 2012 08:44:01 -0700 To: Andy Bauer , Sebastien Jourdain Cc: "migic...@gmail.com" , woodring , "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 To: Sebastien Jourdain Cc: Sohail Shafii ; "migic...@gmail.com" ; "woodr...@lanl.gov" ; "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 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 = "/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 > 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 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://parav
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 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" > *To:* Sohail Shafii ; Andy Bauer < > andy.ba...@kitware.com>; Sebastien Jourdain < > sebastien.jourd...@kitware.com> > *Cc:* "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 > Reply-To: Sohail Shafii > Date: Tue, 10 Jul 2012 08:44:01 -0700 > To: Andy Bauer , Sebastien Jourdain < > sebastien.jourd...@kitware.com> > Cc: "migic...@gmail.com" , woodring , > "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 > *To:* Sebastien Jourdain > *Cc:* Sohail Shafii ; "migic...@gmail.com" < > migic...@gmail.com>; "woodr...@lanl.gov" ; " > 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 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 = "/test1_topo.wind" > >>> Show() > >>> Render() > > This shouldn't be too har
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
What is the class that is responsible for testing to reader to see if it can open the .wind file? Sohail From: Andy Bauer To: Sohail Shafii Cc: "Woodring, Jonathan L" ; Sebastien Jourdain ; "migic...@gmail.com" ; "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 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" >To: Sohail Shafii ; Andy Bauer >; Sebastien Jourdain >Cc: "migic...@gmail.com" ; "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 >Reply-To: Sohail Shafii >Date: Tue, 10 Jul 2012 08:44:01 -0700 >To: Andy Bauer , Sebastien Jourdain > >Cc: "migic...@gmail.com" , woodring , >"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 >To: Sebastien Jourdain >Cc: Sohail Shafii ; "migic...@gmail.com" >; "woodr...@lanl.gov" ; >"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 wrote: > >I get the same problem in both 3.14.1 and master. The reader is still >available but just not convenientl
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
kargad:ParaView demarle$ find . -name "*WindBlade*" -print ---> ./VTK/IO/Parallel/Testing/Cxx/TestWindBladeReader.cxx ./VTK/IO/Parallel/vtkWindBladeReader.cxx ./VTK/IO/Parallel/vtkWindBladeReader.h David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Jul 17, 2012 at 2:09 PM, Sohail Shafii wrote: > What is the class that is responsible for testing to reader to see if it can > open the .wind file? > > Sohail > > > From: Andy Bauer > To: Sohail Shafii > Cc: "Woodring, Jonathan L" ; Sebastien Jourdain > ; "migic...@gmail.com" ; > "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 > 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" > To: Sohail Shafii ; Andy Bauer > ; Sebastien Jourdain > > Cc: "migic...@gmail.com" ; "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 > Reply-To: Sohail Shafii > Date: Tue, 10 Jul 2012 08:44:01 -0700 > To: Andy Bauer , Sebastien Jourdain > > Cc: "migic...@gmail.com" , woodring , > "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 > To: Sebastien Jourdain > Cc: Sohail Shafii ; "migic...@gmail.com" > ; "woodr...@lanl.gov" ; > "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/
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Sorry, but I meant to ask a different question. Here's what Andy said before, which relates to my concern: "> > 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." What I meant was; which ParaView class "creates" or "tests" a reader to see if it can handle a file? The test code you specified has a predefined data set that is loaded in, and I think is more of an example to your average user. Correct me if I'm wrong. So basically ParaView will recognize the file extension, tries to load it, crashes somewhere, then asks you specify the data format from a dialog. I'm trying to figure out where it crashes so that I can see how that relates to the wind blade reader class and any MPI calls that are in there. Sohail From: David E DeMarle To: Sohail Shafii Cc: Andy Bauer ; "migic...@gmail.com" ; "paraview@paraview.org" ; "Woodring, Jonathan L" Sent: Tuesday, July 17, 2012 12:43 PM Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade reader kargad:ParaView demarle$ find . -name "*WindBlade*" -print ---> ./VTK/IO/Parallel/Testing/Cxx/TestWindBladeReader.cxx ./VTK/IO/Parallel/vtkWindBladeReader.cxx ./VTK/IO/Parallel/vtkWindBladeReader.h David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Jul 17, 2012 at 2:09 PM, Sohail Shafii wrote: > What is the class that is responsible for testing to reader to see if it can > open the .wind file? > > Sohail > > > From: Andy Bauer > To: Sohail Shafii > Cc: "Woodring, Jonathan L" ; Sebastien Jourdain > ; "migic...@gmail.com" ; > "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 > 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" > To: Sohail Shafii ; Andy Bauer > ; Sebastien Jourdain > > Cc: "migic...@gmail.com" ; "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 > Reply-To: Sohail Shafii > Date: Tue, 10 Jul 2012 08:44:01 -0700 > To: Andy Bauer , Sebastien Jourdain > > Cc: "migic...@gmail.com" , woodring , > "paraview@paraview.org" > Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade > reader
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Each file that has an association with that file extension, made via the XML, has its CanReadFile method called. Put a breakpoint there to determine if ParaView even knows about that reader. On Tuesday, July 17, 2012, Sohail Shafii wrote: > Sorry, but I meant to ask a different question. Here's what Andy said > before, which relates to my concern: > "> > > 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." > > What I meant was; which ParaView class "creates" or "tests" a reader to > see if it can handle a file? The test code you specified has a predefined > data set that is loaded in, and I think is more of an example to your > average user. Correct me if I'm wrong. > > So basically ParaView will recognize the file extension, tries to load it, > crashes somewhere, then asks you specify the data format from a dialog. > I'm trying to figure out where it crashes so that I can see how that > relates to the wind blade reader class and any MPI calls that are in there. > > Sohail > > *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind > blade reader > > kargad:ParaView demarle$ find . -name "*WindBlade*" -print > ---> ./VTK/IO/Parallel/Testing/Cxx/TestWindBladeReader.cxx > ./VTK/IO/Parallel/vtkWindBladeReader.cxx > ./VTK/IO/Parallel/vtkWindBladeReader.h > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Tue, Jul 17, 2012 at 2:09 PM, Sohail Shafii > wrote: > > What is the class that is responsible for testing to reader to see if it > can > > open the .wind file? > > > > Sohail > > > > ____ > > From: Andy Bauer > > To: Sohail Shafii > > Cc: "Woodring, Jonathan L" ; Sebastien Jourdain > > ; "migic...@gmail.com" < > migic...@gmail.com>; > > "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 > > 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" > > To: Sohail Shafii ; Andy Bauer > > ; Sebastien Jourdain > > > > Cc: "migic...@gmail.com" ; "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 w > -- David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 ___ 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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
When running serially, vtkSMReaderFactory::CanReadFile sees that the session has a single process. As such, on line 660 it realizes that the source proxy's process support (in this case the source is a vtkWindBladeReader proxy) is multiple processes, which causes a return of "false" from that function. This makes ParaView think that the wind blade reader can't read a .wind file in serial. According to Andy, the reader works find in parallel. I assume that a fix for this is pretty trivial? It never did this before in previous versions of ParaView and I think that the wind blade reader code has remained mostly the same. Andy mentioned some details in person when he was talking with Jon but at that time I didn't know as much as I do now. There is a mention below about enabling the filter in serial and parallel -- is this done in a xml file? Sohail From: David E DeMarle To: Sohail Shafii Cc: Andy Bauer ; "migic...@gmail.com" ; "paraview@paraview.org" ; "Woodring, Jonathan L" Sent: Tuesday, July 17, 2012 7:00 PM Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade reader Each file that has an association with that file extension, made via the XML, has its CanReadFile method called. Put a breakpoint there to determine if ParaView even knows about that reader. On Tuesday, July 17, 2012, Sohail Shafii wrote: Sorry, but I meant to ask a different question. Here's what Andy said before, which relates to my concern: >"> >> 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." > > >What I meant was; which ParaView class "creates" or "tests" a reader to see if >it can handle a file? The test code you specified has a predefined data set >that is loaded in, and I think is more of an example to your average user. >Correct me if I'm wrong. > > >So basically ParaView will recognize the file extension, tries to load it, >crashes somewhere, then asks you specify the data format from a dialog. I'm >trying to figure out where it crashes so that I can see how that relates to >the wind blade reader class and any MPI calls that are in there. > > >Sohail > > >Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade >reader > >kargad:ParaView demarle$ find . -name "*WindBlade*" -print >---> ./VTK/IO/Parallel/Testing/Cxx/TestWindBladeReader.cxx >./VTK/IO/Parallel/vtkWindBladeReader.cxx >./VTK/IO/Parallel/vtkWindBladeReader.h > >David E DeMarle >Kitware, Inc. >R&D Engineer >21 Corporate Drive >Clifton Park, NY 12065-8662 >Phone: 518-881-4909 > > >On Tue, Jul 17, 2012 at 2:09 PM, Sohail Shafii wrote: >> What is the class that is responsible for testing to reader to see if it can >> open the .wind file? >> >> Sohail >> >> ____ >> From: Andy Bauer >> To: Sohail Shafii >> Cc: "Woodring, Jonathan L" ; Sebastien Jourdain >> ; "migic...@gmail.com" ; >> "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 >> wrote: >> >> I'm not aware of any option to build/link against mpi-io. This is just a >> standard
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 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 cmake config options) turned configured on or off. This is so because it makes it very hard to package VTK when the libs behave differently in different situations. Ie, we can't have any more #ifdef VTK_USE_MPI do something #else do something different #endif in VTK classes. Now if we want a class to behave differently when MPI is turned on or off we have to make a serial only version in a non MPI dependent module and a subclass of that in an MPI dependent module. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jul 19, 2012 at 3:52 PM, Sohail Shafii wrote: > When running serially, vtkSMReaderFactory::CanReadFile sees that the session > has a single process. As such, on line 660 it realizes that the source > proxy's process support (in this case the source is a vtkWindBladeReader > proxy) is multiple processes, which causes a return of "false" from that > function. This makes ParaView think that the wind blade reader can't read a > .wind file in serial. According to Andy, the reader works find in parallel. > > I assume that a fix for this is pretty trivial? It never did this before in > previous versions of ParaView and I think that the wind blade reader code > has remained mostly the same. Andy mentioned some details in person when he > was talking with Jon but at that time I didn't know as much as I do now. > There is a mention below about enabling the filter in serial and parallel -- > is this done in a xml file? > > Sohail > > > From: David E DeMarle > To: Sohail Shafii > Cc: Andy Bauer ; "migic...@gmail.com" > ; "paraview@paraview.org" ; > "Woodring, Jonathan L" > Sent: Tuesday, July 17, 2012 7:00 PM > > Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade > reader > > Each file that has an association with that file extension, made via the > XML, has its CanReadFile method called. Put a breakpoint there to determine > if ParaView even knows about that reader. > > On Tuesday, July 17, 2012, Sohail Shafii wrote: > > Sorry, but I meant to ask a different question. Here's what Andy said > before, which relates to my concern: > "> >> 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." > > What I meant was; which ParaView class "creates" or "tests" a reader to see > if it can handle a file? The test code you specified has a predefined data > set that is loaded in, and I think is more of an example to your average > user. Correct me if I'm wrong. > > So basically ParaView will recognize the file extension, tries to load it, > crashes somewhere, then asks you specify the data format from a dialog. I'm > trying to figure out where it crashes so that I can see how that relates to > the wind blade reader class and any MPI calls that are in there. > > Sohail > > Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade > reader > > kargad:ParaView demarle$ find . -name "*WindBlade*" -print > ---> ./VTK/IO/Parallel/Testing/Cxx/TestWindBladeReader.cxx > ./VTK/IO/Parall
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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 To: Sohail Shafii Cc: Andy Bauer ; "migic...@gmail.com" ; "paraview@paraview.org" ; "Woodring, Jonathan L" 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 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 cmake config options) turned configured on or off. This is so because it makes it very hard to package VTK when the libs behave differently in different situations. Ie, we can't have any more #ifdef VTK_USE_MPI do something #else do something different #endif in VTK classes. Now if we want a class to behave differently when MPI is turned on or off we have to make a serial only version in a non MPI dependent module and a subclass of that in an MPI dependent module. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jul 19, 2012 at 3:52 PM, Sohail Shafii wrote: > When running serially, vtkSMReaderFactory::CanReadFile sees that the session > has a single process. As such, on line 660 it realizes that the source > proxy's process support (in this case the source is a vtkWindBladeReader > proxy) is multiple processes, which causes a return of "false" from that > function. This makes ParaView think that the wind blade reader can't read a > .wind file in serial. According to Andy, the reader works find in parallel. > > I assume that a fix for this is pretty trivial? It never did this before in > previous versions of ParaView and I think that the wind blade reader code > has remained mostly the same. Andy mentioned some details in person when he > was talking with Jon but at that time I didn't know as much as I do now. > There is a mention below about enabling the filter in serial and parallel -- > is this done in a xml file? > > Sohail > > > From: David E DeMarle > To: Sohail Shafii > Cc: Andy Bauer ; "migic...@gmail.com" > ; "paraview@paraview.org" ; > "Woodring, Jonathan L" > Sent: Tuesday, July 17, 2012 7:00 PM > > Subject: Re: [Paraview] ParaView thinks that it does not have a wind blade > reader > > Each file that has an association with that file extension, made via the > XML, has its CanReadFile method called. Put a breakpoint there to determine > if ParaView even knows about that reader. > > On Tuesday, July 17, 2012, Sohail Shafii wrote: > > Sorry, but I meant to ask a different question. Here's what Andy said > before, which relates to my concern: > "> >> I went through the code and it jogged my memory about previous problems >> w
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii 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 > To: Sohail Shafii > Cc: Andy Bauer ; "migic...@gmail.com" > ; "paraview@paraview.org" ; > "Woodring, Jonathan L" > 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 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 cmake config options) turned > configured on or off. This is so because it makes it very hard to > package VTK when the libs behave differently in different situations. > > Ie, we can't have any more > #ifdef VTK_USE_MPI > do something > #else > do something different > #endif > in VTK classes. > > Now if we want a class to behave differently when MPI is turned on or > off we have to make a serial only version in a non MPI dependent > module and a subclass of that in an MPI dependent module. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Thu, Jul 19, 2012 at 3:52 PM, Sohail Shafii > wrote: >> When running serially, vtkSMReaderFactory::CanReadFile sees that the >> session >> has a single process. As such, on line 660 it realizes that the source >> proxy's process support (in this case the source is a vtkWindBladeReader >> proxy) is multiple processes, which causes a return of "false" from that >> function. This makes ParaView think that the wind blade reader can't read >> a >> .wind file in serial. According to Andy, the reader works find in >> parallel. >> >> I assume that a fix for this is pretty trivial? It never did this before >> in >> previous versions of ParaView and I think that the wind blade reader code >> has remained mostly the same. Andy mentioned some details in person when >>
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Hi Sohail,
Sorry for the slow reply but I wanted to make sure how things should work
first and that took a bit to figure out. Anyways, this is closer to what's
needed but the way it is supposed to work in VTK is that we use
vtkObjectFactory to determine which one should be created when
vtkWindBladeReader::New() is called. This is done at build time based on
whether or not VTK is built with MPI. So if VTK and ParaView are built in
parallel then there is code added that creates a vtkPWindBladeReader when
vtkWindBladeReader::New() is called. This is regardless of whether or not
the executable is run with mpi initialized or not. Because of this, the
parallel version of the reader is responsible for checking whether mpi is
initialized, ideally by doing
vtkMultiProcessController::GetGlobalController()->IsA("vtkMPIController")
is true, and if it isn't it should just call the parent class's methods for
reading in the files. You may want to look at vtkPNrrdReader and the
CMakeLists.txt file in that directory to see how they did things. Note
though that if it's a single process running that it doesn't do any MPI
calls even in the parallel version so your code will be slightly different
than theirs.
As for other parts of the email below:
1) yes, please keep cc'ing the list as there are some details in here that
will be helpful to other people trying to implement their own parallel
readers or filters
2) I'm not sure what's going on with the gradient filter but am guessing
that it has to do with the multiblock data set and that there probably
isn't that same array in each block. But that's just a guess. Did you try
extracting the "air" block and do the vorticity and/or q criterion
computation on that?
3) vtkSMReaderFactory may be the class you're looking for to determine
which reader is getting used. ParaViewReaders.xml has a list of readers
that it will try to read in a file.
Andy
On Tue, Aug 21, 2012 at 7:11 PM, Sohail Shafii wrote:
> because it's stupid>
>
> Here's the first version. Do you want me to keep ccing the list? Not sure
> if that's necessary at this point because this is related to the
> development of ParaView and not help.
>
> I've run it with an older version of the master, and it seems to read in a
> test .wind file just fine. For now I had to store the vtkPWindBladeReader*
> files into VTK/Parallel/MPI since I don't have VTK/IO/MPIParallel module
> yet. Now when I run the gradient filter after the field, the gradient
> filter thinks that the input array does not have the appropriate number of
> components for Q criterion or vorticity...but it should (UVW does have
> three components per tuple). Might be my outdated copy of the git repo.
> Haven't debugged that gradient code yet.
>
> *I was wondering if this is the type of code that you want? Or should
> the classes be designed differently?* Also, I have only run it parallel
> because if I try to instantiate it inside of the python shell in serial it
> tries to run RequestInformation (which assumes that the file path exists
> but does not). It's a work-in-progress but it's a start.
>
> A random question: if ParaView reads a file, where would I put a
> breakpoint that tells me which reader it ends up picking?? I have some
> separate VTK code that reads in a rectilinear grid, but does not generate
> cell/bounds information. ParaView does generate information about the
> bounds though.
>
> Sohail
>
> --
> *From:* David E DeMarle
> *To:* Sohail Shafii
> *Cc:* Andy Bauer ; "migic...@gmail.com" <
> migic...@gmail.com>; "paraview@paraview.org" ;
> "Woodring, Jonathan L"
> *Sent:* Friday, July 20, 2012 10:02 AM
> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind
> blade reader
>
> 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.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
> On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii
> 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
&g
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
I see...so if MPI is running then it will create a parallel version of the
class. Otherwise, it will create the normal reader.
As far as the check goes for a multiprocess controller; while it does call
the parent request data in the serial case, the inherited parallel class
overrides some of the methods. Which is a problem because it refers to its
own file pointer in those methods (it uses MPI_File instead of a FILE*).
Hmm.
Sohail
On Thu, Aug 23, 2012 at 3:20 PM, Andy Bauer wrote:
> Hi Sohail,
>
> Sorry for the slow reply but I wanted to make sure how things should work
> first and that took a bit to figure out. Anyways, this is closer to what's
> needed but the way it is supposed to work in VTK is that we use
> vtkObjectFactory to determine which one should be created when
> vtkWindBladeReader::New() is called. This is done at build time based on
> whether or not VTK is built with MPI. So if VTK and ParaView are built in
> parallel then there is code added that creates a vtkPWindBladeReader when
> vtkWindBladeReader::New() is called. This is regardless of whether or not
> the executable is run with mpi initialized or not. Because of this, the
> parallel version of the reader is responsible for checking whether mpi is
> initialized, ideally by doing
> vtkMultiProcessController::GetGlobalController()->IsA("vtkMPIController")
> is true, and if it isn't it should just call the parent class's methods for
> reading in the files. You may want to look at vtkPNrrdReader and the
> CMakeLists.txt file in that directory to see how they did things. Note
> though that if it's a single process running that it doesn't do any MPI
> calls even in the parallel version so your code will be slightly different
> than theirs.
>
> As for other parts of the email below:
>
> 1) yes, please keep cc'ing the list as there are some details in here that
> will be helpful to other people trying to implement their own parallel
> readers or filters
>
> 2) I'm not sure what's going on with the gradient filter but am guessing
> that it has to do with the multiblock data set and that there probably
> isn't that same array in each block. But that's just a guess. Did you try
> extracting the "air" block and do the vorticity and/or q criterion
> computation on that?
>
> 3) vtkSMReaderFactory may be the class you're looking for to determine
> which reader is getting used. ParaViewReaders.xml has a list of readers
> that it will try to read in a file.
>
> Andy
>
>
> On Tue, Aug 21, 2012 at 7:11 PM, Sohail Shafii wrote:
>
>> > stuff because it's stupid>
>>
>> Here's the first version. Do you want me to keep ccing the list? Not
>> sure if that's necessary at this point because this is related to the
>> development of ParaView and not help.
>>
>> I've run it with an older version of the master, and it seems to read in
>> a test .wind file just fine. For now I had to store the
>> vtkPWindBladeReader* files into VTK/Parallel/MPI since I don't have
>> VTK/IO/MPIParallel module yet. Now when I run the gradient filter after
>> the field, the gradient filter thinks that the input array does not have
>> the appropriate number of components for Q criterion or vorticity...but it
>> should (UVW does have three components per tuple). Might be my outdated
>> copy of the git repo. Haven't debugged that gradient code yet.
>>
>> *I was wondering if this is the type of code that you want? Or should
>> the classes be designed differently?* Also, I have only run it parallel
>> because if I try to instantiate it inside of the python shell in serial it
>> tries to run RequestInformation (which assumes that the file path exists
>> but does not). It's a work-in-progress but it's a start.
>>
>> A random question: if ParaView reads a file, where would I put a
>> breakpoint that tells me which reader it ends up picking?? I have some
>> separate VTK code that reads in a rectilinear grid, but does not generate
>> cell/bounds information. ParaView does generate information about the
>> bounds though.
>>
>> Sohail
>>
>> --
>> *From:* David E DeMarle
>> *To:* Sohail Shafii
>> *Cc:* Andy Bauer ; "migic...@gmail.com" <
>> migic...@gmail.com>; "paraview@paraview.org" ;
>> "Woodring, Jonathan L"
>> *Sent:* Friday, July 20, 2012 10:02 AM
>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind
>> blade reader
>>
>> Thanks.
>>
>> In today's git master it now sits in VTK/IO/Paralle
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
f ParaView reads a file, where would I put a >>> breakpoint that tells me which reader it ends up picking?? I have some >>> separate VTK code that reads in a rectilinear grid, but does not generate >>> cell/bounds information. ParaView does generate information about the >>> bounds though. >>> >>> Sohail >>> >>> -- >>> *From:* David E DeMarle >>> *To:* Sohail Shafii >>> *Cc:* Andy Bauer ; "migic...@gmail.com" < >>> migic...@gmail.com>; "paraview@paraview.org" ; >>> "Woodring, Jonathan L" >>> *Sent:* Friday, July 20, 2012 10:02 AM >>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind >>> blade reader >>> >>> 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. >>> R&D Engineer >>> 21 Corporate Drive >>> Clifton Park, NY 12065-8662 >>> Phone: 518-881-4909 >>> >>> >>> On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii >>> 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 >>> > To: Sohail Shafii >>> > Cc: Andy Bauer ; "migic...@gmail.com" >>> > ; "paraview@paraview.org" ; >>> > "Woodring, Jonathan L" >>> > 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 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 >>> >ProcessS
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
me to keep ccing the list? Not >>>> sure if that's necessary at this point because this is related to the >>>> development of ParaView and not help. >>>> >>>> I've run it with an older version of the master, and it seems to read >>>> in a test .wind file just fine. For now I had to store the >>>> vtkPWindBladeReader* files into VTK/Parallel/MPI since I don't have >>>> VTK/IO/MPIParallel module yet. Now when I run the gradient filter after >>>> the field, the gradient filter thinks that the input array does not have >>>> the appropriate number of components for Q criterion or vorticity...but it >>>> should (UVW does have three components per tuple). Might be my outdated >>>> copy of the git repo. Haven't debugged that gradient code yet. >>>> >>>> *I was wondering if this is the type of code that you want? Or should >>>> the classes be designed differently?* Also, I have only run it >>>> parallel because if I try to instantiate it inside of the python shell in >>>> serial it tries to run RequestInformation (which assumes that the file path >>>> exists but does not). It's a work-in-progress but it's a start. >>>> >>>> A random question: if ParaView reads a file, where would I put a >>>> breakpoint that tells me which reader it ends up picking?? I have some >>>> separate VTK code that reads in a rectilinear grid, but does not generate >>>> cell/bounds information. ParaView does generate information about the >>>> bounds though. >>>> >>>> Sohail >>>> >>>> -- >>>> *From:* David E DeMarle >>>> *To:* Sohail Shafii >>>> *Cc:* Andy Bauer ; "migic...@gmail.com" < >>>> migic...@gmail.com>; "paraview@paraview.org" ; >>>> "Woodring, Jonathan L" >>>> *Sent:* Friday, July 20, 2012 10:02 AM >>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind >>>> blade reader >>>> >>>> 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. >>>> R&D Engineer >>>> 21 Corporate Drive >>>> Clifton Park, NY 12065-8662 >>>> Phone: 518-881-4909 >>>> >>>> >>>> On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii >>>> 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. >>>> > >>>> >
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
nd/or q criterion >>>> computation on that? >>>> >>>> 3) vtkSMReaderFactory may be the class you're looking for to determine >>>> which reader is getting used. ParaViewReaders.xml has a list of readers >>>> that it will try to read in a file. >>>> >>>> Andy >>>> >>>> >>>> On Tue, Aug 21, 2012 at 7:11 PM, Sohail Shafii wrote: >>>> >>>>> >>>> stuff because it's stupid> >>>>> >>>>> Here's the first version. Do you want me to keep ccing the list? Not >>>>> sure if that's necessary at this point because this is related to the >>>>> development of ParaView and not help. >>>>> >>>>> I've run it with an older version of the master, and it seems to read >>>>> in a test .wind file just fine. For now I had to store the >>>>> vtkPWindBladeReader* files into VTK/Parallel/MPI since I don't have >>>>> VTK/IO/MPIParallel module yet. Now when I run the gradient filter after >>>>> the field, the gradient filter thinks that the input array does not have >>>>> the appropriate number of components for Q criterion or vorticity...but it >>>>> should (UVW does have three components per tuple). Might be my outdated >>>>> copy of the git repo. Haven't debugged that gradient code yet. >>>>> >>>>> *I was wondering if this is the type of code that you want? Or >>>>> should the classes be designed differently?* Also, I have only run >>>>> it parallel because if I try to instantiate it inside of the python shell >>>>> in serial it tries to run RequestInformation (which assumes that the file >>>>> path exists but does not). It's a work-in-progress but it's a start. >>>>> >>>>> A random question: if ParaView reads a file, where would I put a >>>>> breakpoint that tells me which reader it ends up picking?? I have some >>>>> separate VTK code that reads in a rectilinear grid, but does not generate >>>>> cell/bounds information. ParaView does generate information about the >>>>> bounds though. >>>>> >>>>> Sohail >>>>> >>>>> -- >>>>> *From:* David E DeMarle >>>>> *To:* Sohail Shafii >>>>> *Cc:* Andy Bauer ; "migic...@gmail.com" < >>>>> migic...@gmail.com>; "paraview@paraview.org" ; >>>>> "Woodring, Jonathan L" >>>>> *Sent:* Friday, July 20, 2012 10:02 AM >>>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a >>>>> wind blade reader >>>>> >>>>> 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. >>>>> R&D Engineer >>>>> 21 Corporate Drive >>>>> Clifton Park, NY 12065-8662 >>>>> Phone: 518-881-4909 >>>>> >>>>> >>>>> On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii >>>>> 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 >
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Note >>>>> though that if it's a single process running that it doesn't do any MPI >>>>> calls even in the parallel version so your code will be slightly different >>>>> than theirs. >>>>> >>>>> As for other parts of the email below: >>>>> >>>>> 1) yes, please keep cc'ing the list as there are some details in here >>>>> that will be helpful to other people trying to implement their own >>>>> parallel >>>>> readers or filters >>>>> >>>>> 2) I'm not sure what's going on with the gradient filter but am >>>>> guessing that it has to do with the multiblock data set and that there >>>>> probably isn't that same array in each block. But that's just a guess. Did >>>>> you try extracting the "air" block and do the vorticity and/or q criterion >>>>> computation on that? >>>>> >>>>> 3) vtkSMReaderFactory may be the class you're looking for to determine >>>>> which reader is getting used. ParaViewReaders.xml has a list of readers >>>>> that it will try to read in a file. >>>>> >>>>> Andy >>>>> >>>>> >>>>> On Tue, Aug 21, 2012 at 7:11 PM, Sohail Shafii >>>>> wrote: >>>>> >>>>>> >>>>> stuff because it's stupid> >>>>>> >>>>>> Here's the first version. Do you want me to keep ccing the list? Not >>>>>> sure if that's necessary at this point because this is related to the >>>>>> development of ParaView and not help. >>>>>> >>>>>> I've run it with an older version of the master, and it seems to read >>>>>> in a test .wind file just fine. For now I had to store the >>>>>> vtkPWindBladeReader* files into VTK/Parallel/MPI since I don't have >>>>>> VTK/IO/MPIParallel module yet. Now when I run the gradient filter after >>>>>> the field, the gradient filter thinks that the input array does not have >>>>>> the appropriate number of components for Q criterion or vorticity...but >>>>>> it >>>>>> should (UVW does have three components per tuple). Might be my outdated >>>>>> copy of the git repo. Haven't debugged that gradient code yet. >>>>>> >>>>>> *I was wondering if this is the type of code that you want? Or >>>>>> should the classes be designed differently?* Also, I have only run >>>>>> it parallel because if I try to instantiate it inside of the python shell >>>>>> in serial it tries to run RequestInformation (which assumes that the file >>>>>> path exists but does not). It's a work-in-progress but it's a start. >>>>>> >>>>>> A random question: if ParaView reads a file, where would I put a >>>>>> breakpoint that tells me which reader it ends up picking?? I have some >>>>>> separate VTK code that reads in a rectilinear grid, but does not generate >>>>>> cell/bounds information. ParaView does generate information about the >>>>>> bounds though. >>>>>> >>>>>> Sohail >>>>>> >>>>>> -- >>>>>> *From:* David E DeMarle >>>>>> *To:* Sohail Shafii >>>>>> *Cc:* Andy Bauer ; "migic...@gmail.com" < >>>>>> migic...@gmail.com>; "paraview@paraview.org" ; >>>>>> "Woodring, Jonathan L" >>>>>> *Sent:* Friday, July 20, 2012 10:02 AM >>>>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a >>>>>> wind blade reader >>>>>> >>>>>> 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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
gt;> of the class. Otherwise, it will create the normal reader.
>>>>>>
>>>>>
>>>>> Technically, if ParaView is built with MPI enabled it will create the
>>>>> parallel version of the class every time whether or not the client,
>>>>> server,
>>>>> or python scripts are actually run with mpiexec, mpirun, or whatever is
>>>>> used to start the executable. So you can't rely on MPI being initialized
>>>>> and should not initialize it yourself in your class as that can cause
>>>>> problems as well. I think that's what you meant but wanted to be as clear
>>>>> as possible for the implications for the classes.
>>>>>
>>>>>
>>>>>>
>>>>>> As far as the check goes for a multiprocess controller; while it does
>>>>>> call the parent request data in the serial case, the inherited parallel
>>>>>> class overrides some of the methods. Which is a problem because it
>>>>>> refers
>>>>>> to its own file pointer in those methods (it uses MPI_File instead of a
>>>>>> FILE*). Hmm.
>>>>>>
>>>>>> Sohail
>>>>>>
>>>>>>
>>>>>> On Thu, Aug 23, 2012 at 3:20 PM, Andy Bauer
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Sohail,
>>>>>>>
>>>>>>> Sorry for the slow reply but I wanted to make sure how things should
>>>>>>> work first and that took a bit to figure out. Anyways, this is closer to
>>>>>>> what's needed but the way it is supposed to work in VTK is that we use
>>>>>>> vtkObjectFactory to determine which one should be created when
>>>>>>> vtkWindBladeReader::New() is called. This is done at build time based on
>>>>>>> whether or not VTK is built with MPI. So if VTK and ParaView are built
>>>>>>> in
>>>>>>> parallel then there is code added that creates a vtkPWindBladeReader
>>>>>>> when
>>>>>>> vtkWindBladeReader::New() is called. This is regardless of whether or
>>>>>>> not
>>>>>>> the executable is run with mpi initialized or not. Because of this, the
>>>>>>> parallel version of the reader is responsible for checking whether mpi
>>>>>>> is
>>>>>>> initialized, ideally by doing
>>>>>>> vtkMultiProcessController::GetGlobalController()->IsA("vtkMPIController")
>>>>>>> is true, and if it isn't it should just call the parent class's methods
>>>>>>> for
>>>>>>> reading in the files. You may want to look at vtkPNrrdReader and the
>>>>>>> CMakeLists.txt file in that directory to see how they did things. Note
>>>>>>> though that if it's a single process running that it doesn't do any MPI
>>>>>>> calls even in the parallel version so your code will be slightly
>>>>>>> different
>>>>>>> than theirs.
>>>>>>>
>>>>>>> As for other parts of the email below:
>>>>>>>
>>>>>>> 1) yes, please keep cc'ing the list as there are some details in
>>>>>>> here that will be helpful to other people trying to implement their own
>>>>>>> parallel readers or filters
>>>>>>>
>>>>>>> 2) I'm not sure what's going on with the gradient filter but am
>>>>>>> guessing that it has to do with the multiblock data set and that there
>>>>>>> probably isn't that same array in each block. But that's just a guess.
>>>>>>> Did
>>>>>>> you try extracting the "air" block and do the vorticity and/or q
>>>>>>> criterion
>>>>>>> computation on that?
>>>>>>>
>>>>>>> 3) vtkSMReaderFactory may be the class you're looking for to
>>>>>>> determine which reader is getting used. ParaViewReaders.xml has a list
>>>>>>> of
>>>>>>> readers that it will try to read in a file.
>>>>>>>
>>>>>>> Andy
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Aug 21, 2012 at 7:11 PM, Sohail
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 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. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii > 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 > > To: Sohail Shafii > > Cc: Andy Bauer ; "migic...@gmail.com" > > ; "paraview@paraview.org" ; > > "Woodring, Jonathan L" > > 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 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 cmake config options) turned > > configured on or off. This is so because it makes it very hard to > > package VTK when the libs behave differently in different situations. > > > > Ie, we can't have any more > > #ifdef VTK_USE_MPI > > do something > > #else > > d
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
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 wrote: > 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 > *To:* David E DeMarle > *Cc:* Sohail Shafii ; "migic...@gmail.com" < > migic...@gmail.com>; "paraview@paraview.org" ; > "Woodring, Jonathan L" > *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. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii > 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 > > To: Sohail Shafii > > Cc: Andy Bauer ; "migic...@gmail.com" > > ; "paraview@paraview.org" ; > > "Woodring, Jonathan L" > > 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 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 &
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Hi Sohail, Did you get a chance to look at the warnings for the vtkIOGeometryCxx-TestWindBladeReader test for the http://review.source.kitware.com/#/t/1396/ gerrit topic? It's going to need to be fixed pretty soon if it's going to make it into the ParaView 4.0 release. Thanks, Andy On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer wrote: > 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 wrote: > >> 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 >> *To:* David E DeMarle >> *Cc:* Sohail Shafii ; "migic...@gmail.com" < >> migic...@gmail.com>; "paraview@paraview.org" ; >> "Woodring, Jonathan L" >> *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. >> R&D Engineer >> 21 Corporate Drive >> Clifton Park, NY 12065-8662 >> Phone: 518-881-4909 >> >> >> On Thu, Jul 19, 2012 at 7:08 PM, Sohail Shafii >> 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 >> > To: Sohail Shafii >> > Cc: Andy Bauer ; "migic...@gmail.com" >> > ; "paraview@paraview.org" ; >> > "Woodring, Jonathan L" >> > Sent: Thursday, July 19, 2012 3:20 PM >> > >> > Subject: Re: [Paraview] ParaView thinks that it does not have a wind >&g
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Current master version can't launch (MacOS Mountain Lion): paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Program received signal SIGABRT, Aborted. 0x7fff82432212 in __pthread_kill () (gdb) bt 14 #0 0x7fff82432212 in __pthread_kill () #1 0x7fff87964af4 in pthread_kill () #2 0x7fff879a8dce in abort () #3 0x7fff8797c959 in free () #4 0x7fff5fc0762a in __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ () #5 0x7fff5fc0f06b in __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () #6 0x7fff5fc04ce4 in __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () #7 0x7fff5fc0a81a in __dyld_dlopen () #8 0x7fff8ac96dd8 in dlopen () #9 0x7fff83dcfa10 in gfxInitializeLibrary () #10 0x00011e6014fe in gliInitializeLibrary () #11 0x7fff8a4f63e6 in glcPluginCount () #12 0x7fff8a4f62a8 in glcPluginCount () #13 0x7fff8a4f6091 in glcPluginCount () (More stack frames follow...) Which version of the master works, so that I can debug? Sohail On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer wrote: > A beta version will be released by mid-November. In order for the desired > changes to make it in to that, the VTK part that's waiting your changes > needs to go in early next week so that I can make the changes to ParaView > to enable the WindBlade reader when running in either built-in mode or > connecting to a serial server. > > Andy > > On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii wrote: > >> >> Haven't had a chance yet due to a paper. I'll look at it this week. How >> soon will it be released? >> >> Also please respond to my sssha...@ucdavis.edu as this address is not on >> the paraview list anymore. >> >> Sohail >> >> -- >> *From:* Andy Bauer >> *To:* Sohail Shafii >> *Cc:* David E DeMarle ; "migic...@gmail.com" < >> migic...@gmail.com>; "paraview@paraview.org" ; >> "Woodring, Jonathan L" >> *Sent:* Wednesday, October 24, 2012 8:09 AM >> >> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind >> blade reader >> >> Hi Sohail, >> >> Did you get a chance to look at the warnings for the >> vtkIOGeometryCxx-TestWindBladeReader test for the >> http://review.source.kitware.com/#/t/1396/ gerrit topic? It's going to >> need to be fixed pretty soon if it's going to make it into the ParaView 4.0 >> release. >> >> Thanks, >> Andy >> >> On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer wrote: >> >> It's available with "git clone git://vtk.org/VTKLargeData.gitVTKLargeData". >> It's in the Data/WindBladeReader subdirectory there. >> >> On Wed, Oct 3, 2012 at 6:27 PM, Sohail Shafii wrote: >> >> 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 >> *To:* David E DeMarle >> *Cc:* Sohail Shafii ; "migic...@gmail.com" < >> migic...@gmail.com>; "paraview@paraview.org" ; >> "Woodring, Jonathan L" >> *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
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
This change is only in VTK in gerrit so you need to follow the directions there to check out the code and run the test. The directions are at http://review.source.kitware.com/#/t/1396/ I'm not sure why paraview is crashing though. I'll check on that. andy On Fri, Oct 26, 2012 at 5:06 PM, Sohail Shafii wrote: > Current master version can't launch (MacOS Mountain Lion): > > paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: > pointer being freed was not allocated > *** set a breakpoint in malloc_error_break to debug > > Program received signal SIGABRT, Aborted. > 0x7fff82432212 in __pthread_kill () > (gdb) bt 14 > #0 0x7fff82432212 in __pthread_kill () > #1 0x7fff87964af4 in pthread_kill () > #2 0x7fff879a8dce in abort () > #3 0x7fff8797c959 in free () > #4 0x7fff5fc0762a in > __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ > () > #5 0x7fff5fc0f06b in > __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () > #6 0x7fff5fc04ce4 in > __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () > #7 0x7fff5fc0a81a in __dyld_dlopen () > #8 0x7fff8ac96dd8 in dlopen () > #9 0x7fff83dcfa10 in gfxInitializeLibrary () > #10 0x00011e6014fe in gliInitializeLibrary () > #11 0x7fff8a4f63e6 in glcPluginCount () > #12 0x7fff8a4f62a8 in glcPluginCount () > #13 0x7fff8a4f6091 in glcPluginCount () > (More stack frames follow...) > > > Which version of the master works, so that I can debug? > > Sohail > > > On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer wrote: > >> A beta version will be released by mid-November. In order for the desired >> changes to make it in to that, the VTK part that's waiting your changes >> needs to go in early next week so that I can make the changes to ParaView >> to enable the WindBlade reader when running in either built-in mode or >> connecting to a serial server. >> >> Andy >> >> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii >> wrote: >> >>> >>> Haven't had a chance yet due to a paper. I'll look at it this week. How >>> soon will it be released? >>> >>> Also please respond to my sssha...@ucdavis.edu as this address is not >>> on the paraview list anymore. >>> >>> Sohail >>> >>> ------------------ >>> *From:* Andy Bauer >>> *To:* Sohail Shafii >>> *Cc:* David E DeMarle ; "migic...@gmail.com" < >>> migic...@gmail.com>; "paraview@paraview.org" ; >>> "Woodring, Jonathan L" >>> *Sent:* Wednesday, October 24, 2012 8:09 AM >>> >>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind >>> blade reader >>> >>> Hi Sohail, >>> >>> Did you get a chance to look at the warnings for the >>> vtkIOGeometryCxx-TestWindBladeReader test for the >>> http://review.source.kitware.com/#/t/1396/ gerrit topic? It's going to >>> need to be fixed pretty soon if it's going to make it into the ParaView 4.0 >>> release. >>> >>> Thanks, >>> Andy >>> >>> On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer wrote: >>> >>> It's available with "git clone git://vtk.org/VTKLargeData.gitVTKLargeData". >>> It's in the Data/WindBladeReader subdirectory there. >>> >>> On Wed, Oct 3, 2012 at 6:27 PM, Sohail Shafii wrote: >>> >>> 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 >>> *To:* David E DeMarle >>> *Cc:* Sohail Shafii ; "migic...@gmail.com" < >>> migic...@gmail.com>; "paraview@paraview.org" ; >>> "Woodring, Jonathan L" >>> *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 t
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Well you probably know already, but I won't be able to make the changes right now. I have a submission due this Friday. The reader still works for newer data sets but fails for the outdated one that you guys use for testing. So the fixes will have to come later. On Fri, Oct 26, 2012 at 2:39 PM, Andy Bauer wrote: > This change is only in VTK in gerrit so you need to follow the directions > there to check out the code and run the test. The directions are at > http://review.source.kitware.com/#/t/1396/ > > I'm not sure why paraview is crashing though. I'll check on that. > > andy > > > On Fri, Oct 26, 2012 at 5:06 PM, Sohail Shafii wrote: > >> Current master version can't launch (MacOS Mountain Lion): >> >> paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: >> pointer being freed was not allocated >> *** set a breakpoint in malloc_error_break to debug >> >> Program received signal SIGABRT, Aborted. >> 0x7fff82432212 in __pthread_kill () >> (gdb) bt 14 >> #0 0x7fff82432212 in __pthread_kill () >> #1 0x7fff87964af4 in pthread_kill () >> #2 0x7fff879a8dce in abort () >> #3 0x7fff8797c959 in free () >> #4 0x7fff5fc0762a in >> __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ >> () >> #5 0x7fff5fc0f06b in >> __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () >> #6 0x7fff5fc04ce4 in >> __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () >> #7 0x7fff5fc0a81a in __dyld_dlopen () >> #8 0x7fff8ac96dd8 in dlopen () >> #9 0x7fff83dcfa10 in gfxInitializeLibrary () >> #10 0x00011e6014fe in gliInitializeLibrary () >> #11 0x7fff8a4f63e6 in glcPluginCount () >> #12 0x7fff8a4f62a8 in glcPluginCount () >> #13 0x7fff8a4f6091 in glcPluginCount () >> (More stack frames follow...) >> >> >> Which version of the master works, so that I can debug? >> >> Sohail >> >> >> On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer wrote: >> >>> A beta version will be released by mid-November. In order for the >>> desired changes to make it in to that, the VTK part that's waiting your >>> changes needs to go in early next week so that I can make the changes to >>> ParaView to enable the WindBlade reader when running in either built-in >>> mode or connecting to a serial server. >>> >>> Andy >>> >>> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii >>> wrote: >>> >>>> >>>> Haven't had a chance yet due to a paper. I'll look at it this week. How >>>> soon will it be released? >>>> >>>> Also please respond to my sssha...@ucdavis.edu as this address is not >>>> on the paraview list anymore. >>>> >>>> Sohail >>>> >>>> -- >>>> *From:* Andy Bauer >>>> *To:* Sohail Shafii >>>> *Cc:* David E DeMarle ; "migic...@gmail.com" >>>> ; "paraview@paraview.org" ; >>>> "Woodring, Jonathan L" >>>> *Sent:* Wednesday, October 24, 2012 8:09 AM >>>> >>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a wind >>>> blade reader >>>> >>>> Hi Sohail, >>>> >>>> Did you get a chance to look at the warnings for the >>>> vtkIOGeometryCxx-TestWindBladeReader test for the >>>> http://review.source.kitware.com/#/t/1396/ gerrit topic? It's going to >>>> need to be fixed pretty soon if it's going to make it into the ParaView 4.0 >>>> release. >>>> >>>> Thanks, >>>> Andy >>>> >>>> On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer wrote: >>>> >>>> It's available with "git clone git://vtk.org/VTKLargeData.gitVTKLargeData". >>>> It's in the Data/WindBladeReader subdirectory there. >>>> >>>> On Wed, Oct 3, 2012 at 6:27 PM, Sohail Shafii >>>> wrote: >>>> >>>> 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 >>>> >>>> -- >>>> *
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
We're getting ready for a pre-release of PV 4.0 now so we'll need this soon. If we need to update to a newer WindBlade file for the test, we can do that too. You'll have to think though on how to handle backwards compatibility. Andy On Wed, Oct 31, 2012 at 12:37 PM, Sohail Shafii wrote: > Well you probably know already, but I won't be able to make the changes > right now. I have a submission due this Friday. The reader still works > for newer data sets but fails for the outdated one that you guys use for > testing. So the fixes will have to come later. > > > On Fri, Oct 26, 2012 at 2:39 PM, Andy Bauer wrote: > >> This change is only in VTK in gerrit so you need to follow the directions >> there to check out the code and run the test. The directions are at >> http://review.source.kitware.com/#/t/1396/ >> >> I'm not sure why paraview is crashing though. I'll check on that. >> >> andy >> >> >> On Fri, Oct 26, 2012 at 5:06 PM, Sohail Shafii wrote: >> >>> Current master version can't launch (MacOS Mountain Lion): >>> >>> paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: >>> pointer being freed was not allocated >>> *** set a breakpoint in malloc_error_break to debug >>> >>> Program received signal SIGABRT, Aborted. >>> 0x7fff82432212 in __pthread_kill () >>> (gdb) bt 14 >>> #0 0x7fff82432212 in __pthread_kill () >>> #1 0x7fff87964af4 in pthread_kill () >>> #2 0x7fff879a8dce in abort () >>> #3 0x7fff8797c959 in free () >>> #4 0x7fff5fc0762a in >>> __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ >>> () >>> #5 0x7fff5fc0f06b in >>> __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () >>> #6 0x7fff5fc04ce4 in >>> __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () >>> #7 0x7fff5fc0a81a in __dyld_dlopen () >>> #8 0x7fff8ac96dd8 in dlopen () >>> #9 0x7fff83dcfa10 in gfxInitializeLibrary () >>> #10 0x00011e6014fe in gliInitializeLibrary () >>> #11 0x7fff8a4f63e6 in glcPluginCount () >>> #12 0x7fff8a4f62a8 in glcPluginCount () >>> #13 0x7fff8a4f6091 in glcPluginCount () >>> (More stack frames follow...) >>> >>> >>> Which version of the master works, so that I can debug? >>> >>> Sohail >>> >>> >>> On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer wrote: >>> >>>> A beta version will be released by mid-November. In order for the >>>> desired changes to make it in to that, the VTK part that's waiting your >>>> changes needs to go in early next week so that I can make the changes to >>>> ParaView to enable the WindBlade reader when running in either built-in >>>> mode or connecting to a serial server. >>>> >>>> Andy >>>> >>>> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii >>> > wrote: >>>> >>>>> >>>>> Haven't had a chance yet due to a paper. I'll look at it this week. >>>>> How soon will it be released? >>>>> >>>>> Also please respond to my sssha...@ucdavis.edu as this address is not >>>>> on the paraview list anymore. >>>>> >>>>> Sohail >>>>> >>>>> -- >>>>> *From:* Andy Bauer >>>>> *To:* Sohail Shafii >>>>> *Cc:* David E DeMarle ; "migic...@gmail.com" >>>>> ; "paraview@paraview.org" ; >>>>> "Woodring, Jonathan L" >>>>> *Sent:* Wednesday, October 24, 2012 8:09 AM >>>>> >>>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a >>>>> wind blade reader >>>>> >>>>> Hi Sohail, >>>>> >>>>> Did you get a chance to look at the warnings for the >>>>> vtkIOGeometryCxx-TestWindBladeReader test for the >>>>> http://review.source.kitware.com/#/t/1396/ gerrit topic? It's going >>>>> to need to be fixed pretty soon if it's going to make it into the ParaView >>>>> 4.0 release. >>>>> >>>>> Thanks, >>>>> Andy >>>>> >>>>> On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer wrote: >>>>> >>>>> It&#x
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
At this point the changes will have to wait, unfortunately. For the past two weeks I've been involved with a TopoInVis submission so I couldn't get around to it. I'll look at it this weekend. No need to wait for me. On Thu, Nov 1, 2012 at 10:29 AM, Andy Bauer wrote: > We're getting ready for a pre-release of PV 4.0 now so we'll need this > soon. If we need to update to a newer WindBlade file for the test, we can > do that too. You'll have to think though on how to handle backwards > compatibility. > > Andy > > > On Wed, Oct 31, 2012 at 12:37 PM, Sohail Shafii wrote: > >> Well you probably know already, but I won't be able to make the changes >> right now. I have a submission due this Friday. The reader still works >> for newer data sets but fails for the outdated one that you guys use for >> testing. So the fixes will have to come later. >> >> >> On Fri, Oct 26, 2012 at 2:39 PM, Andy Bauer wrote: >> >>> This change is only in VTK in gerrit so you need to follow the >>> directions there to check out the code and run the test. The directions are >>> at http://review.source.kitware.com/#/t/1396/ >>> >>> I'm not sure why paraview is crashing though. I'll check on that. >>> >>> andy >>> >>> >>> On Fri, Oct 26, 2012 at 5:06 PM, Sohail Shafii wrote: >>> >>>> Current master version can't launch (MacOS Mountain Lion): >>>> >>>> paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: >>>> pointer being freed was not allocated >>>> *** set a breakpoint in malloc_error_break to debug >>>> >>>> Program received signal SIGABRT, Aborted. >>>> 0x7fff82432212 in __pthread_kill () >>>> (gdb) bt 14 >>>> #0 0x7fff82432212 in __pthread_kill () >>>> #1 0x7fff87964af4 in pthread_kill () >>>> #2 0x7fff879a8dce in abort () >>>> #3 0x7fff8797c959 in free () >>>> #4 0x7fff5fc0762a in >>>> __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ >>>> () >>>> #5 0x7fff5fc0f06b in >>>> __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () >>>> #6 0x7fff5fc04ce4 in >>>> __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () >>>> #7 0x7fff5fc0a81a in __dyld_dlopen () >>>> #8 0x7fff8ac96dd8 in dlopen () >>>> #9 0x7fff83dcfa10 in gfxInitializeLibrary () >>>> #10 0x00011e6014fe in gliInitializeLibrary () >>>> #11 0x7fff8a4f63e6 in glcPluginCount () >>>> #12 0x7fff8a4f62a8 in glcPluginCount () >>>> #13 0x7fff8a4f6091 in glcPluginCount () >>>> (More stack frames follow...) >>>> >>>> >>>> Which version of the master works, so that I can debug? >>>> >>>> Sohail >>>> >>>> >>>> On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer wrote: >>>> >>>>> A beta version will be released by mid-November. In order for the >>>>> desired changes to make it in to that, the VTK part that's waiting your >>>>> changes needs to go in early next week so that I can make the changes to >>>>> ParaView to enable the WindBlade reader when running in either built-in >>>>> mode or connecting to a serial server. >>>>> >>>>> Andy >>>>> >>>>> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii < >>>>> sohailsha...@yahoo.com> wrote: >>>>> >>>>>> >>>>>> Haven't had a chance yet due to a paper. I'll look at it this week. >>>>>> How soon will it be released? >>>>>> >>>>>> Also please respond to my sssha...@ucdavis.edu as this address is >>>>>> not on the paraview list anymore. >>>>>> >>>>>> Sohail >>>>>> >>>>>> -- >>>>>> *From:* Andy Bauer >>>>>> *To:* Sohail Shafii >>>>>> *Cc:* David E DeMarle ; "migic...@gmail.com" >>>>>> ; "paraview@paraview.org" ; >>>>>> "Woodring, Jonathan L" >>>>>> *Sent:* Wednesday, October 24, 2012 8:09 AM >>>>>> >>>>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a >>
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Also I'm removing Jimmy from this list since he may not be working with wind files at this point. Sohail On Sat, Nov 3, 2012 at 1:15 PM, Sohail Shafii wrote: > At this point the changes will have to wait, unfortunately. For the past > two weeks I've been involved with a TopoInVis submission so I couldn't get > around to it. I'll look at it this weekend. No need to wait for me. > > > On Thu, Nov 1, 2012 at 10:29 AM, Andy Bauer wrote: > >> We're getting ready for a pre-release of PV 4.0 now so we'll need this >> soon. If we need to update to a newer WindBlade file for the test, we can >> do that too. You'll have to think though on how to handle backwards >> compatibility. >> >> Andy >> >> >> On Wed, Oct 31, 2012 at 12:37 PM, Sohail Shafii wrote: >> >>> Well you probably know already, but I won't be able to make the changes >>> right now. I have a submission due this Friday. The reader still works >>> for newer data sets but fails for the outdated one that you guys use for >>> testing. So the fixes will have to come later. >>> >>> >>> On Fri, Oct 26, 2012 at 2:39 PM, Andy Bauer wrote: >>> >>>> This change is only in VTK in gerrit so you need to follow the >>>> directions there to check out the code and run the test. The directions are >>>> at http://review.source.kitware.com/#/t/1396/ >>>> >>>> I'm not sure why paraview is crashing though. I'll check on that. >>>> >>>> andy >>>> >>>> >>>> On Fri, Oct 26, 2012 at 5:06 PM, Sohail Shafii wrote: >>>> >>>>> Current master version can't launch (MacOS Mountain Lion): >>>>> >>>>> paraview(575,0x7fff72e33180) malloc: *** error for object 0x111058450: >>>>> pointer being freed was not allocated >>>>> *** set a breakpoint in malloc_error_break to debug >>>>> >>>>> Program received signal SIGABRT, Aborted. >>>>> 0x7fff82432212 in __pthread_kill () >>>>> (gdb) bt 14 >>>>> #0 0x7fff82432212 in __pthread_kill () >>>>> #1 0x7fff87964af4 in pthread_kill () >>>>> #2 0x7fff879a8dce in abort () >>>>> #3 0x7fff8797c959 in free () >>>>> #4 0x7fff5fc0762a in >>>>> __dyld__ZN4dyldL12registerDOFsERKNSt3__16vectorIN11ImageLoader7DOFInfoENS0_9allocatorIS3_ >>>>> () >>>>> #5 0x7fff5fc0f06b in >>>>> __dyld__ZN11ImageLoader4linkERKNS_11LinkContextEbbRKNS_10RPathChainE () >>>>> #6 0x7fff5fc04ce4 in >>>>> __dyld__ZN4dyld4linkEP11ImageLoaderbRKNS0_10RPathChainE () >>>>> #7 0x7fff5fc0a81a in __dyld_dlopen () >>>>> #8 0x7fff8ac96dd8 in dlopen () >>>>> #9 0x7fff83dcfa10 in gfxInitializeLibrary () >>>>> #10 0x00011e6014fe in gliInitializeLibrary () >>>>> #11 0x7fff8a4f63e6 in glcPluginCount () >>>>> #12 0x7fff8a4f62a8 in glcPluginCount () >>>>> #13 0x7fff8a4f6091 in glcPluginCount () >>>>> (More stack frames follow...) >>>>> >>>>> >>>>> Which version of the master works, so that I can debug? >>>>> >>>>> Sohail >>>>> >>>>> >>>>> On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer >>>>> wrote: >>>>> >>>>>> A beta version will be released by mid-November. In order for the >>>>>> desired changes to make it in to that, the VTK part that's waiting your >>>>>> changes needs to go in early next week so that I can make the changes to >>>>>> ParaView to enable the WindBlade reader when running in either built-in >>>>>> mode or connecting to a serial server. >>>>>> >>>>>> Andy >>>>>> >>>>>> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii < >>>>>> sohailsha...@yahoo.com> wrote: >>>>>> >>>>>>> >>>>>>> Haven't had a chance yet due to a paper. I'll look at it this week. >>>>>>> How soon will it be released? >>>>>>> >>>>>>> Also please respond to my sssha...@ucdavis.edu as this address is >>>>>>> not on the paraview list anymore. >>>>>>> >>>>>>> Sohail >>
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
aderbRKNS0_10RPathChainE () >>>>>> #7 0x7fff5fc0a81a in __dyld_dlopen () >>>>>> #8 0x7fff8ac96dd8 in dlopen () >>>>>> #9 0x7fff83dcfa10 in gfxInitializeLibrary () >>>>>> #10 0x00011e6014fe in gliInitializeLibrary () >>>>>> #11 0x7fff8a4f63e6 in glcPluginCount () >>>>>> #12 0x7fff8a4f62a8 in glcPluginCount () >>>>>> #13 0x7fff8a4f6091 in glcPluginCount () >>>>>> (More stack frames follow...) >>>>>> >>>>>> >>>>>> Which version of the master works, so that I can debug? >>>>>> >>>>>> Sohail >>>>>> >>>>>> >>>>>> On Wed, Oct 24, 2012 at 10:04 AM, Andy Bauer >>>>>> wrote: >>>>>> >>>>>>> A beta version will be released by mid-November. In order for the >>>>>>> desired changes to make it in to that, the VTK part that's waiting your >>>>>>> changes needs to go in early next week so that I can make the changes to >>>>>>> ParaView to enable the WindBlade reader when running in either built-in >>>>>>> mode or connecting to a serial server. >>>>>>> >>>>>>> Andy >>>>>>> >>>>>>> On Wed, Oct 24, 2012 at 12:13 PM, Sohail Shafii < >>>>>>> sohailsha...@yahoo.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> Haven't had a chance yet due to a paper. I'll look at it this week. >>>>>>>> How soon will it be released? >>>>>>>> >>>>>>>> Also please respond to my sssha...@ucdavis.edu as this address is >>>>>>>> not on the paraview list anymore. >>>>>>>> >>>>>>>> Sohail >>>>>>>> >>>>>>>> -- >>>>>>>> *From:* Andy Bauer >>>>>>>> *To:* Sohail Shafii >>>>>>>> *Cc:* David E DeMarle ; " >>>>>>>> migic...@gmail.com" ; "paraview@paraview.org" < >>>>>>>> paraview@paraview.org>; "Woodring, Jonathan L" >>>>>>>> *Sent:* Wednesday, October 24, 2012 8:09 AM >>>>>>>> >>>>>>>> *Subject:* Re: [Paraview] ParaView thinks that it does not have a >>>>>>>> wind blade reader >>>>>>>> >>>>>>>> Hi Sohail, >>>>>>>> >>>>>>>> Did you get a chance to look at the warnings for the >>>>>>>> vtkIOGeometryCxx-TestWindBladeReader test for the >>>>>>>> http://review.source.kitware.com/#/t/1396/ gerrit topic? It's >>>>>>>> going to need to be fixed pretty soon if it's going to make it into the >>>>>>>> ParaView 4.0 release. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Andy >>>>>>>> >>>>>>>> On Wed, Oct 3, 2012 at 10:22 PM, Andy Bauer >>>>>>> > wrote: >>>>>>>> >>>>>>>> It's available with "git clone >>>>>>>> git://vtk.org/VTKLargeData.gitVTKLargeData". >>>>>>>> It's in the Data/WindBladeReader subdirectory there. >>>>>>>> >>>>>>>> On Wed, Oct 3, 2012 at 6:27 PM, Sohail Shafii < >>>>>>>> sohailsha...@yahoo.com> wrote: >>>>>>>> >>>>>>>> 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 >>>>>>>> *To:* David E DeMarle >>>>>>>> *Cc:* Sohail Shafii ; "migic...@gmail.com"
Re: [Paraview] ParaView thinks that it does not have a wind blade reader
Thanks for the help.
On Sunday, January 20, 2013, Andy Bauer wrote:
> FYI: this finally has made its way into ParaView such that it will be
> available in the GUI for single process runs.
>
> Andy
>
> On Thu, Dec 20, 2012 at 8:08 PM, Sohail Shafii wrote:
>
> Thanks. Please take your time. If there any other problems with this
> reader then feel free to consult me.
>
> 1) typically I make a separate build directory for VTK or ParaView. The
> test I ran looked for "../../../../vtkData" or something like that, so it
> seems like the test executable has to be four directories deep. So I guess
> there is a common parent to the data folders and paraview, not sure what
> this parent would be or if there is a reference for this hierarchy.
>
> 2) I guess in this case I would have to experiment when I do make the
> switch to the newer VTK
>
>
> On Thu, Dec 20, 2012 at 9:45 AM, Andy Bauer wrote:
>
> Hi Sohail,
>
> Changing the number of fields from 23 to 16 fixed the warnings. I'll get
> these changes into VTK and then change ParaView so that it can read in
> WindBlade files with a single process. That may take a week or so though.
>
> As for the other questions:
>
> 1) If the data directories are called VTKData, VTKLargeData, and
> ParaViewData and they share the same parent directory as VTK or ParaView,
> when you build VTK or ParaView it will automatically pick up the path to
> each of them.
>
> 2) For the library names, after modularization they've been changed and
> relocated from the bin subdirectory to the lib subdirectory. Many of the
> old libraries have been subdivided into better organized libraries. I don't
> know any specific document that specifies what to do for this though.
>
> Andy
>
>
> On Sun, Dec 16, 2012 at 9:39 PM, Sohail Shafii wrote:
>
> I have some time now, so I addressed the issue. I don't the code has a
> problem; the problem is related to the .wind file.
>
> Near the bottom, it describes how many fields exist in the comp.out files
> ("DATA_VARIABLES"). For your test data, each file is about 64.5 MB. The
> .wind says that each file should have 23 fields. For n scalar fields, 1 is
> reserved for UVW; (n-1) for scalar data. So for this one, 1 for UWV while
> 22 for scalar data.
>
> The UVW block is about 10 MB (160x80x70x(4 bytes)x(3 components)); each
> scalar field is about 3.6 MB (160x80x70x(4 bytes)). So 10 MB + 22 scalar
> fields*3.6 gives you about 90 MB. That's way too big compared to the
> actual sizes of the comp.out files that you guys have for testing. * The
> test works when you reduce the "DATA_VARIABLES" item from 23 to 16*(which
> will give you close to 64.5 MB).
>
> I'm not sure why this .wind file is bad. Maybe older wind blade readers
> just ignored errors like these. Anyway, the test seems to launch a window
> and close right away. I didn't see any other errors after I fixed the wind
> file that I am using.
>
> A couple of questions:
> 1. How do you organize the VTK build directory with the testdata? The VTK
> tests seem to expect the data to be four directories UP the hierarchy, so I
> had to place my vtkData directory in my home folder.
> 2. I tried the new versions of VTK with QT and it appears that the -l
> commands that I put in the .pro file for linking (i.e. -lvtkIO) don't seem
> to work...is there a document somewhere that helps in this regard? I
> reverted to an older version of VTK for now but I want to eventually
> upgrade.
>
> Sohail
>
>
> On Sat, Nov 3, 2012 at 1:16 PM, Sohail Shafii wrote:
>
> Also I'm removing Jimmy from this list since he may not be working with
> wind files at this point.
>
> Sohail
>
>
> On Sat, Nov
>
>
___
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
