HP Scalable Visualization Array Software - Manual (Page 41)

• sva_startx.sh
This script takes a list of nodes and allocates them as part of an SVA job. Once the nodes are
allocated, an X server starts on each node using the specified (or default) tile geometry. You
are then left with a shell prompt, which you can use to start other programs or job steps.
This is a fully functional script on your PATH. The sva_startx.sh script is located in the
/opt/sva/bin
directory.
• sva_paraview.sh
This script is specifically optimized to launch the ParaView application
2
. It can serve as a
launch command for your use of ParaView. However, it may need site-specific editing before
use. The sva_paraview.sh script is located in the /opt/sva/bin directory.
• sva_ensight82.sh
This script is specifically optimized to launch the EnSight application
3
. It can serve as a
template for your use of EnSight. However, it may need site-specific editing before use. The
sva_ensight82.sh
script is located in the /opt/sva/bin directory.
For more information on the EnSight application, see www.mc.com .
• sva_amiravr.sh
This script is specifically optimized to launch the AmiraVR application
4
. It can serve as a
launch command for your use of AmiraVR. However, it may need site-specific editing before
use. The sva_amiravr.sh script is located in the /opt/sva/bin directory.
For more information on the AmiraVR application, which is developed by Mercury Computer
Associates, see
www.mc.com .
5.2.2 Modifying a Script Template
After selecting a script template, you must edit it to suit your specific application and system
environment. It's a good idea to copy the selected template to your working directory before
making changes. The templates are commented to describe what each template does and what
areas of a template you must edit. These comments are the place to begin when you are ready
to select and edit a script template.
Templates have several major functional areas that execute successively using Data Access
Functions and associated environment variables. These functions and variables are defined in
/opt/sva/bin/sva_init.sh
and draw their default values from the Configuration Data
Files. The SVA Visualization System Software Reference Guide details the functions and their
associated environment variables.
After the script initializes the variables, the main functional areas of the script execute as follows:
1. Allocate: Allocates cluster resources for the visualization job.
The allocation phase launches an HP XC SLURM job using the srun command. A SLURM
Job ID is assigned to the job, which starts a session with the appropriate cluster resources;
for example, the Display Surface and the requested number of display and render nodes.
The number of resources can be specified using command line options in the script.
2. Launch: Starts the visualization session and necessary services on the render and display
nodes; for example, X Servers and DMX.
3. Run: Starts the master application component on the display node and the worker application
components (if any) on the render nodes and display nodes. The run phase also starts any
Chromium components, if appropriate to the job. Where the master runs is based on the
Execution Host value in the Configuration Data Files. This varies based on the Display
2. The ParaView application is not shipped as part of the SVA Kit.
3. The EnSight application is not shipped as part of the SVA Kit.
4. The AmiraVR application is not shipped as part of the SVA Kit.
5.2 Running an Application Using Scripts 41