Skip to main content
Yanked

This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 2.13.0.1001 instead.

License Documentation GitHub release latest packaged version(s) OpenSSF Scorecard OpenSSF Best Practices LFX Health Score LFX Contributors LFX Active Contributors

ADIOS2 : The Adaptable Input Output System version 2

ADIOS2 is an adaptable, scalable, and unified framework for scientific data I/O. It transports self-describing variables and attributes across files, networks, and memory using a single API, and is used in production on the world's largest supercomputers.

Features

  • Unified I/O API: same interface for files, wide-area networks, and in-memory staging; switch transport without changing application code
  • BP format: self-describing binary-packed format (.bp) with rapid metadata extraction and built-in compression support
  • MPI-native: scales from laptop to petabyte workloads on the largest HPC systems; serial use also supported
  • Streaming and step-based: asynchronous, grouped variable transport with an explicit steps abstraction for in-situ and in-transit workflows
  • Multiple language bindings: C++17, Python, C99, Fortran 90, and Matlab
  • Compression operators: ZFP, SZ3, MGARD, Blosc2, PNG, and others
  • Encryption operators: symmetric (AES-256-GCM) and asymmetric encryption available for data at rest
  • In-situ/in-transit engines: SST and DataMan engines for code coupling over RDMA, MPI, and TCP without touching files
  • DAOS engine: writes and reads datasets through the DAOS data plane (native object API) directly, with no dfuse or POSIX interception required
  • Plugin support: extend ADIOS2 with custom engines and operators via shared-library plugins at runtime
  • Security-focused: committed to OpenSSF best practices; see the OpenSSF Scorecard and Best Practices badge
  • Widely available: packaged for major Linux distributions, Conda, Spack, Homebrew, and vcpkg; validated on U.S. DoE supercomputers including Frontier, Summit, and Perlmutter
  • HDF5 VOL: existing HDF5 applications can use ADIOS2 as a backend transparently via the HDF5 Virtual Object Layer

Example

import adios2
import numpy as np

data = np.array([1.0, 2.0, 3.0, 4.0, 5.0])

# Write to a BP file
with adios2.Stream("data.bp", "w") as f:
    f.write("data", data)

# Read it back
with adios2.Stream("data.bp", "r") as f:
    for _ in f.steps():
        result = f.read("data")

print(result)  # [1. 2. 3. 4. 5.]

Install ADIOS2

Python (PyPI):

pip install adios2

From source: See the install documentation and scripts/runconf/runconf.sh for a CMake configuration example. Once installed, refer to Linking ADIOS2.

Packages

Platform Package
Summary latest packaged version(s)
Conda Conda Version
Spack Spack package
Homebrew Homebrew package
Ubuntu 24.04 Ubuntu 24.04 package
Ubuntu 26.04 Ubuntu 26.04 package
Debian Unstable Debian Unstable package
Arch Arch Linux package
OpenSUSE TumbleWeed openSUSE Tumbleweed package
Nix unstable nixpkgs unstable package
vcpkg Vcpkg package
Dockerhub Docker Image Version

An Apptainer/Singularity SIF image is also published to GHCR on every master push:

apptainer pull adios2.sif oras://ghcr.io/ornladios/adios2-apptainer-sif-master-x64:latest

Notes for packagers other than HPC sysadmins

ADIOS2 has a wide spectrum of optional features, from a small, dependency-free core to specialized backends that pull in heavy or uncommon third-party libraries. It is also a research project, so those backends come and go, and the sites that rely on them usually build from source for each environment (or via Spack) rather than from a package manager. Therefore we recommend a lean build, not trying to satisfy all possible optional dependencies.

Core (no or trivial dependencies):

  • BP3 / BP4 / BP5 file engines (.bp format), no external dependencies
  • SST streaming engine (TCP by default)
  • C and C++ bindings

Common options (widely packaged):

  • MPI, recommended but not required
  • Python, Fortran bindings
  • HDF5 (interop and the HDF5 VOL)
  • Compression: ZFP, SZ3, BZip2, Blosc2, PNG
  • Campaign (requires SQLite3 and ZLIB, both lightweight and commonly available)
  • CURL (HTTPS remote data access)

Specialized (of interest only to specific workflows):

  • Additional compression / refactoring: MGARD, SZ (for existing data only), LibPressio, BigWhoop, ProDM
  • GPU: CUDA, Kokkos
  • Encryption: Sodium (libsodium; backs both the EncryptionOperator and encrypted Campaign metadata)
  • Remote / storage backends: XRootD, OpenSSL (TLS for HTTPS remote access), AWSSDK (S3), DAOS
  • In-situ visualization: Catalyst (ParaView)

Legacy engines and transports (unmaintained, off by default):

  • DataMan, SSC, MHS, DataSpaces, IME

These older staging and coupling engines, and the DDN IME transport, are no longer actively maintained and are candidates for future removal. They are disabled by default and must be enabled explicitly (for example -DADIOS2_USE_MHS=ON) if needed. ZeroMQ is required only by the DataMan engine and is likewise off by default, so a default build pulls in no ZeroMQ dependency.

HPC network transports (RDMA)

The SST engine reaches full performance through RDMA data planes that depend on fabric libraries: libfabric (InfiniBand/verbs and HPE-Cray Slingshot/CXI; detected automatically when SST is enabled), UCX (ADIOS2_USE_UCX), and Mercury (ADIOS2_USE_Mercury). These matter on systems with an RDMA interconnect, where an HPC-targeted package should install one or more of libfabric, UCX and Mercury before building so SST picks them up. On machines without an RDMA network they provide no benefit may cause trouble (SST will fallback to TCP and or MPI dataplanes if RDMA is not directly available.) General-purpose packages can safely leave them out.

A default build

A default configuration is already lean: the legacy engines above are off, and every other optional feature is enabled only when its dependency is already present. Enabling the common options is a matter of turning them on explicitly, for example:

cmake -DADIOS2_USE_HDF5=ON -DADIOS2_USE_Python=ON -DADIOS2_USE_MPI=ON ..

Questions about whether a given feature is worth packaging are welcome on GitHub Discussions.

Resources

Community

ADIOS2 is an open source project: questions, discussion, and contributions are welcome.

Institutions

ADIOS2 is developed as a multi-institutional collaboration between:

License

ADIOS2 is licensed under the Apache License v2.0. See the accompanying Copyright.txt for more details.

Metadata

Release files for adios2-mpi 2.13.0.1000

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for adios2-mpi 2.13.0.1000
File Actions
adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64 Details for adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_x86_64.whl
adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64 Details for adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_aarch64.whl
adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_x86_64.whl CPython 3.12 abi3 Linux glibc 2.28+ x86-64 Details for adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_x86_64.whl
adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_aarch64.whl CPython 3.12 abi3 Linux glibc 2.28+ ARM64 Details for adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_aarch64.whl
adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64 Details for adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_x86_64.whl
adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64 Details for adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_aarch64.whl
adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64 Details for adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_x86_64.whl
adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64 Details for adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_aarch64.whl
adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64 Details for adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_x86_64.whl
adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ ARM64 Details for adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_aarch64.whl

Total release size: 164.4 MB

Release files / adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_x86_64.whl

Download URL adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_x86_64.whl
Size 17.1 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
91a420ec8824dcfeff2ba99de8979a9cca6ac3cde4ba95789644bd0a72c1b563
BLAKE2b-256 checksum
How to use checksums
2f108978e5e98fd4c66905257c1e084e1178fd733a03073c74265f123da41c81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_aarch64.whl

Download URL adios2_mpi-2.13.0.1000-cp314-cp314t-manylinux_2_28_aarch64.whl
Size 15.8 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
cc7764eaa9783adcd7c6fc0731318a5877308a7632974acbb139bd247b4515c4
BLAKE2b-256 checksum
How to use checksums
34171bcfaab63fff0215a84812e905e0a36e1d2c66d41d6c31d1982af29ffd9a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_x86_64.whl

Download URL adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_x86_64.whl
Size 17.1 MB
Tags CPython 3.12 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
5043f6f7725f9a52c6ca5bca160364b645a4a4a327c98528bb933f26916f085b
BLAKE2b-256 checksum
How to use checksums
8e55bdfac0b244b9bd932d31a0bd7b148cadede79ef100c1a36ff2d53bfab4d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_aarch64.whl

Download URL adios2_mpi-2.13.0.1000-cp312-abi3-manylinux_2_28_aarch64.whl
Size 15.8 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
34e2945df59de87c12f0bdaefa35c050e8e2e920f1d42988bb2902f3adb9dc65
BLAKE2b-256 checksum
How to use checksums
dd5211a70613a4f3969318b7296f217d099595e1ccf12e528f8a6fee180913bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_x86_64.whl

Download URL adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_x86_64.whl
Size 17.1 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
9748679b1b6766c25b0d4c77e259804fd2cf6d26a66dc1d1d5aef5faaad21968
BLAKE2b-256 checksum
How to use checksums
e98b8cde3b28f75bd6ed75b0ea3ff0beb19409f6f3c8abf1b155fffe177e1087
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_aarch64.whl

Download URL adios2_mpi-2.13.0.1000-cp311-cp311-manylinux_2_28_aarch64.whl
Size 15.8 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
64a10ea040b451d7d35c37420d636a2e934d75428471e4a35b9c4a9b52da9545
BLAKE2b-256 checksum
How to use checksums
b32da9599286342faf0d0b89b4bc3801d039a8c515c4bc3571374d56f91e1cc2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_x86_64.whl

Download URL adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_x86_64.whl
Size 17.1 MB
Tags CPython 3.10 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
12115e375c19e266202d35905340a0528ae72810ef00beb5ff93e7d18d49c5b2
BLAKE2b-256 checksum
How to use checksums
d30ea36af2373e45a630e96ad9633cc3759d0c35371a47cab66e14add5ce2f62
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_aarch64.whl

Download URL adios2_mpi-2.13.0.1000-cp310-cp310-manylinux_2_28_aarch64.whl
Size 15.8 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
6ef20c2bc4c758f2ab8b2d7a6c7d6e9a1d0f0858060fd230904b0be2c8cb11b4
BLAKE2b-256 checksum
How to use checksums
d19321a99fec2c3579f85093a7a71fa9ce584c35097d28b27e5c5c629e3481a3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_x86_64.whl

Download URL adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_x86_64.whl
Size 17.1 MB
Tags CPython 3.9 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
33d3da3d4b825735608a8ac5dd393580af73b7daa183f369b34c6aeccd48a8a6
BLAKE2b-256 checksum
How to use checksums
15cfd95ededa1a8e5bb0e0fed91114cfac1851972d6fd25617b7793a19acb3db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_aarch64.whl

Download URL adios2_mpi-2.13.0.1000-cp39-cp39-manylinux_2_28_aarch64.whl
Size 15.8 MB
Tags CPython 3.9 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
8ed0acee701fc61cb85d7d87161a5a4bc483bf367a95c5785d5a11b8a46b787f
BLAKE2b-256 checksum
How to use checksums
2d7377ea8603b5ed1c4fbff457ba388a6046ace327d964e59126a7785eed9779
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Security for adios2-mpi 2.13.0.1000

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page