Singularity container for sPHENIX and EIC-sPHENIX allow collaborators to run sPHENIX RCF/SDCC environment with the nightly builds on your local computers or on external high-performance computing clusters.
This repository includes the instruction and local update macro for this Singularity container.
Daily validations: updatebuild.sh --build=new
sPHENIX and EIC-sPHENIX software can be obtained to your local computing environment in two ways. You can use both - there is no collision between these two options. Which you use is determined by the start of the singularity container (look closely - for option 1 you use /cvmfs:/cvmfs which mounts our cvmfs volume under /cvmfs, for option 2 you use cvmfs:/cvmfs which mounts your local copy under /cvmfs)
- Option-1 Mount sPHENIX CVMFS: sPHENIX container, software and builds are distribute on CVMFS since Nov 2018. Like RCF/SDCC computing cluster at BNL, external collaborating computing center could also mount the
/cvmfs/sphenix.opensciencegrid.org(preferred choice) or/cvmfs/sphenix.sdcc.bnl.gov/CVMFS repository, which automatically obtain, buffer and update all sPHENIX build files./cvmfs/sphenix.opensciencegrid.orgis also distributed by default throughout the Open Science Grid. - Option-2 Download sPHENIX build via HTTPS archive: one can also directly download the files for sPHENIX build to a local folder via the nightly refreshed HTTPS archive.
The advantage of Option-1 Mount sPHENIX CVMFS is that it mounts all sPHENIX builds and software and perform automatic caching and updates. This would be suitable for the case of a computing center or server environment. However, it requires constant network connection to function. Therefore, if you wish to use sPHENIX/EIC-sPHENIX software on a laptop during travel, Option-2 Downloading sPHENIX build via HTTPS archive would work best. All download instructions are the same for sPHENIX and EIC-sPHENIX.
Note: although singularity container are supported under MacOS and Windows Linux Subsystem, it runs best under Linux. Therefore, for Windows and Mac user, it would produce most smooth experience to run Option2 within a Linux virtual machine, such as an Unbuntu VirtualBox.
-
On your local system, install Singularity.
- Note: Singularity installation may require host to support local compilation. E.g. on Ubuntu, it can be obtained via
sudo apt-get install libtool m4 automake
- Note: Singularity installation may require host to support local compilation. E.g. on Ubuntu, it can be obtained via
-
Install CVMFS from CERN. CERN support build packages under (various Linux distribution and MAC)[https://cernvm.cern.ch/portal/filesystem/downloads].
- Note: for loading
/cvmfs/sphenix.opensciencegrid.orgby default, you may need to add following to/etc/cvmfs/default.local.
- Note: for loading
CVMFS_STRICT_MOUNT=no
CVMFS_REPOSITORIES=oasis.opensciencegrid.org
CVMFS_HTTP_PROXY="DIRECT"
- [Optional] this step only applies to mounting
/cvmfs/sphenix.sdcc.bnl.gov/in order to reproduce identical CVMFS structure with SDCC/RCF. However, use of/cvmfs/sphenix.opensciencegrid.orgis more convenient and this step can be skipped.
Copy these three configuration and key files to your local computer from RCF (e.g. from any interactive RCF computer nodes):
/etc/cvmfs/keys/sdcc.bnl.gov/sphenix.sdcc.bnl.gov.pub
/etc/cvmfs/config.d/sphenix.sdcc.bnl.gov.local
/etc/cvmfs/domain.d/sdcc.bnl.gov.local
Add sphenix.sdcc.bnl.gov to CVMFS_REPOSITORIES in /etc/cvmfs/default.local. e.g.
CVMFS_REPOSITORIES=sphenix.sdcc.bnl.gov
You may also need to specify CVMFS_HTTP_PROXY in /etc/cvmfs/default.local from your local computing to access the http://cvmfs.sdcc.bnl.gov:8000/ server. For direct network access, CVMFS_HTTP_PROXY=DIRECT would work.
After completing step 2 and 3, please confirm you can read local path /cvmfs/sphenix.sdcc.bnl.gov/, which should show same content as that on RCF interactive nodes.
- launch singularity container for sPHENIX and EIC-sPHENIX with following command
singularity shell -B /cvmfs:/cvmfs /cvmfs/sphenix.opensciencegrid.org/singularity/rhic_sl7_ext.sif
source /cvmfs/sphenix.opensciencegrid.org/default/opt/sphenix/core/bin/sphenix_setup.sh -n # setup sPHENIX environment in the singularity container shell. Note the shell is bash by default
root # give a test
For Singularity v3+, in particular CERN computing users: rhic_sl7_ext.sif might be slow to load under certain Singularity security settings at your computing center. In that case, please load with an alternative image: singularity shell -B /cvmfs:/cvmfs /cvmfs/sphenix.opensciencegrid.org/singularity/rhic_sl7_ext
-
On your local system, install Singularity.
- Note: Singularity installation may require host to support local compilation. E.g. on Ubuntu, it can be obtained via
sudo apt-get install libtool m4 automake
- Note: Singularity installation may require host to support local compilation. E.g. on Ubuntu, it can be obtained via
-
Download this repository:
git clone https://github.com/sPHENIX-Collaboration/Singularity.git
cd Singularity/
- Run the download/update macro updatebuild.sh.
./updatebuild.sh
This macro download the current release of sPHENIX/EIC-sPHENIX Singularity container and nightly build libs. The total download size is about 5 GB and decompressed disk usage is about 10 GB. Two build versions are supported with default as the new build, as well as the root5 build with ./updatebuild.sh --build=root5. The new build with gcc 8.3 can be downloaded using ./updatebuild.sh --sysname=gcc-8.3
- Start the container with
singularity shell -B cvmfs:/cvmfs cvmfs/sphenix.sdcc.bnl.gov/singularity/rhic_sl7_ext.sif
source /opt/sphenix/core/bin/sphenix_setup.sh -n # setup sPHENIX environment in the singularity container shell. Note the shell is bash by default
root # give a test
Please note the slight difference in singularity shell commands for option 1 and option 2
- To get daily build update, run the download/update macro updatebuild.sh to sync build files again.
After entering the Singularity container, you can source sPHENIX environment and interact with it in the same way as on RCF:
computer:~/> singularity shell <options depending on which of the two downloading options above>
Singularity: Invoking an interactive shell within container...
Singularity rhic_sl7_ext.sif:~/> source /opt/sphenix/core/bin/sphenix_setup.sh -n
Singularity rhic_sl7_ext.sif:~/> lsb_release -a # Verify same environment shows up as that on RCF
LSB Version: :core-4.1-amd64:core-4.1-ia32:core-4.1-noarch
Distributor ID: Scientific
Description: Scientific Linux release 7.3 (Nitrogen)
Release: 7.3
Codename: Nitrogen
This bring up a shell environment which is identical to sPHENIX RCF. Meanwhile, it use your local file system for non-system files, e.g. it directly work on your code or data directories. Singularity container also support running in the command mode or background mode.
Next, please try the sPHENIX simulation tutorial.
Please discuss on sPHENIX software email list and meeting regarding any question or suggestion.
Singularity runs under linux OS. But in macOS, it require another layer of virtual machine to generate a linux environment first (read more on Singularity docs). The easiest approach would be using the container within a Unbuntu VirtualBox. Alternatively, Here is a more detailed guild on the macOS installation of sPHENIX container.
The easiest approach is to install Virtual Box running our within a Unbuntu VirtualBox.
The container is built for batch computing. It could be tricky to bring up 3D-accelerated graphics for Geant4 display.
- On Linux, binding local X IPC socket folder to the singularity container could help enabling local hardware 3D acceleration, e.g.
singularity -B /tmp/.X11-unix:/tmp/.X11-unix ....followed withsetenv DISPLAY unix:0.0in the container. - On MacOS and Windows, accelerated graphics runs well with a Linux VirtualBox with graphical acceleration enabled in the VirtualBox.
- On MacOS John H. have developed a note on how to get the 3D graphics working on MAC.
Occasionally, local download cache can become corrupt, e.g. after an interrupted updatebuild.sh call. If you encounter a problem executing container, it is always useful to first try clean up the local download buffer by removing the ./cvmfs folder and download again. Or you can run ./updatebuild.sh --clean <other options> which force a clean download (default is incremental updates).
If you have RCF credentials, you can also compare your local output with the daily test runs of the default simulation macro in the container following these links: updatebuild.sh --build=new