At the core of bwVisu are the provided visualization applications. These are containerized using the container solution Singularity.
Applications in bwVisu have only a few restrictions. These being namely:
singularity run IMAGE_NAMEwith the appropriate executable set as run command. This should be the case for many applications already available on public registries.
bwVisu is in general compatible with any graphical application that fulfills the above mentioned restrictions. Example applications can be found in the GitLab group
bwVisu provides every job with an accelerated Xorg as this is necessary to have hardware acceleration for your application. Xorg itself will be provided by an image (probably named
bwvisu_xorg.sif). This Xorg is modified to patch out the need for virtual consoles and can be started by non-root users. This is necessary for providing an X server for every job so that users do not need to share one. For more information see this article and this issue.
You can get the bwVisu Xorg image via
singularity pull docker://registry-gitlab.urz.uni-heidelberg.de/urz-sb-fire/sg-dic/bwvisu/bwvisu-images/urz-sb-fire-bwvisu-driver/centos-7-5
There are a number of steps involved before a user can actually interact with a visualization application. Here is a rough breakdown of the steps.
app bundles. See here for more information on how to provide these app bundles.
singularity runcommand with a couple of other options.