38,760
edits
ParaView/en: Difference between revisions
Jump to navigation
Jump to search
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 198: | Line 198: | ||
Next, compile <code>llvm</code>: | Next, compile <code>llvm</code>: | ||
<source lang="console"> | |||
cd | |||
wget http://releases.llvm.org/3.9.1/llvm-3.9.1.src.tar.xz | wget http://releases.llvm.org/3.9.1/llvm-3.9.1.src.tar.xz | ||
unpack and cd there | unpack and cd there | ||
| Line 212: | Line 212: | ||
make | make | ||
sudo make install | sudo make install | ||
</source> | |||
Next, compile Mesa with OSMesa: | Next, compile Mesa with OSMesa: | ||
<source lang="console"> | |||
cd | |||
wget ftp://ftp.freedesktop.org/pub/mesa/mesa-17.0.0.tar.gz | wget ftp://ftp.freedesktop.org/pub/mesa/mesa-17.0.0.tar.gz | ||
unpack and cd there | unpack and cd there | ||
| Line 231: | Line 232: | ||
make | make | ||
sudo make install | sudo make install | ||
</source> | |||
Next, compile the ParaView server: | Next, compile the ParaView server: | ||
<source lang="console"> | |||
cd | |||
wget http://www.paraview.org/files/v5.2/ParaView-v5.2.0.tar.gz | wget http://www.paraview.org/files/v5.2/ParaView-v5.2.0.tar.gz | ||
unpack and cd there | unpack and cd there | ||
| Line 250: | Line 252: | ||
make | make | ||
make install | make install | ||
</source> | |||
=== Client-server mode === | === Client-server mode === | ||
You are now ready to start ParaView server on the VM with SWR rendering: | You are now ready to start ParaView server on the VM with SWR rendering: | ||
<source lang="console"> | |||
./paraview/bin/pvserver --mesa-swr-avx2 | |||
</source> | |||
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: | ||
<source lang="console"> | |||
ssh centos@vm.ip.address -L 11111:localhost:11111 | |||
</source> | |||
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.'' | |||
</tab> | |||
</tabs> | |||
= Remote VNC desktop on Graham VDI nodes = | |||
For small interactive visualizations, you can use Graham's VDI nodes. Unlike client-server visualizations, on the VDI nodes you'll be using VNC remote desktop. Here are the steps: | |||
For small interactive visualizations, you can use Graham's VDI nodes. Unlike client-server visualizations | |||
1. Connect to the VDI node of Graham | 1. Connect to the VDI node of Graham. | ||
You need to use a [[VNC]] client (Tiger VNC is preferred) to get connected to the VDI node. | You need to use a [[VNC]] client (Tiger VNC is preferred) to get connected to the VDI node. | ||
2. Load CC modules and launch ParaView | 2. Load CC modules and launch ParaView. | ||
After login to the VDI node, you need to open a terminal in which you issue the following commands | After login to the VDI node, you need to open a terminal in which you issue the following commands | ||
| Line 279: | Line 286: | ||
|paraview | |paraview | ||
}} | }} | ||
= Batch rendering = | = Batch rendering = | ||
For large-scale and automated visualization, we strongly recommend switching from interactive client-server to off-screen batch visualization. ParaView supports Python scripting, so you can script your workflow and submit it as a regular, possibly parallel production job on a cluster. If you need any help with this, please contact [[Technical support]]. | For large-scale and automated visualization, we strongly recommend switching from interactive client-server to off-screen batch visualization. ParaView supports Python scripting, so you can script your workflow and submit it as a regular, possibly parallel production job on a cluster. If you need any help with this, please contact [[Technical support]]. | ||