Remote Cluster Testing: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Created page with "This page contains instructions on how to test ParaView running on a remote server. It is only a procedure for testing - it does not explain how to actually do the connection...") |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page contains instructions on how to test ParaView running on a remote server. It is only a procedure for testing - it does not explain how to actually do the connection. | This page contains instructions on how to test ParaView running on a remote server or cluster. It is only a procedure for testing - it does not explain how to actually do the connection. | ||
=Test setup= | =Test setup= | ||
| Line 6: | Line 6: | ||
=Cluster test with Source= | =Cluster test with Source= | ||
*Edit/ Settings/ Render View/ Remove Render Threshold. Change this to 0, OK. This will force all future rendering to the target server. | *Edit/ Settings/ Render View/ Remove Render Threshold. Change this to 0, OK. This will force all future rendering to the target server, and not on the local client. | ||
*Sources/ Sphere. Apply. Spin, spin. Delete. | *Sources/ Sphere. Apply. Spin, spin. Delete. | ||
*Sources/ Wavelet. Apply. Representation Surface. Color by RTData. Rotate Wavelet. Make sure that the edges of the Wavelet go somewhat rough (saw toothy). This means we really are rendering on the cluster. | *Sources/ Wavelet. Apply. Representation Surface. Color by RTData. Rotate Wavelet. Make sure that the edges of the Wavelet go somewhat rough (saw toothy). This means we really are rendering on the cluster. | ||
*While still on Wavelet, Filters/ Alphabetical/ ProcessID Scalars. This will paint by rendering process number. | *While still on Wavelet, Filters/ Alphabetical/ ProcessID Scalars. This will paint by rendering process number. | ||
=Cluster test with Source= | |||
*Read in some data. Make it simple, such as can.exo. Spin, spin. Play, play. | *Read in some data. Make it simple, such as can.exo. Spin, spin. Play, play. | ||
=Tools to help debug= | =Tools to help debug= | ||
Latest revision as of 21:58, 14 December 2016
This page contains instructions on how to test ParaView running on a remote server or cluster. It is only a procedure for testing - it does not explain how to actually do the connection.
Test setup
- ParaView client needs to be running on a local computer, blade or workstation.
- Remote server needs to be running on the target server, with at least 2 (preferably 4) pvservers.
Cluster test with Source
- Edit/ Settings/ Render View/ Remove Render Threshold. Change this to 0, OK. This will force all future rendering to the target server, and not on the local client.
- Sources/ Sphere. Apply. Spin, spin. Delete.
- Sources/ Wavelet. Apply. Representation Surface. Color by RTData. Rotate Wavelet. Make sure that the edges of the Wavelet go somewhat rough (saw toothy). This means we really are rendering on the cluster.
- While still on Wavelet, Filters/ Alphabetical/ ProcessID Scalars. This will paint by rendering process number.
Cluster test with Source
- Read in some data. Make it simple, such as can.exo. Spin, spin. Play, play.
Tools to help debug
- When you qsub nodes, add a -e fileName and -o fileName. Then, error and normal output prints should go to these files.
- View/ Memory Inspector will tell you how much memory you are using.
- Help/ About/ Connection information will tell you the number of pvserver processes you have and how rendering is being done, along with other useful information.
- Edit/ Settings/ Advanced/ Render View/ Show Annotation will write some debugging information to the screen.
