STEPSS v3.60
STEPSS v3.60
Rebuilt for RAMSES 3.60 (was 3.59), URAMSES 3.60 (was 3.59).
Bundled components
| Component | Version | Upstream release | Published |
|---|---|---|---|
| RAMSES | 3.60 | v3.60 | 2026-08-12 |
| Helios | 1.4.1 | v1.4.1 | — |
| DYNGRAPH | 1.3.0 | v1.3.0 | — |
| CODEGEN | 5.2.0 | v5.2.0 | — |
| URAMSES | 3.60 | v3.60 | 2026-08-12 |
Upstream release notes
RAMSES v3.60 — RAMSES v3.60
Infrastructure release. No solver changes: the simulation results of 3.60 are those of 3.59, and the Nordic voltage-collapse regression gate reproduces the 3.59 baseline on Linux, Windows and macOS.
Release assets renamed
The shared-library bundles are now published as:
ramses-libs-linux-v3.60.zip(ramses.so)ramses-libs-windows-v3.60.zip(ramses.dll)ramses-libs-macos-arm64-v3.60.zip(ramses.so)
They were previously published under a name carrying the Python package's former branding. These archives hold only the RAMSES shared library, so they are named after the engine. The module kits (uramses-modules_*) and the standalone executables (ramses-*-x86_64, ramses-macos-arm64) keep their names.
If you consume these archives from a script, update the names. Anything pinning an earlier tag is unaffected: the previous names remain on the releases that published them.
No action for most users
The stepss Python package and URAMSES both pick this release up through their own automation. Nothing to do if you install through either.
URAMSES v3.60 — RAMSES v3.60
Toolchain and kit provenance
The modules_*/ directories in this release ship pre-compiled RAMSES
libraries and .mod files. They are committed to the repository, so the
Source code archive below (or a clone checked out at this tag) is the
whole release; there are no separate kit downloads to fetch and unpack.
A .mod file can only be read by the gfortran generation that wrote it, so
to add your own Fortran models you need a compiler emitting the same module
ABI version as your platform's kit. make -f <makefile> check-deps verifies
this before building.
| Makefile | Kit directory | Built with | .mod ABI |
Target | Runtime floor |
|---|---|---|---|---|---|
build/Makefile.linux |
modules_l |
GNU Fortran (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0 | 15 | x86_64-linux-gnu |
ldd (Ubuntu GLIBC 2.39-0ubuntu8.7) 2.39 |
build/Makefile.macos |
modules_m |
GNU Fortran (Homebrew GCC 16.1.0) 16.1.0 | 16 | aarch64-apple-darwin24 |
macOS 15.7.7 arm64; needs brew install gcc openblas |
build/Makefile.windows |
modules_wg |
GNU Fortran (Rev5, Built by MSYS2 project) 16.1.0 | 16 | x86_64-w64-mingw32 |
static - self-contained, no MSYS2 runtime required |
Exact compile flags, BLAS build and RAMSES commit for each kit are recorded in
that kit's BUILDINFO.txt, for example modules_l/BUILDINFO.txt.
The Windows/Intel kit in modules_wi/ (used by build/msvs/URAMSES.sln) is
not refreshed by this release: no CI produces Intel-format modules. See
modules_wi/BUILDINFO.txt for what it was last built from.
Infrastructure release. No solver changes: the simulation results of 3.60 are those of 3.59, and the Nordic voltage-collapse regression gate reproduces the 3.59 baseline on Linux, Windows and macOS.
Release assets renamed
The shared-library bundles are now published as:
ramses-libs-linux-v3.60.zip(ramses.so)ramses-libs-windows-v3.60.zip(ramses.dll)ramses-libs-macos-arm64-v3.60.zip(ramses.so)
They were previously published under a name carrying the Python package's former branding. These archives hold only the RAMSES shared library, so they are named after the engine. The module kits (uramses-modules_*) and the standalone executables (ramses-*-x86_64, ramses-macos-arm64) keep their names.
If you consume these archives from a script, update the names. Anything pinning an earlier tag is unaffected: the previous names remain on the releases that published them.
No action for most users
The stepss Python package and URAMSES both pick this release up through their own automation. Nothing to do if you install through either.
Artifact
stepss.jar — SHA-256 4d65e4cc7128e8ced23a97fb639156a842b8bfbbd4e0a7509f2c4e08ae141e5e