Hi Seb,
Thanks for the info. The client browser opens properly with "--authKey",
"${secret}" removed.
=> "sessionURL" : "ws://192.168.120.8:${port}/proxy?sessionId=${id}"
${port} should be there otherwise "pvpython pv_web_visualizer.py" is
not issued.
Thanks!
Ying
On 2014-12-2 0:53, S
we implemented vortex cores in paraview many years ago, but after searching I
could not find the code
http://www.inf.ethz.ch/personal/peikert/SciVis/research/CTI-FinalReport.pdf
is the/one reference.
Filip Sadlo was the main author and might have a copy somewhere. I must have it
in one of my arc
Hi Ken,
Thanks for your prompt response. Sorry about the confusion here.
I have a large Netcdf file which is visualized with Parallel Paraview. Now I
have no problems with visualizing the values of an attribute( e.g.,
temperature). The next step is to modify the attribute values based on the
ano
The point of using Apache as a front-end is to provide a single entry point
(just port 80 or 443 for https).
While the ${port} here will change for each running visualization process.
More information can be found here
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/mul