-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add pace remote interactive documentation
- Loading branch information
Showing
1 changed file
with
89 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,89 @@ | ||
# Interactive Visualization on Phoenix | ||
This tutorial outlines how to perform interactive remove visualization on GATechs Phoenix cluster. | ||
Using remote visualization allows for the visualization of much larger simulations interactively, without the need for Paraview's batch mode | ||
|
||
## Step 1 - Setting up your Environment | ||
Begin by downloading the .zip file here (https://gatech.box.com/s/1diud4lgequvuie5fg2ac6hcvoelndu5). | ||
This file contains two things | ||
|
||
- A bash script to automate the job submission process and provide instructions for remote connection. | ||
|
||
- A prebuilt Paraview 5.11 binary | ||
|
||
Place the file `paceParview.zip` in you scratch direction on Phoenix and unzip is using `unzip paceParaview.zip`. | ||
Enter the new directory `paceParaview` and run `tar -xvf ParaView-5.11.0-egl-MPI-Linux-Python3.9-x86_64.tar.gz` to decompress the compiled binary. | ||
Now that you have the binary on Phoenix, you'll need to download Paraview 5.11 on your local machine. | ||
Paraview binaries can be downloaded here (https://www.paraview.org/download/). | ||
Make sure to select `v5.11` from the version drop down bar and install a `5.11.0` version of Paraview. | ||
|
||
## Step 2 - Customize the Bash Script | ||
While all of the options for the bash script could be passed as command line arguments, it saves time to hard code certain options that are unlikely to change. | ||
The following is a list of required and suggested updates to make to `pace-paraview-server`. | ||
|
||
- (Optional) Update line 4 to customize the job name that will show up in the scheduler | ||
|
||
- (Required) Update line 6 to point towards the location of you Paraview bin directory | ||
|
||
- (Optional) Update line 51 to reflect the default account you'll use to run Paraview jobs | ||
|
||
- (Optional) Update line 52 to reflect the default wall time requested for your job | ||
|
||
## Step 3 - Running pace-paraview-server | ||
Before running `pace-paraview-server` for the first time, you'll need to update its permissions by running `chmod u+x pace-paraview-server` in your command line. | ||
Once this has been done, you can run `./pace-paraview-server` with the following options: | ||
|
||
- `--account` specifies the charge account to use for the job. | ||
If you updated line 51 of `pace-paraview-server` to reflect a default account, this option is optional, otherwise it is required. | ||
|
||
- `--nodes` specifies the number of nodes to request (default 1) | ||
|
||
- `--mem` specifies the memory per node to request (default is to request all memory) | ||
|
||
- `--gres` specifes the GPU resources to request. | ||
These instructions have only been verified to work with `--gres gpu:V100:2`. | ||
|
||
- `--time` specifies the time limit for your job. | ||
This option is optional and defaults to whatever is set on line 52 of `pace-paraview-server`. | ||
|
||
Once you run `./pace-paraview-server <options>`, you will see | ||
|
||
``` | ||
Submitted batch job <job #> | ||
Wating for ParaView server to start. This may take several minutes ... | ||
``` | ||
|
||
in your terminal. | ||
Once the job starts, a dialogue containing the following instructions will appear detailing how to connect to the remote server from your local machine. | ||
|
||
``` | ||
1) Press SHIFT + ~ then SHIFT + C to open an SSH console (The prompt 'ssh>' should appear on the next line) | ||
***Note: '~' MUST be the first character on the line to be recognized as the escape character, in which case it will not appear on your terminal.*** | ||
***If you see the '~' character when you start typing, delete it, hit 'ENTER' and type 'SHIFT' + '~' + 'C' again.*** | ||
2) Type -L 8722:<nodeIdentifier>:53723 and then ENTER | ||
3) In the ParaView 5.11 desktop client, create the server configuration. | ||
( screenshots are at https://docs.pace.gatech.edu/slurm-software/paraview/#starting-the-paraview-client-on-your-computer ) | ||
Set the 'Server Type' to: | ||
Client / Server | ||
Set the 'Host' to: | ||
localhost | ||
Set the 'Port' to: | ||
8722 | ||
If you have previously configured the server cs://localhost:8722 in ParaView, | ||
you can re-use it and do not need to create a new configuration. | ||
4) When your work is finished, check the Slurm queue (squeue --name=paraview) | ||
and end your ParaView job if it is still active (scancel --name=paraview) | ||
``` | ||
|
||
Depending on your local version of openSSH, you may need to add the following to you `/.ssh/config` file for `SHIFT + ~ + C` to work as expected. | ||
|
||
``` | ||
Host * | ||
EnableEscapeCommandline yes | ||
``` | ||
|
||
## Step 4 - Connecting from your Local Machine | ||
Once you have `Paraview5.11.0` open on your machine, select `file -> Connect..` to open the remote connection dialogue box. | ||
If you've already set up the pace connection, simply double-click the existing configuration. | ||
If you have not yet set up the pace connection, click `Add Server`. | ||
This will bring up a new dialogue box where you can specify a configuration name and set the `Port` to 8722. | ||
Once this is done, click `configure` and then `save` on the next dialogue box. |