Visit Remote Host
A. Setting HPCC host profile in Visit:
Important Notes
Visit requires matching versions on the client (your PC) and the server (rider). For example, Visit 6.0.x matches with Visit6.0.1, 6.0.2 etc.
The menu might have been slightly changed in newer versions.
Remote Host
Install Visit in you PC following the instructions at https://wci.llnl.gov/simulation/computer-codes/visit/downloads.
Open Visit in your PC
Under Options menu, choose Host Profiles …
Click New on the lower left of the window
Host nickname: rider
Remote host name: rider.case.edu
Path to VisIt Installation: /usr/local/visit/2.10.0
Username: Enter your Case user name
Tunnel data connections through SSH: Check box to enable; DO NOT check ssh and sshport
Change the tab to Launch Profiles in the upper right of the window.
Create a profile by clicking New in the middle of the window.
Enter the following in the Settings tab:
Profile name: hpc-parallel
Choose the Parallel tab and configure as follows:
Launch parallel engine Check box to enable
Parallel launch method: srun
Partition / Pool / Queue: <optional> or <use any one of the available queues>
Default number of processors: 4 or <requirement>
Default number of nodes: 1 or <requirement>
Default Bank / Account:
Default Time Limit: 01:00:00 (set this as per your needs)
Click Apply on the lower left of the window and then click Dismiss.
(Very Important) From the Options menu, choose Save Settings.
B. Connecting to HPCC from Visit Application running on your PC:
Start the VisIt application on your computer.
In the VisIt main window under Sources click the Open button.
Select the drop down list of hosts at the top.
In the Host field, use drop down button on right and choose hpclogin.
You may get a prompt for password to allow VisIt to connect to HPCC.
Once connected to HPCC, you should be able to see a listing of your home directory
C. Demo and Test:
Follow the "Simple Visit Demo" in "HPC Visit Guide"
You will get another window showing that the job has been submitted (with number of servers depending on the number of cores)and it is waiting for the job to run and start.
If the machine has nodes available your job should start in a short time.
See the status of your job:
sq | grep <username>
(Note that the status shows that 4 processors have been used)
References:
http://www.sdsc.edu/us/resources/gordon/docs/gordon_visit.html
http://www.sdsc.edu/support/user_guides/tutorials/visit.html