CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Visualization & Post-Processing Software > ParaView

[General] Error in rendering and visualization from Paraview web docker image

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   November 8, 2021, 04:35
Default Error in rendering and visualization from Paraview web docker image
  #1
Member
 
Sunag R A
Join Date: Jul 2019
Location: Bangalore, India
Posts: 82
Rep Power: 5
sunagra27 is on a distinguished road
Dear all,


I am trying to visualization from paraview web server using docker image.

1. I have read this documentation http://kitware.github.io/paraviewweb...heatsheet.html and ran the docker container from run.sh as shown below for paraview5.6 version.

2. <APP_ROOT> = /pvw

3. I am getting the error as shown in Error_Image_link below.


Commands:

run.sh file

Code:
#!/bin/bash 
export PORT=9000 
export DATA=/home/Sunag/pvw/data 
export DEPLOY=/home/Sunag/pvw 
export SERVER_NAME=localhost:80 
export PROTOCOL=ws  

sudo docker run --name model_osmesa \    
                          -p 0.0.0.0:${PORT}:80    \   
                         -v ${DATA}:/data    \    
                         -v ${DEPLOY}:/pvw    \    
                         -e "SERVER_NAME=${SERVER_NAME}"\     
                         -e "PROTOCOL=${PROTOCOL}"\     
                          -ti kitware/paraviewweb:pvw-v5.6.0-osmesa
3. I am getting "Websocket connection error for either visualizer or paraview lite" as shown in the image link below:

Error_image_link: https://drive.google.com/file/d/1bIf...ew?usp=sharing

4. The launcher configuration file is as presented below:
Code:
{   "resources": [ {"port_range": [9001, 9103], "host": "localhost"} ],  
 "sessionData": {     "updir": "/Home"    },   
"configuration": {     
           "log_dir": "/pvw/launcher/log",    
           "host": "localhost",    
           "endpoint": "paraview",   
           "sessionURL": "SESSION_URL_ROOT/proxy?sessionId=${id}&path=ws", 
           "timeout": 60,  
          "upload_dir":"/data/upload", 
         "fields": [],    
         "port": 9000,    
         "proxy_file": "/opt/launcher/proxy-mapping.txt",  
         "sanitize": {       "version": {         
                         "type": "regexp",          
                         "regexp": "^v[0-9]+.[0-9]+.[0-9]+$",          
                         "default": "v0.0.0"       },      
                    "file": {           
                        "type": "regexp",          
                        "regexp": "^[-\\\\w./]+$",          
                        "default": "emptyFile"      
                             } 
                         }  
                      },   
            "properties": {    
                       "dataDir": "/data",    
                       "webapps_dir": "/opt/paraview/share/paraview-5.6/web", 
                       "python_exec": "/opt/paraview/bin/pvpython"  
                                },  
              "apps": {    
                        "visualizer": {      
                        "cmd": [        
                           "${python_exec}",        
                           EXTRA_PVPYTHON_ARGS        
                            "${webapps_dir}/visualizer/server/pvw-visualizer.py",        
                             "--port", "${port}",       
                             "--data", "${dataDir}",        
                             "--authKey", "${secret}"       
                                      ],      
                           "ready_line" : "Starting factory"     
                         }  
                    }
                }
5. When I got onto http://localhost:9000/visualizer, the error occurs as presented in the error link above. All the logs are captured including a unique id in proxy-mapping.txt.

6. I am trying to make this work from past a week.

7. I tried with different versions of paraview such as 5.7,5.8 and 5.8 for both osmesa version and egl version in office system. But, getting same error.

Any suggestions or workaround will be appreciated.

Regards,
Sunag R A.
sunagra27 is offline   Reply With Quote

Reply

Tags
openfoam, paraview, paraviewweb, vtk

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[General] welding sim visualization problems in Paraview Aorus ParaView 0 December 25, 2009 15:39


All times are GMT -4. The time now is 09:45.