search

pnnl / ExaGO

High-performance power grid optimization for stochastic, security-constrained, and multi-period ACOPF problems.
Other
64 stars 8 forks source link

Add E4S container and build cache information to ExaGO documentation #61

Open cameronrutherford opened 10 months ago

cameronrutherford commented 10 months ago

Per @eugeneswalker, E4S has useful build caches and container base images that users can leverage, and so we should document that appropriately:

I've set up a public repo for running nightly Spack development builds of exago@develop for the following GPUs on UO Frank systems:

The last workflow run can be seen from the pipelines page:

The workflow linked above uses the following CI container images:

  • esw123/exago-rocm90a:2023.10.23 (for AMD MI210)
  • esw123/exago-cuda80:2023.10.23 (for NVIDIA A100)

These container images are built using recipes from the following public repository: https://gitlab.e4s.io/uo-public/exago-images

CUDA Image:

ROCM Image:

The binaries used to generate the images above are publicly exposed via standard Spack mirror here:

$ spack mirror add exago-ci https://cache.e4s.io/exago-ci
$ spack buildcache keys -it
$ spack buildcache list -al

The idea is that the CI images contain all the dependencies needed to build ExaGO from source, already installed.

This is what I've been working on. Right now it just runs the basic ctest once the spack dev-build completes.

cameronrutherford commented 9 months ago

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic - we also have ghcr build cache from #85, so these should both be documented