# Install hdf5-mpi with Homebrew, Nix File format designed to store large amounts of data. Version 2.1.1 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:hdf5-mpi ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install hdf5-mpi ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#hdf5-mpi ``` Evidence: nixpkgs package indexes: hdf5-mpi from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Package facts - **Package key:** brew:hdf5-mpi - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.1.1 - **Source summary:** File format designed to store large amounts of data - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** BSD-3-Clause - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - h5pcc (cli) - h5perf (cli) - h5pfc (cli) - ph5diff (cli) - h5pcc (alias) - h5perf (alias) - h5pfc (alias) - ph5diff (alias) ## Dependencies - gcc - libaec - open-mpi - pkgconf ## Build dependencies - cmake ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.1.1 - Local data: ok - Upstream repository: https://github.com/HDFGroup/hdf5 - info: No package-manager update timestamp was available. - info: No cached GitHub release or tag data was available. ## Project history and usage hdf5-mpi is the MPI-enabled packaging role for the HDF5 library and tools. It shares HDF5's project history, but it matters to users who need Parallel HDF5 builds linked with MPI and MPI-IO support rather than only serial HDF5 libraries. ### Project history HDF began at NCSA in 1987 as an architecture-independent scientific data library and file format. By 1996, HDF's maintainers considered the older line insufficient for larger data volumes and newer computing systems, and in 1998 HDF5 was implemented as the more scalable successor to HDF4. Parallel HDF5 was designed around compatibility with serial HDF5 files, a single shared file image across processes, and a portable standard parallel I/O interface. The HDF Group documentation says the initial target was MPI programming rather than shared-memory programming, matching the MPI-enabled package role. ### Adoption history The MPI-enabled package exists because HPC users often need the same HDF5 data model but with collective access from multiple processes. Upstream installation guidance for Parallel HDF5 calls out MPI compilers with MPI-IO support and POSIX-compliant parallel file systems, which maps directly to cluster module and package-manager variants. For Homebrew and Nix users, hdf5-mpi separates the parallel build from the default serial package so dependent software can link against the expected ABI and compiler wrappers. The package role is about build configuration and dependency selection, not a separate upstream project. ### How it is used Parallel HDF5 is used by MPI applications that need many processes to create, open, read, write, and close HDF5 files while preserving serial-file compatibility. Upstream CMake guidance enables this path with HDF5_ENABLE_PARALLEL=ON and MPI compilers such as mpicc or mpif90. The package exposes MPI-aware compiler wrappers and tools recorded in the batch input, including h5pcc, h5pfc, h5perf, and ph5diff. Those names signal to build systems and users that this package is for parallel HDF5 development and testing. ### Why package nerds care hdf5-mpi is a classic package-manager split: same upstream, different feature matrix. It matters because mixing serial HDF5, MPI HDF5, C, Fortran, C++, thread-safety, filters, and compiler wrappers can break downstream builds in subtle ways. Package users care about this variant when building scientific Python, Julia, Fortran, C, and C++ software against cluster MPI stacks. The package is less about command-line novelty and more about getting the right library compiled with the right parallel I/O assumptions. ### Timeline - 1987: NCSA began work on the original architecture-independent HDF technology. - 1998: HDF5 was implemented as a more scalable successor to HDF4. - 1998: Parallel HDF5 design work targeted MPI programming and portable parallel I/O. - 2006: The HDF Group began operating as a separate nonprofit steward. - 2020: The official HDF5 source repository was created on GitHub. - 2026: Batch input records Homebrew and Nix packaging for the MPI-enabled package variant. ### Related projects - HDF5 is the upstream library and file format project. - MPI and MPI-IO provide the parallel programming and I/O substrate for Parallel HDF5. - h5py and HDF5.jl are examples of higher-level ecosystems that distinguish serial and MPI-enabled HDF5 builds. - netCDF is a neighboring scientific-data ecosystem commonly tested with HDF5 by upstream integration workflows. ### Sources - - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** hdf5-mpi - **Version Scheme:** 1 - **Revision:** 0 - **Conflicts With:** hdf5 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Nix - hdf5-mpi: normalized package name match | nixpkgs package indexes: hdf5-mpi from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [Database and data packages](https://www.automicvault.com/pkg/database-data-tools/) - Matched database, SQL, migration, or data-store metadata. - [gcc](https://www.automicvault.com/pkg/brew/gcc/) - Runtime dependency declared by Homebrew. - [open-mpi](https://www.automicvault.com/pkg/brew/open-mpi/) - Runtime dependency declared by Homebrew. - [pkgconf](https://www.automicvault.com/pkg/brew/pkgconf/) - Runtime dependency declared by Homebrew. - [cmake](https://www.automicvault.com/pkg/brew/cmake/) - Build dependency declared by Homebrew. - [damask-grid](https://www.automicvault.com/pkg/brew/damask-grid/) - Popular package that depends on this formula. - [hdf5](https://www.automicvault.com/pkg/brew/hdf5/) - Shares the same upstream source repository. - [cgns](https://www.automicvault.com/pkg/brew/cgns/) - Shares av.db curated category or tags: cli, data, hdf5, scientific-data. - [libgetdata](https://www.automicvault.com/pkg/brew/libgetdata/) - Shares av.db curated category or tags: cli, data, scientific-data. - [netcdf](https://www.automicvault.com/pkg/brew/netcdf/) - Shares av.db curated category or tags: cli, data, scientific-data. - [netcdf-cxx](https://www.automicvault.com/pkg/brew/netcdf-cxx/) - Shares av.db curated category or tags: cli, data, scientific-data. - [netcdf-fortran](https://www.automicvault.com/pkg/brew/netcdf-fortran/) - Shares av.db curated category or tags: cli, data, scientific-data. - [adios2](https://www.automicvault.com/pkg/brew/adios2/) - Shares av.db curated category or tags: cli, data, scientific-data. - [datalad](https://www.automicvault.com/pkg/brew/datalad/) - Shares av.db curated category or tags: cli, data, scientific-data. ## Combined YAML source View the package source record on GitHub. [combined/hdf5-mpi.yml](https://github.com/automic-vault/db/blob/main/combined/hdf5-mpi.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph