ParaView/Run on Remote Machine - Revision history

Prte0550 at 19:28, 11 November 2022

2022-11-11T19:28:56Z

Prte0550: Added Cooley documentation

2022-11-11T17:43:37Z

Added Cooley documentation

Jrwrigh: Jrwrigh moved page Paraview: Run on Remote Machine to ParaView/Run on Remote Machine: Move to a subpage organization

2022-09-18T18:01:54Z

Jrwrigh moved page Paraview: Run on Remote Machine to ParaView/Run on Remote Machine: Move to a subpage organization

Jrwrigh at 23:11, 13 July 2020

2020-07-13T23:11:20Z

Jrwrigh at 23:08, 13 July 2020

2020-07-13T23:08:09Z

Jrwrigh: /* Janus (CUBoulder RC Computing) */

2020-07-13T22:46:48Z

‎Janus (CUBoulder RC Computing)

Jrwrigh: Jrwrigh moved page ParaView:Run on Remote Machine to Paraview: Run on Remote Machine: Misspell

2020-07-13T22:44:02Z

Jrwrigh moved page ParaView:Run on Remote Machine to Paraview: Run on Remote Machine: Misspell

Jrwrigh at 22:42, 13 July 2020

2020-07-13T22:42:30Z

Jrwrigh: /* Tukey (ALCF) */

2020-07-13T22:40:52Z

‎Tukey (ALCF)

Jrwrigh: Moved previously separate pages into a single page.

2020-07-13T22:39:31Z

Moved previously separate pages into a single page.

New page

Here are instructions for running Paraview on some selected remote machines.

In general, this involves launching an interactive job using the machine's job scheduler, loading whatever required software is needed, and then launching the Paraview server:

== Retired Machines ==

=== Eureka (ALCF) ===
==== Connect to Eureka ====
*From the command line on the Colorado machine,
ssh '''''username'''''@eureka.alcf.anl.gov
*Enter 4 digit pin, followed by the number on the CRYPTOCard

==== Submit Interactive Job ====
*From the command line on Eureka, <code>cp /home/jmartin/qsub_interactive_command.sh</code> to your home directory. Open <code>qsub_interactive_command.sh</code> and change the total time you want to run paraview (time), and the allocation your account is under (account).
./qsub_interactive_command.sh '''''nodes'''''
where '''''nodes''''' is the total number of nodes you want. Each node has 8 cores, and 32 GB of memory.

=== Janus (CUBoulder RC Computing) ===
Video Tutorial (use the paths below, NOT the ones in the Video)
http://fluid.colorado.edu/~matthb2/janus/pv_on_janus.html

==== Running the UI on Portal0 ====
soft add @paraview-3.8.0
soft add +paraview-3.8.0-gnu-ompi-covis
vglrun paraview

and then start and connect to the server:

==== Starting the Server on Janus ====
. /projects/jansenke/matthb2/env-gnu.sh
qsub -q janus-debug /projects/jansenke/matthb2/pvserver-gnu_runscript-sysgl.sh

and use checkjob or look at the output files to figure out which node your rank0 is on and connect ParaView to that (or change it to use reverse connections if you prefer).

=== Tukey (ALCF) ===
==== Video Tutorial about how to run a pvserver-syncio in parallel on the Tukey visualization nodes and connect the pvserver to a ParaView Gui running on portal0 at Colorado ====
http://fluid.colorado.edu/~mrasquin/Documents_HIDE/Tukey/ParaviewOnTukeyFromPortal0/index.html

This video can be copied from /users/mrasquin/public_html/Documents_HIDE/Tukey/ParaviewOnTukeyFromPortal0 on the viz nodes.

==== Video Tutorial about how to run a pvserver-syncio in parallel on the Tukey visualization nodes and connect the pvserver to a ParaView Gui running on the Tukey login node ====
https://fluid.colorado.edu/~mrasquin/phasta/ParaViewOnTukey/index.html

This video can be copied from /users/mrasquin/public_html/Tukey/ParaviewOnTukeyThroughVNC on the viz nodes.

Note that because vncserver on the Tukey head node does not support OpenGL, this method does not allow the export of png pictures from the ParaView Gui. Indeed, the result will be completely fuzzy. The first method is therefore strongly recommended.

← Older revision		Revision as of 19:28, 11 November 2022
Line 22:		Line 22:
	Once the server is running and "Waiting for client..." you should launch ParaView on the Viz Nodes and select the connect to server icon (just to the right of the open file icon at the top of the screen). From here, using the listed <code>cc*</code> number, you will need to configure the server connection if you do not have one configured for the <code>cc</code> number. This is done by selecting "Add Server" and then populating the "Edit Server Configuration" page. The name of the server should be the <code>cc</code> number, the host field will be <code>cc*.cooley.pub.alcf.anl.gov<code> and the port is <code>8000</code>. From here you can select configure and then connect.		Once the server is running and "Waiting for client..." you should launch ParaView on the Viz Nodes and select the connect to server icon (just to the right of the open file icon at the top of the screen). From here, using the listed <code>cc*</code> number, you will need to configure the server connection if you do not have one configured for the <code>cc</code> number. This is done by selecting "Add Server" and then populating the "Edit Server Configuration" page. The name of the server should be the <code>cc</code> number, the host field will be <code>cc*.cooley.pub.alcf.anl.gov<code> and the port is <code>8000</code>. From here you can select configure and then connect.

−	If, upon connection, you need to load the SyncIO plugin, these can be found for multiple versions of ParaView at <code>/lus/theta-fs0/projects/PHASTA_aesp/ParaView/ParaViewSyncIOReaderPlugin</code>.	+	If, upon connection, you need to load the SyncIO remote plugin, these can be found for multiple versions of ParaView at <code>/lus/theta-fs0/projects/PHASTA_aesp/ParaView/ParaViewSyncIOReaderPlugin</code>.

@@ Line 1: / Line 1: @@
-Here are instructions for running Paraview on some selected remote machines.
+Here are instructions for running ParaView on some selected remote machines.
 In general, this involves:
@@ Line 6: / Line 6: @@
 # Launching the Paraview server on the session
 # Connecting to the remote Paraview server through a local Paraview instance
 == Retired Machines ==

← Older revision		Revision as of 23:11, 13 July 2020
Line 52:		Line 52:

	Note that because vncserver on the Tukey head node does not support OpenGL, this method does not allow the export of png pictures from the ParaView Gui. Indeed, the result will be completely fuzzy. The first method is therefore strongly recommended.		Note that because vncserver on the Tukey head node does not support OpenGL, this method does not allow the export of png pictures from the ParaView Gui. Indeed, the result will be completely fuzzy. The first method is therefore strongly recommended.
		+
		+	[[Category:Paraview]]

@@ Line 2: / Line 2: @@
 In general, this involves:
-# Launching an interactive job using the machine's job scheduler,
+# Launching an interactive job using the machine's job scheduler
 # Loading whatever required software is needed on the session
 # Launching the Paraview server on the session

← Older revision	Revision as of 18:01, 18 September 2022
(No difference)

@@ Line 20: / Line 20: @@
 where '''''nodes''''' is the total number of nodes you want. Each node has 8 cores, and 32 GB of memory.
-=== Janus (CUBoulder RC Computing) ===
+=== Janus (CUBoulder Research Computing) ===
 Video Tutorial (use the paths below, NOT the ones in the Video)
 http://fluid.colorado.edu/~matthb2/janus/pv_on_janus.html

← Older revision	Revision as of 22:44, 13 July 2020
(No difference)

@@ Line 34: / Line 34: @@
 === Tukey (ALCF) ===
-==== Video Tutorial about how to run a pvserver-syncio in parallel on the Tukey visualization nodes and connect the pvserver to a ParaView Gui running on portal0 at Colorado ====
+==== ParaView GUI running on portal0 at Colorado ====
    http://fluid.colorado.edu/~mrasquin/Documents_HIDE/Tukey/ParaviewOnTukeyFromPortal0/index.html
 This video can be copied from /users/mrasquin/public_html/Documents_HIDE/Tukey/ParaviewOnTukeyFromPortal0 on the viz nodes.
-==== Video Tutorial about how to run a pvserver-syncio in parallel on the Tukey visualization nodes and connect the pvserver to a ParaView Gui running on the Tukey login node ====
+==== ParaView GUI running on the Tukey login node ====
    https://fluid.colorado.edu/~mrasquin/phasta/ParaViewOnTukey/index.html