Singularity container recipes to run the paraview visualizer
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
img
.gitignore
LICENSE
README.md
Singularity
Singularity.nv

README.md

Paraview Visualizer

For instructions on using the full Paraview Web directly from a Singularity container, see this post on AskCyberinfrastructre. Continue reading below for using the Paraview Visualizer via a Docker container, or Singularity container instance.

Singularity

If you don't have nvidia on your host, use the Singularity recipe. If you have nvidia, use the Singularity.nv recipe:

$ sudo singularity build paraview.simg Singularity     # no nvidia
$ sudo singularity build paraview.simg Singularity.nv  # nvidia

If you need it, make a data folder to bind to on the host:

$ mkdir -p /tmp/data

Start the container instance, here we are naming it "visualizer"

$ singularity instance.start --bind /tmp/data:/data paraview.simg visualizer

You should now see the paraview interface running on 127.0.0.1:8080

img/visualizer.png

The mapping to /data is where local web applications will load files from.

Also note that you must stop local web servers, including any Docker applications running on that port.

Credits

Huge thanks to:

Interactive shell

If you need to debug interactively:

$ singularity shell instance://visualizer

Cleaning Up

And to stop the container, you also need sudo

$ singularity instance.stop instance://visualizer

If you are using Singularity 3.0 and up the instance group is now changed to "instance stop" and "instance start"