[Paraview] VTK ParaView 2-day course, 17-18 sept. 2012, Lyon, France

2012-08-27 Thread Philippe Pebay
Hello,

Kitware will be organizing a 2-day course on VTK and ParaView on 09/17 and
09/18 at the Lyon office in France.
*
**Goals:*
1. Understand and program a pipeline with VTK
2. Visualize 2D and 3D images and meshes using VTK
3. Become familiar with the ParaView parallel visualization application
4. Learn to handle and analyse data with ParaView
5. Use ParaView in parallel for distributed data

*Registration fees***:   One day:

   - 590€ HT
   - 490€ HT for students

 Two days

   - 990€ HT
   - 790€ HT for students

 *Additional Information*:
Program and goals for the course are available in pdf
format
.
The course will be taught in English.

Please do not hesitate to
contactus if you have any
question.

Thank you
Philippe


-- 
Philippe Pébay, PhD
Director of Visualization and High Performance Computing /
Directeur de la Visualisation et du Calcul Haute Performance
Kitware SAS
26 rue Louis Guérin, 69100 Villeurbanne, France
+33 (0) 6.83.61.55.70 / 4.37.45.04.15
http://www.kitware.fr 
___
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


[Paraview] Different pvbatch results when not on host

2012-08-27 Thread Joe Borġ
Different results for ViewSize when running on remote station.

See my test.py script.  If I run that on a localhost, then the image gets
made the correct size.  If I run this on a remote station (of exactly the
same spec and after setting the DISPLAY) I get a different size screenshot,
even though the image size is correct.


Regards,
Joseph David Borġ
http://www.jdborg.com


test.py
Description: Binary data
___
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


[Paraview] Make array calculator operate on field data AND Field data is not maintained after some filters

2012-08-27 Thread Felipe Bordeu

Hello,

I work mainly with XDMF files in ParaView in a daily bases, and I 
normally add some field data to store global data (like material 
properties or extra model parameters).


The problem:
1) Some filters like the 3D filter do not pass the field data to the output.
2) I need to calculate some quantities using the field data and point 
data, so I need to have access to that data in the calculator.


I patched my version of ParaView (3.14 Linux 64) and put the code in the 
bug tracker 6 months ago, but nobody seems to care about it.


Please can someone look at the patches and tell me if is the good 
approach. And eventually commit the patches to the ParaView repository.


solution for 1)
http://paraview.org/Bug/view.php?id=10787
http://paraview.org/Bug/view.php?id=12777

solution for 2)
http://paraview.org/Bug/view.php?id=5626
http://paraview.org/Bug/view.php?id=12778

Thanks a lot.

--

Felipe Bordeu Weldt
Ingénieur de Recherche
-
Tél. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
felipe.bor...@ec-nantes.fr
Institut GeM - UMR CNRS 6183
École Centrale Nantes
1 Rue de La Noë, 44321 Nantes, FRANCE
-

___
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] Make array calculator operate on field data AND Field data is not maintained after some filters

2012-08-27 Thread Utkarsh Ayachit
We're on it. Thanks for the patches.

Utkarsh

On Mon, Aug 27, 2012 at 6:56 AM, Felipe Bordeu
 wrote:
> Hello,
>
> I work mainly with XDMF files in ParaView in a daily bases, and I normally
> add some field data to store global data (like material properties or extra
> model parameters).
>
> The problem:
> 1) Some filters like the 3D filter do not pass the field data to the output.
> 2) I need to calculate some quantities using the field data and point data,
> so I need to have access to that data in the calculator.
>
> I patched my version of ParaView (3.14 Linux 64) and put the code in the bug
> tracker 6 months ago, but nobody seems to care about it.
>
> Please can someone look at the patches and tell me if is the good approach.
> And eventually commit the patches to the ParaView repository.
>
> solution for 1)
> http://paraview.org/Bug/view.php?id=10787
> http://paraview.org/Bug/view.php?id=12777
>
> solution for 2)
> http://paraview.org/Bug/view.php?id=5626
> http://paraview.org/Bug/view.php?id=12778
>
> Thanks a lot.
>
> --
>
> Felipe Bordeu Weldt
> Ingénieur de Recherche
> -
> Tél. : 33 (0)2 40 37 16 57
> Fax. : 33 (0)2 40 74 74 06
> felipe.bor...@ec-nantes.fr
> Institut GeM - UMR CNRS 6183
> École Centrale Nantes
> 1 Rue de La Noë, 44321 Nantes, FRANCE
> -
>
> ___
> 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


[Paraview] Unlink a property from a GUI widget on a reader panel

2012-08-27 Thread Takuya OSHIMA
Hi,

I have a checkbox on my custom reader panel which is automatically
generated in connection with an IntVector boolean domain property from
the SM XML proxy definition, which is set to immediate_update. 

In order for checking/unchecking the checkbox to take effect in the
server side immediately without turning the Apply button to green, In
addition to setting the immediate_update attribute I unlink the
default property link and setup/take care of an alternative link by

  pqNamedWidgets::unlinkObject(regionNames, pqSMProxy(this->proxy()),
  "ShowRegionNames", this->propertyManager());
  this->Implementation->Links.addPropertyLink(regionNames, "checked",
  SIGNAL(toggled(bool)), this->proxy(), showRegionNames);
  this->Implementation->VTKConnect->Connect(showRegionNames,
  vtkCommand::ModifiedEvent, this, SLOT(onShowRegionNamesModified()));

where regonNames is the QCheckBox and showRegionNames is the
vtkSMIntVectorProperty. This has worked well with PV 3.14.1 and
earlier versions, but with the git-master the Apply button turns to
green when the checkbox is clicked. Is there a way to immediately push
the property to the server without changing the Apply button state for
the git-master?

Just as a side note, I tested commit
3bb4f74eff3f0670df5bef12c1e29b77b394a963 (Fix auto-apply with the new
properties panel) from the next branch but it did not help (unless
turning on Auto Accept in the general setting).

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
___
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] Python interpreter not being created for coprocessing?

2012-08-27 Thread Andy Bauer
Hi Mark,

With the modularization of VTK and ParaView the coprocessing tests were
temporarily in a bad state. The serial ones are fixed now (the parallel
runs but gives incorrect results for the screenshot). Is it possible for
you to update your version of ParaView and retry this?

Thanks,
Andy

On Fri, Aug 24, 2012 at 4:03 PM, Vanmoer, Mark W wrote:

>  Hi, I rebuilt with ParaViewData directory set and it’s only finding 1
> out 3 of the CoProcessing tests. Did I forget a step?
>
> ** **
>
> $ ctest --verbose --output-on-failure --output-log ctest.out -R CoProcess*
> ***
>
> ** **
>
> UpdateCTestConfiguration  from
> :/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
>
> Parse Config
> file:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
>
> UpdateCTestConfiguration  from
> :/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
>
> Parse Config
> file:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
>
> Test project /usr/apps/vis/ParaView/repo/withTesting
>
> Constructing a list of tests
>
> Done constructing a list of tests
>
> Checking test dependency graph...
>
> Checking test dependency graph end
>
> test 29
>
> Start  29: vtkCoProcessor-HeaderTest
>
> ** **
>
> 29: Test command: /usr/bin/python
> "/usr/apps/vis/ParaView/repo/ParaView/VTK/Testing/Core/HeaderTesting.py"
> "/usr/apps/vis/ParaView/repo/ParaView/CoProcessing/Core"
> "VTKCOPROCESSOR_EXPORT"
>
> 29: Test timeout computed to be: 1500
>
> 29: Use export macro: VTKCOPROCESSOR_EXPORT
>
> 1/3 Test  #29: vtkCoProcessor-HeaderTest    Passed0.37 sec
>
> test 100
>
> Start 100: CoProcessingTestPythonScript
>
> ** **
>
> 100: Test command: /usr/apps/vis/CMake/2.8.9/bin/cmake "-Dcfg=Release"
> "-P"
> "/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake"
> 
>
> 100: Test timeout computed to be: 1500
>
> 100: CMake Error at
> /usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake:6
> (message):
>
> 100:   
>
> 100:
> '/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
> 
>
> 100:   does not exist
>
> 100: 
>
> 100: 
>
> 2/3 Test #100: CoProcessingTestPythonScript .***Failed0.79 sec
>
> CMake Error at
> /usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake:6
> (message):
>
>   
>
>
>   
> '/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
> 
>
>   does not exist
>
> ** **
>
> ** **
>
> ** **
>
> test 101
>
> Start 101: PCoProcessingTestPythonScript
>
> ** **
>
> 101: Test command: /usr/apps/vis/CMake/2.8.9/bin/cmake "-Dcfg=Release"
> "-P"
> "/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake"
> 
>
> 101: Test timeout computed to be: 1500
>
> 101: CMake Error at
> /usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake:6
> (message):
>
> 101:   
>
> 101:
> '/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
> 
>
> 101:   does not exist
>
> 101: 
>
> 101: 
>
> 3/3 Test #101: PCoProcessingTestPythonScript ***Failed0.01 sec
>
> CMake Error at
> /usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake:6
> (message):
>
>   
>
>
>   
> '/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
> 
>
>   does not exist
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> The following tests passed:
>
> vtkCoProcessor-HeaderTest
>
> ** **
>
> 33% tests passed, 2 tests failed out of 3
>
> ** **
>
> Total Test time (real) =   8.14 sec
>
> ** **
>
> The following tests FAILED:
>
> 100 - CoProcessingTestPythonScript (Failed)
>
> 101 - PCoProcessingTestPythonScript (Failed)
>
> Errors while running CTest
>
> ** **
>
> Mark
>
> *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Sent:* Thursday, August 23, 2012 3:06 PM
>
> *To:* Vanmoer, Mark W
> *Cc:* paraview@paraview.org
> *Subject:* Re: [Paraview] Python interpreter not being created for
> coprocessing?
>
> ** **
>
> ** **
>
> On Thu, Aug 23, 2012 at 4:00 PM, Vanmoer, Mark W 
> wrote:
>
> Two questions – is there a way to tell ctest where the ParaViewData is
> without having to go back into cmake and rebuilding?
>
>
> Not possible for most, if not all, tests. The reason is that the test
> doesn't get added unless ParaViewData is available.
>  
>
>  And 2, is there a way to tell ctest to not use MPIEXEC_MAX_NUMPROCS when
> running tests?
>
>
> Many parallel tests, including the parallel

Re: [Paraview] Python interpreter not being created for coprocessing?

2012-08-27 Thread Vanmoer, Mark W
Hi Andy, I just did a fresh git clone and ccmake gives me
Make Error at VTK/CMake/vtkModuleTop.cmake:29 (message):
   No such module "vtkWrappingTools" needed by "vtkUtilitiesWrapClientServer"
Call Stack (most recent call first):
   VTK/CMake/vtkModuleTop.cmake:45 (vtk_module_check)
   VTK/CMake/vtkModuleTop.cmake:52 (vtk_module_check)
   VTK/CMakeLists.txt:334 (include)

Mark

From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Monday, August 27, 2012 11:59 AM
To: Vanmoer, Mark W
Cc: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?

Hi Mark,

With the modularization of VTK and ParaView the coprocessing tests were 
temporarily in a bad state. The serial ones are fixed now (the parallel runs 
but gives incorrect results for the screenshot). Is it possible for you to 
update your version of ParaView and retry this?

Thanks,
Andy
On Fri, Aug 24, 2012 at 4:03 PM, Vanmoer, Mark W 
mailto:mvanm...@illinois.edu>> wrote:
Hi, I rebuilt with ParaViewData directory set and it's only finding 1 out 3 of 
the CoProcessing tests. Did I forget a step?

$ ctest --verbose --output-on-failure --output-log ctest.out -R CoProcess

UpdateCTestConfiguration  from 
:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
Parse Config file:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
Parse Config file:/usr/apps/vis/ParaView/repo/withTesting/DartConfiguration.tcl
Test project /usr/apps/vis/ParaView/repo/withTesting
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 29
Start  29: vtkCoProcessor-HeaderTest

29: Test command: /usr/bin/python 
"/usr/apps/vis/ParaView/repo/ParaView/VTK/Testing/Core/HeaderTesting.py" 
"/usr/apps/vis/ParaView/repo/ParaView/CoProcessing/Core" "VTKCOPROCESSOR_EXPORT"
29: Test timeout computed to be: 1500
29: Use export macro: VTKCOPROCESSOR_EXPORT
1/3 Test  #29: vtkCoProcessor-HeaderTest    Passed0.37 sec
test 100
Start 100: CoProcessingTestPythonScript

100: Test command: /usr/apps/vis/CMake/2.8.9/bin/cmake "-Dcfg=Release" "-P" 
"/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake"
100: Test timeout computed to be: 1500
100: CMake Error at 
/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake:6
 (message):
100:
100:   
'/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
100:   does not exist
100:
100:
2/3 Test #100: CoProcessingTestPythonScript .***Failed0.79 sec
CMake Error at 
/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/CoProcessingTestPythonScript.cmake:6
 (message):

  
'/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
  does not exist



test 101
Start 101: PCoProcessingTestPythonScript

101: Test command: /usr/apps/vis/CMake/2.8.9/bin/cmake "-Dcfg=Release" "-P" 
"/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake"
101: Test timeout computed to be: 1500
101: CMake Error at 
/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake:6
 (message):
101:
101:   
'/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
101:   does not exist
101:
101:
3/3 Test #101: PCoProcessingTestPythonScript ***Failed0.01 sec
CMake Error at 
/usr/apps/vis/ParaView/repo/withTesting/CoProcessing/PCoProcessingTestPythonScript.cmake:6
 (message):

  
'/usr/apps/vis/ParaView/repo/withTesting/ThirdParty/protobuf/vtkprotobuf/bin/Release/CoProcessingPythonScriptExample.exe'
  does not exist




The following tests passed:
vtkCoProcessor-HeaderTest

33% tests passed, 2 tests failed out of 3

Total Test time (real) =   8.14 sec

The following tests FAILED:
100 - CoProcessingTestPythonScript (Failed)
101 - PCoProcessingTestPythonScript (Failed)
Errors while running CTest

Mark
From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Thursday, August 23, 2012 3:06 PM

To: Vanmoer, Mark W
Cc: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?


On Thu, Aug 23, 2012 at 4:00 PM, Vanmoer, Mark W 
mailto:mvanm...@illinois.edu>> wrote:
Two questions - is there a way to tell ctest where the ParaViewData is without 
having to go back into cmake and rebuilding?

Not possible for most, if not all, tests. The reason is that the test doesn't 
get added unless ParaViewData is available.

And 2, is there a way to tell ctest to not use MPIEXEC_MAX_NUMPROCS when 
running tests?

Many parallel tests, including the parallel coprocessing test, usually jus

Re: [Paraview] ParaView thinks that it does not have a wind blade reader

2012-08-27 Thread Sohail Shafii
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/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, Sohai

Re: [Paraview] ParaView thinks that it does not have a wind blade reader

2012-08-27 Thread Andy Bauer
On Mon, Aug 27, 2012 at 6:53 PM, Sohail Shafii  wrote:

> I see...so if MPI is running then it will create a parallel version 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 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