User Tools

Site Tools


howto:paraview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howto:paraview [2019/05/22 14:49]
ccrosby [Paraview client in a VNC session]
howto:paraview [2020/02/18 11:42] (current)
ccrosby [Paraview client in a VNC session]
Line 4: Line 4:
   - A standard binary distribution Paraview-4.3.1 in ''/​apps/​chpc/​compmech/​ParaView-4.3.1-Linux-64bit/​bin''​   - A standard binary distribution Paraview-4.3.1 in ''/​apps/​chpc/​compmech/​ParaView-4.3.1-Linux-64bit/​bin''​
   - A custom compiled Paraview-5.0.1 in ''​apps/​chpc/​compmech/​CFD/​Paraview/​bin''​   - A custom compiled Paraview-5.0.1 in ''​apps/​chpc/​compmech/​CFD/​Paraview/​bin''​
 +  - A standard binary distribution Paraview-5.2.0 in ''/​apps/​chpc/​compmech/​ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit''​
   - A standard binary distribution Paraview-5.3.0 in ''/​apps/​chpc/​compmech/​ParaView-5.3.0_bininstall''​   - A standard binary distribution Paraview-5.3.0 in ''/​apps/​chpc/​compmech/​ParaView-5.3.0_bininstall''​
   - A standard binary distribution Paraview-5.4.1 in ''/​apps/​chpc/​compmech/​ParaView-5.4.1-Qt5-OpenGL-MPI-Linux-64bit''​   - A standard binary distribution Paraview-5.4.1 in ''/​apps/​chpc/​compmech/​ParaView-5.4.1-Qt5-OpenGL-MPI-Linux-64bit''​
Line 13: Line 14:
  
 ===== Paraview client in a VNC session ===== ===== Paraview client in a VNC session =====
-For many small to moderate visualization tasks, the user may wish to run the Paraview client directly on the cluster, in a [[howto:​remote_viz|VNC session]]. ​ This can be done easily on one of the visualization nodes chpcviz1 or chpclic1. ​ However, due to high levels of use on these nodes, or a demanding data set, the user may prefer to use a VNC session on a compute node.   This process is [[http://​wiki.chpc.ac.za/​howto:​remote_viz?&#​getting_a_virtual_desktop_on_a_compute_node|documented and straightforward]]. ​ However, this relies on persuading the Paraview client to work properly with the Mesa software rendering libraries. and this procedure ​varies between ​the various ​Paraview versions.+For many small to moderate visualization tasks, the user may wish to run the Paraview client directly on the cluster, in a [[howto:​remote_viz|VNC session]]. ​ This can be done easily on one of the visualization nodes chpcviz1 or chpclic1. ​ However, due to high levels of use on these nodes, or a demanding data set, the user may prefer to use a VNC session on a compute node.   This process is [[http://​wiki.chpc.ac.za/​howto:​remote_viz?&#​getting_a_virtual_desktop_on_a_compute_node|documented and straightforward]]. ​ However, this relies on persuading the Paraview client to work properly with the Mesa software rendering libraries. and this procedure ​fails with the later Paraview versions. ​ The problem is an incompatibility between Mesa, VNC and the Qt-5 library. Older versions that rely on Qt-4 work extremely well on a compute node.  The following versions have been tested. 
 + 
 +^ Version ^ Paraview Module ​              ​^ ​ GALLIUM_DRIVER ^ Command line ^ 
 +| 4.3.1 | chpc/​compmech/​Paraview/​4.3.1 ​ | llvmpipe or swr   | paraview ​  | 
 +| 5.2.0 | chpc/​compmech/​Paraview/​5.2.0 ​ | llvmpipe or swr   | paraview ​  | 
 + 
  
  
Line 62: Line 69:
   * In this terminal, load up the module ''​module load chpc/​compmech/​Paraview/​5.4.1''​   * In this terminal, load up the module ''​module load chpc/​compmech/​Paraview/​5.4.1''​
   * In this terminal, start up the paraview server with the command <​code>​mpiexec -np 24 pvserver --mpi --mesa-llvm --use-offscreen-rendering</​code>​. ​ Although you will not launch any graphics from this terminal, the software needs the X-capability to be available.   * In this terminal, start up the paraview server with the command <​code>​mpiexec -np 24 pvserver --mpi --mesa-llvm --use-offscreen-rendering</​code>​. ​ Although you will not launch any graphics from this terminal, the software needs the X-capability to be available.
-  * On your workstation,​ build an ssh-tunnel through lengau.chpc.ac.za to port 11111 on cnode1234. ​ Forward this port to port 11111 on your workstation. ​ The command in Linux is ''​ssh -f jbloga@lengau.chpc.ac.za -L 11111:​cnode1234:​11111 -N''​+  * On your workstation,​ build an ssh-tunnel through lengau.chpc.ac.za to port 11111 on cnode1234. ​ Forward this port to port 11111 on your workstation. ​ The command in Linux is ''​ssh -f jblogs@lengau.chpc.ac.za -L 11111:​cnode1234:​11111 -N''​
   * Launch Paraview on your workstation,​ which can be running any operating system that supports Paraview. ​ It does not need to be Linux.  ​   * Launch Paraview on your workstation,​ which can be running any operating system that supports Paraview. ​ It does not need to be Linux.  ​
   * Use the "​Connect"​ menu in Paraview to set up port 11111@localhost as a Paraview server. ​ Connect to this server.   * Use the "​Connect"​ menu in Paraview to set up port 11111@localhost as a Paraview server. ​ Connect to this server.
/var/www/wiki/data/attic/howto/paraview.1558529387.txt.gz · Last modified: 2019/05/22 14:49 by ccrosby