[Paraview] ParaViewWeb - Issues with Loading ASCII STL file & Rendering the Output Fields

[Scott Wittenburg]

Hello Kai,

   Regarding the data files you shared, I did some testing and found some
things out:

1) Regarding using local rendering on the cube data file: It seems that
with local rendering, we may not properly handle coloring by arrays where
the data range is 0 (e.g. the range of T in your case was [303.1499938964844,
303.1499938964844]).  I was able to use local rendering by first loading
the data, then choosing a local rendering approach (either worked fine),
and then going back and coloring by T.  This could be a workaround if you
need to test the speed of local rendering vs remote.

2) Regarding loading the .stl file, I did not run into the same issue as
you did, i.e. the .stl file loaded without any problems.  The paraviewweb I
am running was built from master which is a day or so old, so I'm wondering
what version you may have compiled?

The rest of my responses are inline below...

On Fri, Sep 25, 2015 at 9:15 AM, kai liu <liuwukai at yahoo.com> wrote:

> Dear Scott,
>
> Thanks for your quick response, I have also put my responses inline below
> with light blue color :
>
>
>
>
> *Issue 1: Loading ASCII stl file*
>
> When I try to load my ASCII stl file on the ParaviewWeb, I receive the
> following error message in my log file. However, desktop ParaView
> application loads the file fine.
>
> ERROR: In
> /home/user/ParaViewWeb/ParaView/src/VTK/IO/Geometry/vtkSTLReader.cxx, line
> 461
> vtkSTLReader (0x5d89b50): STLReader: error while reading file
> /home/user/ParaViewWeb/data/Mitchell_Lee_Administration_ReckordArmory_.stl
> at line 14: unable to read reading point.
>
> ERROR: In
> /home/user/ParaViewWeb/ParaView/src/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (0x5d84f70): Algorithm
> vtkFileSeriesReader(0x5d881b0) returned failure for request: vtkInformation
> (0x5d97f30)
>   Debug: Off
>   Modified Time: 225417
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA
>   FROM_OUTPUT_PORT: 0
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
>
>
> Did you build the ParaView desktop application in the same build as the
> version you're using to run ParaViewWeb?  Maybe you could try to take one
> of the standard ParaView datasets and try to load it in ParaViewWeb, and
> see if you have the same issue you mentioned above.  To get this data if
> you don't already have it, go here:
>
> http://www.paraview.org/download/
>
> And under "Type of Download", choose "Data, Documentation, and
> Tutorials".  Once you get this data, try opening the "disk_out_ref.ex2"
> file in ParaViewWeb.  If you see the same issue as above, then there could
> be something going on with the way you have built ParaView, which we can
> try to figure out at that point.  If you do not see the same issue as
> above, then perhaps you could send me (off the list) a sample data file I
> could use to try to replicate the problem and debug it on this end.
>
>
> Kai's Response
>
> I did not build the ParaView desktop application. I installed ParaView
> 4.1.0 through the Ubuntu terminal using
> *sudo apt-get install paraviewopenfoam410 . *
>
> I tested files with local ParaView desktop application as well as local
> ParaViewWeb. My Ubuntu 14.04 server does not have ParaView application, and
> it has only ParaViewWeb. Both server and local ParaViewWeb produce the same
> issues.
>
> I have tested "disk_out_ref.ex2" file in ParaViewWeb, and it seems to be
> okay. I will send you the sample data files privately.
>
>

Just so I am clear.  Your "local" version is the one you install via
apt-get?  And the Ubuntu 14.04 server version is the one you built
yourself?  Did you download a source bundle to build the server one?  If
so, do you know what version you downloaded and built on your server?


>
> *Issue 2: *
>
> If I do the following selections on the ParaViewWeb, I always receive src/VTK/Common/Core/vtkDataArrayTemplate.h:191:
> T vtkDataArrayTemplate<T>::GetValue(vtkIdType) [with T = float; vtkIdType =
> long long int]: Assertion `id >= 0 && id < this->Size' failed message in
> the log file and cause the web socket connection closed.
>
> [image: Inline image]
>
>
>
>
> 2015-09-23 17:33:52-0400 [-] Log opened.
> 2015-09-23 17:33:53-0400 [-] Site starting on 9009
> 2015-09-23 17:33:53-0400 [-] Starting factory <twisted.web.server.Site
> instance at 0x7fb6f2e55830>
> 2015-09-23 17:33:53-0400 [HTTPChannel,0,127.0.0.1] Client has reconnected,
> cancelling reaper
> 2015-09-23 17:33:53-0400 [HTTPChannel,0,127.0.0.1] on_connect: connection
> count = 1
> pvpython:
> /home/user/ParaViewWeb/ParaView/src/VTK/Common/Core/vtkDataArrayTemplate.h:191:
> T vtkDataArrayTemplate<T>::GetValue(vtkIdType) [with T = float; vtkIdType =
> long long int]: Assertion `id >= 0 && id < this->Size' failed.
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> WebSocket connection to
> 'ws://XXXXXXXXXXX:8080/proxy?sessionId=0c562ad6-623f-11e5-9b44-00155dd73e0d'
> failed: Error during WebSocket handshake: Unexpected response code: 503
>
>
> I checked HTTP traffic, it has the following message. I assume the
> connection is closed because of the above error.
>
>
>
> I wonder if the server side process crashed as a result of the error you
> see in the log file?  That would explain the websocket connection error.
> Again, trying a known data set like "disk_out_ref.ex2" may help us to
> pinpoint problem which caused the error output you saw above.
>
>
> Kai's Response
>
> My unintelligent question is how could I determine if the server side
> process crashed?
>
>
>
One approach: Use a terminal on the machine where ParaViewWeb is running
and type:

ps -ef | grep pvpython

If the process is running, you should see a pvpython instance running,
where your pv_web_visualizer.py script is the argument, along with any
other arguments your launcher provided when it started the process for
you.  Something like:

/path/to/paraview/build/bin/pvpython
/path/to/paraview/build/lib/site-packages/paraview/web/pv_web_visualizer.py
--port 9999 --data-dir /blah/blah/blah

In the case of the cube you shared with me, the process did indeed crash as
a result of the steps you provided.


>
>
>
>
> *Issue 3: Slow ParaViewWeb*
>
> My ParaViewWeb is very slow. Even I change the rendering mode to WebGL, It
> is still very slow. The Ubuntu 14.04 Sever  specifications are the
> following:
>
> - 8 Cores
> - 8 GB RAM
>  - 2.3 Ghz processors
>
>
> To get faster rendering with OSMesa, you may try building a recent version
> of OSMesa using Gallium + LLVMPipe.  See here:
>
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>
> But even that won't be as fast as hardware rendering (not using OSMesa).
> I'm not sure why you don't see a speedup when switching to WebGL, though,
> for if your data is small enough to all fit in within the GPU of your
> desktop or laptop, then it should be faster than offscreen rendering on the
> server, once the data is loaded.
>
> Kai's Response
>
> I believe my build is based on  recent version of OSMesa using Gallium +
> LLVMPipe
>
> *Mesa 9.2.2 OSMesa Gallium llvmpipe*
>
> make -j4
>
> autoreconf -fi
>
> ./configure \
> CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \
> CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \
> --disable-xvmc \
> --disable-glx \
> --disable-dri \
> --with-dri-drivers="" \
> --with-gallium-drivers="swrast" \
> --enable-texture-float \
> --disable-shared-glapi \
> --disable-egl \
> --with-egl-platforms="" \
> --enable-gallium-osmesa \
> --enable-gallium-llvm=yes \
> --with-llvm-shared-libs \
> --prefix=/opt/mesa/9.2.2/llvmpipe
>
>
> *make -j2*
> *make -j4 install*
>
>
This looks fine to me, though I believe OSMesa Gallium llvmpipe has moved
along quite a few versions since that documentation was written, so
building a more recent one could be something to try.


>
> When I built ParaViewWeb, The following is what I changed when I generated
> the cmake file:
>
> PARAVIEW_ENABLE_PYTHON      ON
> PARAVIEW_BUILD_QT_GUI       OFF
> CMAKE_INSTALL_PREFIX        /.../ParaView/install
> VTK_USE_X                   OFF
> OPENGL_INCLUDE_DIR          /opt/mesa/9.2.2/llvmpipe/include
> OPENGL_gl_LIBRARY
> OPENGL_glu_LIBRARY          /opt/mesa/9.2.2/llvmpipe/lib/libGLU.so
> VTK_OPENGL_HAS_OSMESA       ON
> OSMESA_INCLUDE_DIR          /opt/mesa/9.2.2/llvmpipe/include
> OSMESA_LIBRARY              /opt/mesa/9.2.2/llvmpipe/lib/libOSMesa.so
>
>
>
> Please feel free to correct me if you believe you did not build a recent
> version of OSMesa using Gallium + LLVMPipe
>
> I will send you two data files. First one is an ASCII STL file (issue 1)
> and second one is the issue rendering output fields (issue 2). Thank you
> for your help!
>
> Please let me know if you need anything from me.
>
>
>
One other thing that could be useful for us to know is what kind of network
is between your browser and the server.  When local rendering is enabled,
the server's camera is still synchronized with with camera in the browser
so that if you switch back to image delivery, you won't see some unexpected
camera angle.  If the network is *really* slow, this could perhaps keep the
local rendering from being as fast as possible.  But it seems like it would
have to be really slow.

Hope this helps.

Cheers,
Scott


> Kai L.
>
>
> --------------------------------------------------------------------------------------------------------------------------------------
>
> On Thursday, September 24, 2015 9:45 AM, Scott Wittenburg <
> scott.wittenburg at kitware.com> wrote:
>
>
> Hello Kai,
>
>    Thanks for your questions, I have put my responses inline below:
>
> On Thu, Sep 24, 2015 at 5:45 AM, kai liu via ParaView <
> paraview at paraview.org> wrote:
>
> Dear,
>
>
> I have deployed ParaViewWeb. Everything seems to work fine, but I am not
> able to visualize outputs, such as rendering the output fields such as T,
> V, etc.
>
> I built and tried ParaViewWeb 4.1, 4.3 and 4.4 with offscreen OSMesa, and
> I have received the same issues. Currently I use Apache 2.4.16 as a front
> end running on port 8080, python launcher and ParaViewWeb 4.4 with
> offscreen OSMesa. The following is my launcher and
>  Apache configuration files:
>
> *launcher.json*
>
> {
>
>   "configuration": {
>     "host" : "localhost",
>
>     "port" : 9000,
>
>     "endpoint": "paraview",
>
>     "content": "/home/user/ParaViewWeb/ParaView/build/www",
>
>     "proxy_file": "/home/user/ParaViewWeb/pv-mapping-file/mapping.txt",
>     "sessionURL" : "ws://testexample.com:8080/proxy?sessionId=${id}
> <http://testexample.com:8080/proxy?sessionId=$%7Bid%7D>",
>
>     "timeout" : 25,
>
>     "log_dir" : "/home/user/ParaViewWeb/pvwLogs",
>     "upload_dir" : "/home/user/ParaViewWeb/upload",
>     "fields" : ["file", "host", "port", "updir"]
>
>   },
>
>
>   "resources" : [ { "host" : "localhost", "port_range" : [9001, 9010] } ],
>
>
>   "properties" : {
>     "build_dir" : "/home/user/ParaViewWeb/ParaView/build",
>     "python_exec" : "/home/user/ParaViewWeb/ParaView/build/bin/pvpython",
>         "python_path":
> "/home/user/ParaViewWeb/ParaView/build/lib/site-packages",
>     "WWW" : "/home/user/ParaViewWeb/ParaView/build/www",
>     "dataDir": "/home/user/ParaViewWeb/data",
>     "load_file": "/home/user/ParaViewWeb/upload",
>     "source_dir": "/.../src"
>   },
>
>   "apps": {
>     "pipeline": {
>       "cmd": [
>         "${python_exec}", "-dr",
> "${python_path}/paraview/web/pv_web_visualizer.py",
>         "--port", "${port}", "--data-dir", "${dataDir}"
>       ],
>       "ready_line" : "Starting factory"
>     },
>     "visualizer": {
>         "cmd": [
>             "${python_exec}", "-dr",
> "${python_path}/paraview/web/pv_web_visualizer.py",
>             "--port", "${port}", "--data-dir", "${dataDir}"
>         ],
>         "ready_line" : "Starting factory"
>     },
>     "loader": {
>         "cmd": [
>             "${python_exec}", "-dr",
> "${python_path}/paraview/web/pv_web_file_loader.py",
>             "--port", "${port}", "--data-dir", "${dataDir}", "-f",
> "--authKey", "${secret}"
>         ],
>         "ready_line" : "Starting factory"
>     },
>     "data_prober": {
>         "cmd": [
>             "${python_exec}", "-dr",
> "${python_path}/paraview/web/pv_web_data_prober.py",
>             "--port", "${port}", "--data-dir", "${dataDir}", "-f",
> "--authKey", "${secret}"
>         ],
>         "ready_line" : "Starting factory"
>     }
>     }
> }
>
> *httpd-vhosts.conf*
>
> <VirtualHost *:8080>
>     ServerName testexample.com
>     ServerAdmin webmaster at example-host.example.com
>     DocumentRoot "/home/user/ParaViewWeb/ParaView/build/www"
>     ErrorLog "/home/user/ParaViewWeb/apacheLogs/pv-error_log"
>     CustomLog "/home/user/ParaViewWeb/apacheLogs/pv-access_log" common
>
>
>     ProxyPass /paraview http://localhost:9000/paraview
>
>     # Turn on the rewrite engine
>     RewriteEngine On
>
>     # This is the path the mapping file Jetty creates
>     RewriteMap session-to-port
> txt:/home/user/ParaViewWeb/pv-mapping-file/mapping.txt
>
>     # This is the rewrite condition. Look for anything with a sessionId=
> in the query part of the URL and capture the value to use below.
>     RewriteCond %{QUERY_STRING}     ^sessionId=(.*)$ [NC]
>
>     # This does the rewrite using the mapping file and the sessionId
>     RewriteRule    ^/proxy.*$  ws://${session-to-port:%1}/ws  [P]
>
>    <Directory "/home/user/ParaViewWeb/ParaView/build/www">
>         Options Indexes FollowSymLinks
>         Order allow,deny
>         Allow from all
>         AllowOverride None
>         Require all granted
>     </Directory>
> </VirtualHost>
>
>
>
>
> *Issue 1: Loading ASCII stl file*
>
> When I try to load my ASCII stl file on the ParaviewWeb, I receive the
> following error message in my log file. However, desktop ParaView
> application loads the file fine.
>
> ERROR: In
> /home/user/ParaViewWeb/ParaView/src/VTK/IO/Geometry/vtkSTLReader.cxx, line
> 461
> vtkSTLReader (0x5d89b50): STLReader: error while reading file
> /home/user/ParaViewWeb/data/Mitchell_Lee_Administration_ReckordArmory_.stl
> at line 14: unable to read reading point.
>
> ERROR: In
> /home/user/ParaViewWeb/ParaView/src/VTK/Common/ExecutionModel/vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (0x5d84f70): Algorithm
> vtkFileSeriesReader(0x5d881b0) returned failure for request: vtkInformation
> (0x5d97f30)
>   Debug: Off
>   Modified Time: 225417
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA
>   FROM_OUTPUT_PORT: 0
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
>
>
> Did you build the ParaView desktop application in the same build as the
> version you're using to run ParaViewWeb?  Maybe you could try to take one
> of the standard ParaView datasets and try to load it in ParaViewWeb, and
> see if you have the same issue you mentioned above.  To get this data if
> you don't already have it, go here:
>
> http://www.paraview.org/download/
>
> And under "Type of Download", choose "Data, Documentation, and
> Tutorials".  Once you get this data, try opening the "disk_out_ref.ex2"
> file in ParaViewWeb.  If you see the same issue as above, then there could
> be something going on with the way you have built ParaView, which we can
> try to figure out at that point.  If you do not see the same issue as
> above, then perhaps you could send me (off the list) a sample data file I
> could use to try to replicate the problem and debug it on this end.
>
>
>
>
> *Issue 2: *
>
> If I do the following selections on the ParaViewWeb, I always receive src/VTK/Common/Core/vtkDataArrayTemplate.h:191:
> T vtkDataArrayTemplate<T>::GetValue(vtkIdType) [with T = float; vtkIdType =
> long long int]: Assertion `id >= 0 && id < this->Size' failed message in
> the log file and cause the web socket connection closed.
>
> [image: Inline image]
>
>
>
>
> 2015-09-23 17:33:52-0400 [-] Log opened.
> 2015-09-23 17:33:53-0400 [-] Site starting on 9009
> 2015-09-23 17:33:53-0400 [-] Starting factory <twisted.web.server.Site
> instance at 0x7fb6f2e55830>
> 2015-09-23 17:33:53-0400 [HTTPChannel,0,127.0.0.1] Client has reconnected,
> cancelling reaper
> 2015-09-23 17:33:53-0400 [HTTPChannel,0,127.0.0.1] on_connect: connection
> count = 1
> pvpython:
> /home/user/ParaViewWeb/ParaView/src/VTK/Common/Core/vtkDataArrayTemplate.h:191:
> T vtkDataArrayTemplate<T>::GetValue(vtkIdType) [with T = float; vtkIdType =
> long long int]: Assertion `id >= 0 && id < this->Size' failed.
>
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> WebSocket connection to
> 'ws://XXXXXXXXXXX:8080/proxy?sessionId=0c562ad6-623f-11e5-9b44-00155dd73e0d'
> failed: Error during WebSocket handshake: Unexpected response code: 503
>
>
> I checked HTTP traffic, it has the following message. I assume the
> connection is closed because of the above error.
>
>
>
> I wonder if the server side process crashed as a result of the error you
> see in the log file?  That would explain the websocket connection error.
> Again, trying a known data set like "disk_out_ref.ex2" may help us to
> pinpoint problem which caused the error output you saw above.
>
>
> *Issue 3: Slow ParaViewWeb*
>
> My ParaViewWeb is very slow. Even I change the rendering mode to WebGL, It
> is still very slow. The Ubuntu 14.04 Sever  specifications are the
> following:
>
> - 8 Cores
> - 8 GB RAM
>  - 2.3 Ghz processors
>
>
> To get faster rendering with OSMesa, you may try building a recent version
> of OSMesa using Gallium + LLVMPipe.  See here:
>
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>
> But even that won't be as fast as hardware rendering (not using OSMesa).
> I'm not sure why you don't see a speedup when switching to WebGL, though,
> for if your data is small enough to all fit in within the GPU of your
> desktop or laptop, then it should be faster than offscreen rendering on the
> server, once the data is loaded.
>
> Just glancing through the configuration files you provided, I don't see
> anything wrong.
>
> Hope this helps,
> Scott
>
>
>
>
> Please let me know if I have setup anything incorrectly. Could anybody
> help me with the above three issues that I am experiencing now. Thank you
> very much!
>
>
> Kai L.
>
>
>
>
>
> _______________________________________________
> 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
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150925/bf43ca55/attachment.html>