Software stacks¶
Analysis software at Purdue AF can come from several sources, listed here from most to least recommended:
- Pixi environments — the recommended way to manage analysis software.
- Conda environments — supported; use Pixi for new projects.
- LCG stacks distributed via CVMFS — useful for special cases such as CUDA-enabled ROOT.
- Apptainer/Singularity images via CVMFS — a last resort for software that requires a different operating system.
Pixi environments¶
Pixi is a modern package manager and a successor of Conda/Mamba. It is significantly faster than Conda, resolves Conda and PyPI dependencies together, and enforces reproducibility via lock files.
Unlike Conda environments, Pixi environments are meant to be project-specific:
the environment definition (pixi.toml) and the environment itself live in the
project directory, next to your analysis code. A detailed guide on how to start
using Pixi is available here: Pixi guide.
The global Pixi environment¶
In addition to project-specific environments, we provide a global Pixi
environment at /work/pixi/global/, which contains all common HEP analysis
packages and ML libraries. It is a good starting point for new projects and for
code that is not part of any Pixi project.
List of packages in the global environment (pixi.toml configuration)
The canonical definition lives in
pixi/global/pixi.toml
in this repository:
[workspace]
authors = ["Dmitry Kondratyev"]
channels = ["conda-forge"]
name = "pixi-global"
# The cuda entry is the __cuda virtual package the GPU builds need.
platforms = [{ platform = "linux-64", cuda = "12.4" }]
# A lock written by a newer pixi is not readable by an older one.
requires-pixi = ">=0.81"
version = "0.1.0"
[dependencies]
awkward = "*"
awkward-pandas = "*"
bokeh = "3.10.0.*"
# boost = "*"
cabinetry = "*"
ca-certificates = "*"
certifi = "*"
click = "*"
cms-combine = "==11.0.0"
coffea = "2026.9.0.*"
correctionlib="*"
dask = "*"
dask-gateway = "*"
dask-histogram = "*"
dask-jobqueue = "*"
dask-memusage = "*"
dask-ml = "*"
dask-xgboost = "*"
distributed = "*"
eigen = "*"
fsspec-xrootd = "*"
gcc_linux-64 = "*"
graphviz = "*"
gpustat = "*"
gsl = "*"
gxx_linux-64 = "*"
h5py = "<3.16.1"
hepdata-lib = "*"
hist = "*"
ipykernel = "*"
ipympl = "*"
ipywidgets = "*"
jupyter = "*"
jupyter-sshd-proxy = "0.3.0.*"
law = "*"
lhapdf = "*"
libgcc-devel_linux-64 = "*"
libstdcxx-devel_linux-64 = "*"
lmfit = "*"
# madminer = "*"
mamba = "*"
matplotlib = "*"
mimesis = "*"
# floor: an unconstrained solve can pick mlflow 1.x, whose protos fail under protobuf >= 4
mlflow = ">=3"
mplhep = ">=1.1.2"
numba = "*"
numpy = "*"
omegaconf = "*"
openssl = "*"
openssh = "*"
optuna = "*"
pandas = "*"
particle = "*"
pcre2 = "*"
pip = "*"
plotly = "*"
py-spy = "*"
pyarrow = "*"
pycurl = "*"
pydot = "*"
pyhf = "*"
pyjuliacall = "*"
pytest = "*"
python = "3.13.*"
python-graphviz = "*"
pytorch = "2.14.*"
# floor: Ray Train clusters run from this env, with Ray's token authentication (2.52+)
ray-default = ">=2.52"
ray-train = "*"
rucio-clients = "*"
root = ">=6.40.2,<6.41"
scikit-learn = "*"
scikit-optimize = "*"
scipy = "*"
seaborn = "*"
setuptools = "*"
sysroot_linux-64 = "*"
tbb = "*"
torch-geometric = "*"
tqdm = "*"
uncertainties = "*"
uproot = "*"
vdt = "*"
vector = "*"
wrapt = "<2"
xgboost = "*"
# The version pixi/base pins; root_base links libxrootd 6.x on its own.
xrootd = "5.9.2.*"
zuko = "*"
[pypi-dependencies]
cmsstyle = "*"
dbs3-client = "*"
phyprakit = "*"
scalpl = "*"
servicex = "==3.3.1"
termplotlib = "*"
xgbfir = "*"
roastcoffea = "*"
pyroscope-io = "*"
If a package that you consider common is missing from the global environment, let us know — we update it regularly.
Jupyter kernels¶
We provide multiple types of Jupyter kernels to execute analysis code in notebooks.
Pixi kernels¶
There is no one-to-one mapping between Pixi environments and Jupyter kernels. Instead, we provide two special Pixi kernels:
- Python (pixi global) — always uses the global environment at
/work/pixi/global/. - Python (pixi project-aware) — uses the Pixi project that contains the
notebook: the nearest
pixi.toml, orpyproject.tomlwith a[tool.pixi]table, in the notebook's directory or one of its parents. It never uses the global environment: for a notebook outside any Pixi project, choose Python (pixi global).
Before starting, the project-aware kernel runs pixi install for the project's
environment. When it finds no project, or cannot use the one it finds, the
kernel still starts, but every cell fails with the error that stopped it. To be
usable, the project must:
- have the
ipykernelpackage in its environment; - be writable by you — a shared project on
/depot/owned by someone else, or/work/pixi/global/itself, is not; copy itspixi.tomlinto a project of your own (Pixi guide), or use Python (pixi global); - not be under
/home/(Pixi storage locations); - be stored in a publicly readable directory.
Conda kernels¶
Conda environments are discovered automatically and appear as kernels if they
have the ipykernel package installed and are stored in a
publicly readable directory —
see Creating Conda environments and Jupyter kernels.
ROOT C++ kernel¶
This kernel provides an interactive interface to the ROOT command line, allowing you to execute ROOT macros and produce plots inside Jupyter notebooks.
See also
LCG kernels¶
These kernels are based on LCG "views" loaded via CVMFS:
LCG_106b— the standard LCG software stack;LCG_106b_cuda— contains the CUDA-enabled ROOT build and is suitable for running RooFit on GPUs.
Combine¶
Combine is
included in the global Pixi environment (package cms-combine) — see
Using Combine at Purdue AF.
CMSSW¶
CMSSW releases are available via CVMFS in the usual way:
Note that Purdue AF is based on an EL8 system (RHEL8-compatible, el8/slc8
architectures), so CMSSW releases built for other
architectures (e.g. slc7) must be run inside an Apptainer container such as
cmssw-el7 (see below, and the MC generation guide for a
worked example).
Apptainer / Singularity images¶
In rare cases when you need to run code that requires a specific operating system, you can load Apptainer/Singularity images via CVMFS.
Example of loading an Apptainer image based on EL7:
Warning
Your Analysis Facility session already runs in a Docker container. Launching Apptainer inside the AF session leads to a "container-in-container" setup, which is not guaranteed to always work as intended.
We do not recommend using Apptainer at Purdue AF unless it is absolutely needed.