Hi Sven, What you did is what I was planning to do. Maybe cleaner, but that's it. So the end integration could be slightly different, but the core will be the same.
On a side note, we will never call a "Qt" code from Python. As we are note expecting the GUI to be build for ParaViewWeb. Seb On Mon, May 23, 2016 at 10:44 AM, Sven Kramer <svenkrame...@gmail.com> wrote: > Sure, I would share the code. But as I said, I haven't done anything more > than wrapping pqCatalystConnectReaction::connect() and hacking several > lines in the python rpc server, which are probably not done right. > If it helps, I can try to reconstruct all the lines I have modified and > clean up the stuff. However, you'll probably find a cleaner solution to > invoke pqCatalystConnectReaction::connect() from the web client. > > Sven > > 2016-05-23 7:22 GMT+02:00 Sebastien Jourdain < > sebastien.jourd...@kitware.com>: > >> Glad to ear that you managed to get something going. If you feel like >> sharing your code, we might be able to provide some integration into >> ParaView and/or ParaViewWeb proper. >> >> Seb >> >> On Sat, May 21, 2016 at 11:53 AM, Sven Kramer <svenkrame...@gmail.com> >> wrote: >> >>> Thank you, Seb, >>> it seems like I am getting it to work. There are still some difficulties >>> because of my limited javascript experience, but with some quick&dirty >>> workarounds I do have the Catalyst output displayed from ParaViewWeb. As >>> you said, nothing else was required than wrapping the C functions in python. >>> >>> Thanks >>> Sven >>> >>> >>> 2016-05-20 18:59 GMT+02:00 Sebastien Jourdain < >>> sebastien.jourd...@kitware.com>: >>> >>>> Hi Sven, >>>> >>>> I am not aware on any specific developer documentation for Catalyst on >>>> the ParaView side (but I haven't worked on that subject for years), >>>> although Utkarsh or Andy might know. >>>> >>>> Usually looking at the code and redoing it in the Python world is what >>>> is required, but as I said, I'm not sure of what it means since I don't >>>> know that code anymore. ;-) >>>> >>>> For the timeframe, I can't tell (meaning I don't know), but we can >>>> still try to help you or implement the missing piece via support contract >>>> if that make sense on your end. >>>> >>>> Thanks, >>>> >>>> Seb >>>> >>>> On Fri, May 20, 2016 at 10:46 AM, Sven Kramer <svenkrame...@gmail.com> >>>> wrote: >>>> >>>>> Hello Seb, >>>>> glad to read your answer. So the problem is not only that I was unable >>>>> to find the relevant information. >>>>> >>>>> You say, you have not (yet) written the required code. Does "not >>>>> (yet)" mean that it is on the agenda maybe within the next half year? Then >>>>> I could find a workaround and look forward to the next Paraview updates. >>>>> >>>>> Otherwise I would try to work on the implementation for connecting >>>>> Paraviewweb to Catalyst output. Is there any developer documentation of >>>>> Catalysts "specific socket connection"? Or some general Catalyst developer >>>>> information? Those would be great to get started. >>>>> My first attempt would be to "wrap" the functionality of >>>>> Qt/ApplicationComponents/pqCatalystConnectReaction.cxx into pvserver and >>>>> make it available to the web client. Or are the necessary steps much more >>>>> involved? >>>>> >>>>> Thank you >>>>> Sven >>>>> >>>>> >>>>> 2016-05-20 15:42 GMT+02:00 Sebastien Jourdain < >>>>> sebastien.jourd...@kitware.com>: >>>>> >>>>>> Hi Sven, >>>>>> >>>>>> Live catalyst connection require a specific socket connection to the >>>>>> in-situ process with some special handling. >>>>>> We did not (yet) wrote the Python code to perform that specific >>>>>> action for ParaViewWeb so it could be triggered by the web client or >>>>>> configured via an argument at launch time. >>>>>> I don't see any reason why this couldn't work, but as for now, I also >>>>>> don't know an easy step to do it without spending time doing it myself. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Thu, May 19, 2016 at 1:52 PM, Sven Kramer <svenkrame...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hello, >>>>>>> I am looking for the recommended steps how to display an in-situ >>>>>>> (live) Catalyst simulation through ParaViewWeb. >>>>>>> >>>>>>> After some efforts I am able to run ParaViewWeb successfully and I >>>>>>> can view a Catalyst-enabled simulation in paraview. >>>>>>> >>>>>>> I hope, it is also possible to show the live Catalyst output via >>>>>>> ParaViewWeb, but I cannot imagine how to achieve this. I tried starting >>>>>>> a >>>>>>> pvserver as mentioned at the end of >>>>>>> https://blog.kitware.com/introduction-to-paraview-catalyst-live/ >>>>>>> and giving "--ds-host localhost --ds-port 11111" options to >>>>>>> pv_web_visualizer.py, but it doesn't help. I can't share anything to be >>>>>>> displayed on the web. >>>>>>> >>>>>>> Below you find the (not too detailed) steps I took to have a working >>>>>>> solution for either Catalyst-enabled simulations or a working web >>>>>>> visualizer: >>>>>>> >>>>>>> Test connection from Catalyst simulation to paraview: >>>>>>> 1) Build and execute paraview from ParaView-v5.0.1-source.tar.gz >>>>>>> (from http://www.paraview.org/download/) >>>>>>> 2) Choose Catalyst->Connect in paraview >>>>>>> 3) Run CFullExample from >>>>>>> https://github.com/Kitware/ParaViewCatalystExampleCode >>>>>>> 4) Pipeline from CFullExample is shown in paraview. >>>>>>> Success! >>>>>>> >>>>>>> Test ParaViewWeb: >>>>>>> 1) Download ParaViewData-5.0.0.tar.gz from >>>>>>> http://www.paraview.org/download/, extract in /data >>>>>>> 2) Run $ParaView_DIR/bin/pvpython >>>>>>> $ParaView_DIR/lib/site-packages/paraview/web/pv_web_visualizer.py >>>>>>> --content >>>>>>> $ParaView_DIR/www --data-dir /data --port 8080 >>>>>>> 3) Open the Visualizer App http://localhost:8080/apps/Visualizer/ >>>>>>> Success! >>>>>>> >>>>>>> But how do I get Catalyst into the web visualizer? Is there any >>>>>>> example how to combine them? Anybody who can suggest the required steps? >>>>>>> >>>>>>> Regards, >>>>>>> Sven >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> Search the list archives at: http://markmail.org/search/?q=ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview