[Paraview] Starting ParaViewWeb from a web application

[Pawel Kwiecien]

Hi all,
I'm exploring ParaViewWeb included in ParaView 4.0. As described in the
documentation (http://www.paraview.org/Wiki/ParaViewWeb), I can run it
locally like that


./bin/pvpython lib/site-packages/paraview/web/pv_web_visualizer.py
--content www --port 8080 --data-dir $PARAVIEW_DATA

My question would be: how to embed ParaViewWeb in my web application? Is it
possible to start pvpython dynamically?

As an example, user clicks a button and a ParaView visualization should be
loaded.

Thank you very much in advance for your help.

All the best,
Pawel
___
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] My own filter as part of pipeline for coprocessing raises name not defined error

[Andy Bauer]

Hi Hong,

There won't be a separate library created for Python wrapping your plugin
for doing ParaView. Did you add in the following to your adaptor:

#ifndef BUILD_SHARED_LIBS
#include pvStaticPluginsInit.h
#endif

And then in the adaptor initialization step you should have something in it
like:
#ifndef BUILD_SHARED_LIBS
paraview_static_plugins_init();
#endif

If that doesn't work then it will probably take a bit of tinkering to
figure out what's wrong.

Regards,
Andy








On Wed, Oct 2, 2013 at 12:28 PM, Hong Yi hon...@renci.org wrote:

  Thanks for the helpful info, Andy. I looked at the link and followed the
 code change Burlen posted to add the static linked plugin initialization
 into pvbatch and pvpython and that worked fine. Now pvbatch and pypthon all
 have my filter plugin statically loaded. I still got the “name not defined”
 error when coprocessing parses the pipeline though. I believe the problem
 remains because there is still no python wrapped proxy to my filter since
 there is no change to lib\site-packages after I add the static linked
 plugin initialization into pybatch and pvpython. To make sure I am on the
 right track for my further investigation, I am hoping to get answers to a
 couple of my further questions below:

 ** **

 **1.   **What is the right way to go to have the proxy to my filter
 Python wrapped? How can I verity I have the proxy to my filter Python
 wrapped? Is it true that the Python-wrapped proxy to my filter should show
 up in some python file in lib\site-packages if the filter is indeed
 python-wrapped?  

 **2.   **I made similar changes to CPythonAdaptorAPI.cxx and
 CMakeLists.txt as I did to pvpthon and pvbatch to load and init static
 plugin in function coprocessorinitializewithpython() hoping to have plugin
 loaded when doing coprocessing linked to simulation, however, I still have
 the symbol “pv_plugin_instance_SMVorticity” undefined in built
 PythonCatalyst static lib while the plugin symbol is indeed defined in
 pvpython with the same code changes. Just to confirm, does the plugin need
 to be loaded in Catalyst initialization in order to use it in a
 coprocessing pipeline? In other words, to get my plugin working in catalyst
 linked to simulation, I need to resolve two problems: (1) get the plugin
 statically loaded in Catalyst initialization; (2) get the proxy to the
 plugin Python wrapped and show up in some python file in lib\site-packages.
 Is this true?

 ** **

 Yes, I know the gradient of unstructured data set filter can compute
 vorticity, which I referenced to write this custom vorticity filter to make
 it fit our needs better with better performance. I did try to use the
 genetic gradient filter to compute vorticity for coprocessing, but it
 raises a segmentation fault after outputting several images. Will have to
 debug and investigate more to find out more on that.

 ** **

 Thanks,

 Hong

 

 ** **

 *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
 *Sent:* Tuesday, October 01, 2013 2:19 PM

 *To:* Hong Yi
 *Cc:* David E DeMarle; paraview@paraview.org
 *Subject:* Re: [Paraview] My own filter as part of pipeline for
 coprocessing raises name not defined error

 ** **

 Hi Hong,

 I don't think you want to do VTK Python wrapping of your class. What you
 want is to have the proxy to the filter Python wrapped such that it's
 available when you import paraview.simple. This is what's needed for
 Catalyst Python pipelines. I don't think you're properly initializing the
 plugins from the previous directions I sent. You may want to look at
 http://public.kitware.com/pipermail/paraview-developers/2013-September/002499.html
 

 As a side note, the gradient of unstructured data set filter can compute
 vorticity as well. It does require a vtkDataArray with three components to
 use though. 

 Regards,
 Andy

 ** **

 On Mon, Sep 30, 2013 at 5:06 PM, Hong Yi hon...@renci.org wrote:

 Thanks, Andy. The CMakeLists.txt for my plugin is copied below with newly
 added lines for python wrapping in orange:

 -
 if(NOT ParaView_SOURCE_DIR)
   find_package(ParaView)
   include(${PARAVIEW_USE_FILE})
   include (ParaViewPlugins)
 else()
   # we're building from within ParaView Source.
 endif()

 include_directories(${VTK_INCLUDE_DIRS})
 include(wrap-python.cmake)

 # create a paraview plugin containing server manager xml and the server
 # manager classes to build
 # this plugin can be loaded on the server side

 ADD_PARAVIEW_PLUGIN(SMVorticity 1.0
   SERVER_MANAGER_XML VorticityFilter.xml
   SERVER_MANAGER_SOURCES VorticityFilter.cxx)

 target_link_libraries(SMVorticity ${deps})

 if(VTK_WRAP_PYTHON)
   wrap_python(SMVorticity ${sources})
 endif()
 -

 The orange lines are added by following
 http://www.paraview.org/pipermail/paraview/2012-May/024855.html which
 works well and builds my filter and also wraps it in Python (i.e., it
 generates 

Re: [Paraview] My own filter as part of pipeline for coprocessing raises name not defined error

[Hong Yi]

Hi Andy,

That is exactly what I did, and I also modified CMakeLists.txt to link 
${PARAVIEW_PLUGINLIST}  to the target via target_link_libraries. However, the 
symbol pv_plugin_instance_SMVorticity is undefined in the built target static 
library, while following the same process to build pvbatch and pvpython 
executable works, i.e., the same plugin symbol is defined in built pvpython 
executable. Since it is static linking, I know linking order matters, but have 
not got it to work by adjusting linking orders. Let me know if you have ideas 
on what I could try to figure out and resolve this issue.

Thanks,

Hong


From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Thursday, October 03, 2013 10:19 AM
To: Hong Yi
Cc: David E DeMarle; paraview@paraview.org
Subject: Re: [Paraview] My own filter as part of pipeline for coprocessing 
raises name not defined error

Hi Hong,
There won't be a separate library created for Python wrapping your plugin for 
doing ParaView. Did you add in the following to your adaptor:
#ifndef BUILD_SHARED_LIBS
#include pvStaticPluginsInit.h
#endif

And then in the adaptor initialization step you should have something in it 
like:
#ifndef BUILD_SHARED_LIBS
paraview_static_plugins_init();
#endif

If that doesn't work then it will probably take a bit of tinkering to figure 
out what's wrong.

Regards,
Andy




On Wed, Oct 2, 2013 at 12:28 PM, Hong Yi 
hon...@renci.orgmailto:hon...@renci.org wrote:
Thanks for the helpful info, Andy. I looked at the link and followed the code 
change Burlen posted to add the static linked plugin initialization into 
pvbatch and pvpython and that worked fine. Now pvbatch and pypthon all have my 
filter plugin statically loaded. I still got the name not defined error when 
coprocessing parses the pipeline though. I believe the problem remains because 
there is still no python wrapped proxy to my filter since there is no change to 
lib\site-packages after I add the static linked plugin initialization into 
pybatch and pvpython. To make sure I am on the right track for my further 
investigation, I am hoping to get answers to a couple of my further questions 
below:


1.   What is the right way to go to have the proxy to my filter Python 
wrapped? How can I verity I have the proxy to my filter Python wrapped? Is it 
true that the Python-wrapped proxy to my filter should show up in some python 
file in lib\site-packages if the filter is indeed python-wrapped?

2.   I made similar changes to CPythonAdaptorAPI.cxx and CMakeLists.txt as 
I did to pvpthon and pvbatch to load and init static plugin in function 
coprocessorinitializewithpython() hoping to have plugin loaded when doing 
coprocessing linked to simulation, however, I still have the symbol 
pv_plugin_instance_SMVorticity undefined in built PythonCatalyst static lib 
while the plugin symbol is indeed defined in pvpython with the same code 
changes. Just to confirm, does the plugin need to be loaded in Catalyst 
initialization in order to use it in a coprocessing pipeline? In other words, 
to get my plugin working in catalyst linked to simulation, I need to resolve 
two problems: (1) get the plugin statically loaded in Catalyst initialization; 
(2) get the proxy to the plugin Python wrapped and show up in some python file 
in lib\site-packages. Is this true?

Yes, I know the gradient of unstructured data set filter can compute vorticity, 
which I referenced to write this custom vorticity filter to make it fit our 
needs better with better performance. I did try to use the genetic gradient 
filter to compute vorticity for coprocessing, but it raises a segmentation 
fault after outputting several images. Will have to debug and investigate more 
to find out more on that.

Thanks,
Hong

From: Andy Bauer [mailto:andy.ba...@kitware.commailto:andy.ba...@kitware.com]
Sent: Tuesday, October 01, 2013 2:19 PM

To: Hong Yi
Cc: David E DeMarle; paraview@paraview.orgmailto:paraview@paraview.org
Subject: Re: [Paraview] My own filter as part of pipeline for coprocessing 
raises name not defined error

Hi Hong,
I don't think you want to do VTK Python wrapping of your class. What you want 
is to have the proxy to the filter Python wrapped such that it's available when 
you import paraview.simple. This is what's needed for Catalyst Python 
pipelines. I don't think you're properly initializing the plugins from the 
previous directions I sent. You may want to look at 
http://public.kitware.com/pipermail/paraview-developers/2013-September/002499.html
As a side note, the gradient of unstructured data set filter can compute 
vorticity as well. It does require a vtkDataArray with three components to use 
though.
Regards,
Andy

On Mon, Sep 30, 2013 at 5:06 PM, Hong Yi 
hon...@renci.orgmailto:hon...@renci.org wrote:
Thanks, Andy. The CMakeLists.txt for my plugin is copied below with newly added 
lines for python wrapping in orange:

-
if(NOT ParaView_SOURCE_DIR)
  find_package(ParaView)
  

Re: [Paraview] My own filter as part of pipeline for coprocessing raises name not defined error

[Andy Bauer]

Hmm, I would check the link line for your adaptor and for creating the
executable to see if the plugin library is included there. Something else
you can try is explicitly create the plugin's filter in the adaptor code to
make sure that it is linked in properly.

Regards,
Andy


On Thu, Oct 3, 2013 at 10:41 AM, Hong Yi hon...@renci.org wrote:

  Hi Andy,

 ** **

 That is exactly what I did, and I also modified CMakeLists.txt to link
 ${PARAVIEW_PLUGINLIST}  to the target via target_link_libraries. However,
 the symbol “pv_plugin_instance_SMVorticity” is undefined in the built
 target static library, while following the same process to build pvbatch
 and pvpython executable works, i.e., the same plugin symbol is defined in
 built pvpython executable. Since it is static linking, I know linking order
 matters, but have not got it to work by adjusting linking orders. Let me
 know if you have ideas on what I could try to figure out and resolve this
 issue.

 ** **

 Thanks,

 ** **

 Hong

 ** **

 ** **

 *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
 *Sent:* Thursday, October 03, 2013 10:19 AM

 *To:* Hong Yi
 *Cc:* David E DeMarle; paraview@paraview.org
 *Subject:* Re: [Paraview] My own filter as part of pipeline for
 coprocessing raises name not defined error

 ** **

 Hi Hong,

 There won't be a separate library created for Python wrapping your plugin
 for doing ParaView. Did you add in the following to your adaptor:

 #ifndef BUILD_SHARED_LIBS

 #include pvStaticPluginsInit.h

 #endif


 And then in the adaptor initialization step you should have something in
 it like:

 #ifndef BUILD_SHARED_LIBS

 paraview_static_plugins_init();

 #endif

 If that doesn't work then it will probably take a bit of tinkering to
 figure out what's wrong.

 Regards,
 Andy

 ** **

 On Wed, Oct 2, 2013 at 12:28 PM, Hong Yi hon...@renci.org wrote:

 Thanks for the helpful info, Andy. I looked at the link and followed the
 code change Burlen posted to add the static linked plugin initialization
 into pvbatch and pvpython and that worked fine. Now pvbatch and pypthon all
 have my filter plugin statically loaded. I still got the “name not defined”
 error when coprocessing parses the pipeline though. I believe the problem
 remains because there is still no python wrapped proxy to my filter since
 there is no change to lib\site-packages after I add the static linked
 plugin initialization into pybatch and pvpython. To make sure I am on the
 right track for my further investigation, I am hoping to get answers to a
 couple of my further questions below:

  

 1.   What is the right way to go to have the proxy to my filter
 Python wrapped? How can I verity I have the proxy to my filter Python
 wrapped? Is it true that the Python-wrapped proxy to my filter should show
 up in some python file in lib\site-packages if the filter is indeed
 python-wrapped?  

 2.   I made similar changes to CPythonAdaptorAPI.cxx and
 CMakeLists.txt as I did to pvpthon and pvbatch to load and init static
 plugin in function coprocessorinitializewithpython() hoping to have plugin
 loaded when doing coprocessing linked to simulation, however, I still have
 the symbol “pv_plugin_instance_SMVorticity” undefined in built
 PythonCatalyst static lib while the plugin symbol is indeed defined in
 pvpython with the same code changes. Just to confirm, does the plugin need
 to be loaded in Catalyst initialization in order to use it in a
 coprocessing pipeline? In other words, to get my plugin working in catalyst
 linked to simulation, I need to resolve two problems: (1) get the plugin
 statically loaded in Catalyst initialization; (2) get the proxy to the
 plugin Python wrapped and show up in some python file in lib\site-packages.
 Is this true?

  

 Yes, I know the gradient of unstructured data set filter can compute
 vorticity, which I referenced to write this custom vorticity filter to make
 it fit our needs better with better performance. I did try to use the
 genetic gradient filter to compute vorticity for coprocessing, but it
 raises a segmentation fault after outputting several images. Will have to
 debug and investigate more to find out more on that.

  

 Thanks,

 Hong

  

 *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
 *Sent:* Tuesday, October 01, 2013 2:19 PM


 *To:* Hong Yi
 *Cc:* David E DeMarle; paraview@paraview.org
 *Subject:* Re: [Paraview] My own filter as part of pipeline for
 coprocessing raises name not defined error

  

 Hi Hong,

 I don't think you want to do VTK Python wrapping of your class. What you
 want is to have the proxy to the filter Python wrapped such that it's
 available when you import paraview.simple. This is what's needed for
 Catalyst Python pipelines. I don't think you're properly initializing the
 plugins from the previous directions I sent. You may want to look at
 

[Paraview] Null Scalar Value

[Léo Pessanha]

I think it`s a simple question...


I have a scalar value(point_data) between -0.5 and 0.5 in vtk format files

I have some points without information

I would like to put something like '' NULL '' value in this points, but i
can`t seem to find a way

I`ve tried 0 but its in the range of the information and that didnt work

Can anybody help me?

Thanks in advance

Leonardo Pessanha,
Rio de Janeiro - Brasil
___
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] NEK5000 with ParaView

[Patrick O'Leary]

Dear Matteo,

NEK5000 file series is not supported in ParaView 3.98. This feature was
added in the Spring of 2013 and is available in ParaView 4.0. Are you able
to update to the current release?

Regards,
Patrick


On Wed, Oct 2, 2013 at 9:44 AM, Matteo Righi mteo.ri...@gmail.com wrote:

 Dear all,
 I'm trying to use ParaView 3.98 in order to visualize the results of a
 Nek5000 simulation.
 Starting from the output files .fld, I first create the metatada file
 .nek5000.
 When I open this file in Paraview 3.98 all the .fld files are loaded, but
 the problem is that I can see only the first of these files, while the
 others are not visualized. In practice, looking at the time box in the
 information box, the first file has index 0 and a value different from 0,
 while the other files have an index different from 0 (1,2,3,...) and the
 corresponding value equal to 0. So, when I press the start button, I can
 see only the first file and the simulation doesn't start.
 Can anyone explain me the procedure to solve this problem?
 Thanks a lot.

 Matteo


 ___
 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] Null Scalar Value

[Moreland, Kenneth]

Can you put a NaN value in these points?

-Ken

From: Léo Pessanha 
leonardopessanh...@gmail.commailto:leonardopessanh...@gmail.com
Date: Thursday, October 3, 2013 12:35 PM
To: paraview@paraview.orgmailto:paraview@paraview.org 
paraview@paraview.orgmailto:paraview@paraview.org
Subject: [EXTERNAL] [Paraview] Null Scalar Value

I think it`s a simple question...


I have a scalar value(point_data) between -0.5 and 0.5 in vtk format files

I have some points without information

I would like to put something like '' NULL '' value in this points, but i can`t 
seem to find a way

I`ve tried 0 but its in the range of the information and that didnt work

Can anybody help me?

Thanks in advance

Leonardo Pessanha,
Rio de Janeiro - Brasil
___
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] display bonds between atoms using paraview

[Jian Luo]

 
   
 
  ___
  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
 
   
 
   
 
   
 
   
 
  ** **
 
 -- next part --
 An HTML attachment was scrubbed...
 URL: 
 http://www.paraview.org/pipermail/paraview/attachments/20131003/9f68cf01/attachment.htm
 

 --

 ___
 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


 End of ParaView Digest, Vol 114, Issue 6
 

___
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