[Paraview] pvserver test on different systems (UNCLASSIFIED)

[Su, Simon M CTR USARMY ARL (US)]

Utkarsh,

thank you for your explanations. So, 

paraview --script=sample.py 
this will test to see if the python within ParaView

pvpython sample.py
pvbatch sample.py

than what will the above two tests show? If paraview --script=sample.py  test is a successful test, can we also assume that  pvpython and pvbatch test will also work?

So for individual python packages, I will need to do the import test for all the packages I want to test in the script right? Yes I have matplotlib enabled and that's why numpy is still there when I turn it off. Thanks...

thanks again for your help
-simon

________________________________________
From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com]
Sent: Sunday, October 26, 2014 12:16 PM
To: Su, Simon M CTR USARMY ARL (US)
Cc: paraview at paraview.org
Subject: Re: [Paraview] pvserver test on different systems (UNCLASSIFIED)

Simon,

> is running, will that also test the ParaView binary we produced has a working
> python within the ParaView?

No. For that, you can run paraview executable and have it run the
script on launch instead:

     paraview --script=sample.py

> What about checking and see if numpy is available
> for the ParaView binary produced?

Yes, you should do something like the following:

     import numpy
     print numpy.version.version

Same is true for other packages like matplotlib. The API to check the
version will of course be different with each.

> I even tried to turn off the numpy library
> (in the superbuild compile using the cmake flag -DENABLE_numpy=OFF) but the
> compilation process compiled numpy nevertheless.

The only component in the ParaView superbuild that depends directly on
numpy is matplotlib. Is that enabled? If so, it will automatically
enable numpy as well. You'll need to turn both off  to disable numpy
entirely from the build.

Utkarsh