Bureaucrats, cc_docs_admin, cc_staff
2,918
edits
Visualization: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
(→Compiling VisIt with Mesa: exclude shell code from translation) |
(Marked this version for translation) |
||
| Line 29: | Line 29: | ||
This section will be updated as the new systems come online starting with Cedar (SFU) and Graham (Waterloo) in April-May 2017. | This section will be updated as the new systems come online starting with Cedar (SFU) and Graham (Waterloo) in April-May 2017. | ||
== Running client-server ParaView and client-server VisIt in a cloud VM == | == Running client-server ParaView and client-server VisIt in a cloud VM == <!--T:20--> | ||
=== Prerequisites === | === Prerequisites === <!--T:21--> | ||
<!--T:22--> | |||
You can launch a new cloud virtual machine (VM) as described in the [[Cloud Quick Start|Cloud Quick Start Guide]]. Once you log into the VM, you'll need to install some additional packages to be able to compile ParaView or VisIt. For example, on a CentOS VM you can type: | You can launch a new cloud virtual machine (VM) as described in the [[Cloud Quick Start|Cloud Quick Start Guide]]. Once you log into the VM, you'll need to install some additional packages to be able to compile ParaView or VisIt. For example, on a CentOS VM you can type: | ||
| Line 42: | Line 43: | ||
<translate> | <translate> | ||
<!--T:23--> | |||
If you have your own private-public SSH key pair (as opposed to the cloud key), you may want to copy the public key to the VM to simplify logins, by issuing the following command on your laptop: | If you have your own private-public SSH key pair (as opposed to the cloud key), you may want to copy the public key to the VM to simplify logins, by issuing the following command on your laptop: | ||
| Line 48: | Line 50: | ||
<translate> | <translate> | ||
=== Compiling ParaView with OSMesa === | === Compiling ParaView with OSMesa === <!--T:24--> | ||
<!--T:25--> | |||
Since the VM does not have access to a GPU (most Cloud West VMs don't), we need to compile ParaView with OSMesa support so that it can do offscreen (software) rendering. The default configuration of OSMesa will enable OpenSWR (Intel's software rasterization library to run OpenGL). What you'll end up with is a ParaView server that uses OSMesa for offscreen CPU-based rendering without X but with both llvmpipe (oder and slower) and SWR (newer and faster) drivers built. We recommend using SWR. | Since the VM does not have access to a GPU (most Cloud West VMs don't), we need to compile ParaView with OSMesa support so that it can do offscreen (software) rendering. The default configuration of OSMesa will enable OpenSWR (Intel's software rasterization library to run OpenGL). What you'll end up with is a ParaView server that uses OSMesa for offscreen CPU-based rendering without X but with both llvmpipe (oder and slower) and SWR (newer and faster) drivers built. We recommend using SWR. | ||
<!--T:26--> | |||
Back on the VM, compile cmake:: | Back on the VM, compile cmake:: | ||
</translate> | </translate> | ||
| Line 60: | Line 64: | ||
sudo make install | sudo make install | ||
<translate> | <translate> | ||
<!--T:27--> | |||
Next, compile llvm: | Next, compile llvm: | ||
</translate> | </translate> | ||
| Line 76: | Line 81: | ||
sudo make install | sudo make install | ||
<translate> | <translate> | ||
<!--T:28--> | |||
Next, compile Mesa with OSMesa: | Next, compile Mesa with OSMesa: | ||
</translate> | </translate> | ||
| Line 95: | Line 101: | ||
sudo make install | sudo make install | ||
<translate> | <translate> | ||
<!--T:29--> | |||
Next, compile ParaView server: | Next, compile ParaView server: | ||
</translate> | </translate> | ||
| Line 115: | Line 122: | ||
<translate> | <translate> | ||
=== Running ParaView in client-server mode === | === Running ParaView in client-server mode === <!--T:30--> | ||
<!--T:31--> | |||
Now you are ready to start ParaView server on the VM with SWR rendering: | Now you are ready to start ParaView server on the VM with SWR rendering: | ||
</translate> | </translate> | ||
./paraview/bin/pvserver --mesa-swr-avx2 | ./paraview/bin/pvserver --mesa-swr-avx2 | ||
<translate> | <translate> | ||
<!--T:32--> | |||
Back on your laptop, organize an SSH tunnel from the local port 11111 to the VM's port 11111: | Back on your laptop, organize an SSH tunnel from the local port 11111 to the VM's port 11111: | ||
</translate> | </translate> | ||
ssh centos@vm.ip.address -L 11111:localhost:11111 | ssh centos@vm.ip.address -L 11111:localhost:11111 | ||
<translate> | <translate> | ||
<!--T:33--> | |||
Finally, start the ParaView client on your laptop and connect to localhost:11111. If successful, you should be able to open files on the remote VM. During rendering in the console you should see the message "SWR detected AVX2". | Finally, start the ParaView client on your laptop and connect to localhost:11111. If successful, you should be able to open files on the remote VM. During rendering in the console you should see the message "SWR detected AVX2". | ||
=== Compiling VisIt with Mesa === | === Compiling VisIt with Mesa === <!--T:34--> | ||
<!--T:35--> | |||
VisIt with offscreen rendering support can be built with a single script: | VisIt with offscreen rendering support can be built with a single script: | ||
</translate> | </translate> | ||
| Line 136: | Line 147: | ||
--hdf4 --hdf5 --netcdf --silo --szip --xdmf --zlib | --hdf4 --hdf5 --netcdf --silo --szip --xdmf --zlib | ||
<translate> | <translate> | ||
<!--T:36--> | |||
This may take a couple of hours. Once finished, you can test the installation with: | This may take a couple of hours. Once finished, you can test the installation with: | ||
</translate> | </translate> | ||
~/visit/bin/visit -cli -nowin | ~/visit/bin/visit -cli -nowin | ||
<translate> | <translate> | ||
<!--T:37--> | |||
This should start a VisIt Python shell. | This should start a VisIt Python shell. | ||
=== Running VisIt in client-server mode === | === Running VisIt in client-server mode === <!--T:38--> | ||
<!--T:39--> | |||
Start VisIt on your laptop and in Options -> Host profiles... edit the connection nickname (let's call it Cloud West), the VM host name, path to VisIt installation (/home/centos/visit) and your username on the VM, and enable tunneling through ssh. Don't forget to save settings with Options -> Save Settings. Then opening a file (File -> Open file... -> Host = Cloud West) you should see the VM's filesystem. Load a file and try to visualize it. Data processing and rendering should be done on the VM, while the result and the GUI controls will be displayed on your laptop. | Start VisIt on your laptop and in Options -> Host profiles... edit the connection nickname (let's call it Cloud West), the VM host name, path to VisIt installation (/home/centos/visit) and your username on the VM, and enable tunneling through ssh. Don't forget to save settings with Options -> Save Settings. Then opening a file (File -> Open file... -> Host = Cloud West) you should see the VM's filesystem. Load a file and try to visualize it. Data processing and rendering should be done on the VM, while the result and the GUI controls will be displayed on your laptop. | ||