zoomy-prepost
Shared pre/postprocessing conversions for Zoomy — the general place for format conversion so backends don't each ship custom writers.
Today it converts VTK / ParaView .pvd → zoomy HDF5 (the format
zoomy_plotting.read_hdf5 and the GUI read), so any backend that emits VTK
(firedrake .pvd, foam / dmplex .vtu/.vtk) does one call and the normal
postprocessing just works.
from zoomy_prepost import vtk_to_hdf5
vtk_to_hdf5("simulation.pvd", "simulation.h5") # .pvd collection, .vtu, or [frames]
zoomy-convert simulation.pvd simulation.h5
Output layout (zoomy_core.misc.io convention):
/mesh/{dimension, type, n_cells, n_inner_cells,
vertex_coordinates:(dim,n_vert), cell_vertices:(k,n_cells)}
/fields/iteration_i/{time, Q:(n_vars,n_cells)}
Install it only in the containers that need it (firedrake, foam, dmplex). Mesh conversion helpers can grow here too.
1 maintainer
Metadata
1 maintainer
Release files for zoomy-prepost 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zoomy_prepost-0.1.0.tar.gz | 32.4 kB | With provenance | Details for zoomy_prepost-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zoomy_prepost-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for zoomy_prepost-0.1.0-py3-none-any.whl |
Total release size: 62.9 kB
Release files / zoomy_prepost-0.1.0.tar.gz
| Download URL | zoomy_prepost-0.1.0.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7b174883eb72bc02106e2b9639c59b377ec00558491137d413032c7dbd1a3cc
|
|
BLAKE2b-256 checksum How to use checksums |
6fa1f4aaf81f0bbe0023b42af773e8d89dab19c4a1f57a6df0d0993e66d94238
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / zoomy_prepost-0.1.0-py3-none-any.whl
| Download URL | zoomy_prepost-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efe817d82d017ea6b684e9d4dee74bac58e5ad0ce0c1a067ea2e41564185f665
|
|
BLAKE2b-256 checksum How to use checksums |
5ac35fefc7a6791dcda995d25c5baac412620504b8bb0deea466d423004567af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for zoomy-prepost 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zoomy_prepost-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.
