rsnt_translations
56,420
edits
No edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
<!--T:61--> | <!--T:61--> | ||
Cedar and Graham have a number of interactive GPU nodes that can be used for remote ParaView client-server visualization. | Cedar and Graham have a number of interactive GPU nodes that can be used for remote ParaView client-server visualization. | ||
1. First, install the same ParaView version as the one available on the cluster you will be using. Log into Cedar or Graham and start a serial GPU interactive job: | |||
<!--T:62--> | <!--T:62--> | ||
Line 38: | Line 38: | ||
<!--T:63--> | <!--T:63--> | ||
:The job should automatically start on one of GPU interactive nodes. | |||
2. At the prompt (that is now running inside your job), load the ParaView GPU+EGL module, change your display variable so that ParaView does not attempt to use the X11 rendering context, and start the ParaView server. | |||
<!--T:64--> | <!--T:64--> | ||
Line 47: | Line 47: | ||
<!--T:65--> | <!--T:65--> | ||
Wait for the server to be ready to accept client connection. | :Wait for the server to be ready to accept client connection. | ||
<!--T:66--> | <!--T:66--> | ||
Line 55: | Line 55: | ||
<!--T:67--> | <!--T:67--> | ||
3. Make a note of the node (in this case cdr347) and the port (usually 11111) and in another terminal on your laptop (on Mac/Linux; in Windows use a terminal emulator), link the port 11111 on your laptop and the same port on the compute node (make sure to use the correct compute node). | |||
<!--T:68--> | <!--T:68--> | ||
Line 61: | Line 61: | ||
<!--T:69--> | <!--T:69--> | ||
4. Start ParaView on your laptop, go to ''File -> Connect'' (or click on the green ''Connect'' button on the toolbar) and then click ''Add Server''. You'll need to point ParaView to your local port 11111, so you can do something like name = cedar, server type = Client/Server, host = localhost, port = 11111, then click ''Configure'', then select ''Manual'' and click ''Save''. | |||
Once the remote is added to the configuration, simply select the server from the list and click Connect. The first terminal window that read "Accepting connection ..." will now read "Client connected". | :Once the remote is added to the configuration, simply select the server from the list and click Connect. The first terminal window that read "Accepting connection ..." will now read "Client connected". | ||
<!--T:70--> | <!--T:70--> | ||
5. Open a file in ParaView (it'll point you to the remote filesystem) and visualize it as usual. | |||
An important setting in ParaView's preferences is Render View -> Remote/Parallel Rendering Options -> Remote Render Threshold. If you set it to default (20MB) or similar, small rendering will be done on your laptop's GPU, the rotation with a mouse will be fast, but anything modestly intensive (under 20MB) will be shipped to your laptop and -- depending on your connection -- visualization might be slow. If you set it to 0MB, all rendering will be remote including rotation, so you'll be really using the cluster's GPU for everything, good for large data processing but not so good for interactivity. You'll need to play with this setting to see what works best for you. | |||
An important setting in ParaView's preferences is ''Render View -> Remote/Parallel Rendering Options -> Remote Render Threshold''. If you set it to default (20MB) or similar, small rendering will be done on your laptop's GPU, the rotation with a mouse will be fast, but anything modestly intensive (under 20MB) will be shipped to your laptop and -- depending on your connection -- visualization might be slow. If you set it to 0MB, all rendering will be remote including rotation, so you'll be really using the cluster's GPU for everything, which is good for large data processing but not so good for interactivity. You'll need to play with this setting to see what works best for you. | |||
== CPU-based client-server visualization on Cedar and Graham == <!--T:43--> | == CPU-based client-server visualization on Cedar and Graham == <!--T:43--> |