flekspy: FLEKS Python toolkit
Python package for processing FLEKS (FLexible Exascale Kinetic Simulator) data.
Installation
python -m pip install flekspy
Usage
flekspy can load files generated from FLEKS.
import flekspy
ds = flekspy.load("sample_data/3*amrex")
Plotting is supported via Matplotlib and YT. For more detailed usage and contribution guide, please refer to the documentation.
PyVista meshes
Install the optional reader with python -m pip install 'flekspy[pyvista]'.
ASCII Tecplot .dat and VTK .vtk, .vtu, .vts, .vtr, .vti, .vtp,
and .vtm files return native PyVista objects:
import flekspy as fs
mesh = fs.load("simulation/snapshot.vtu")
print(mesh.array_names, mesh.bounds)
slice_mesh = mesh.slice(normal="z", origin=(0, 0, 0))
zones = fs.load("simulation/snapshot.dat")
print(zones.n_blocks, zones[0].array_names)
DAT files always return a pyvista.MultiBlock, preserving every zone. Their
variable names have bracketed units removed, and coordinate names such as
X AU become X for the Tecplot reader. The source file is unchanged. VTK
datasets retain their arrays, metadata, and multiblock hierarchy. No physical
unit conversion or required magnetic/velocity fields are imposed. The direct
reader fs.read_pyvista(path) is also available.
ParaView Plugin
flekspy provides a ParaView plugin for visualizing FLEKS data. To use the plugin, follow these steps:
-
Make sure the ParaView version is 5.13 or higher.
-
Install flekspy for pvpython.
- Go into the ParaView directory and create a virtual environment for Python
./bin/pvpython -m venv .venv
- Check the Python version of
pvpython
./bin/pvpython -c "import sys; print(sys.version)"
- Install flekspy in the directory right in the venv. You may need to adjust the target path if
pvpythondoes not detectflekspy. Assuming the Python version is 3.10.11, run
python3 -m pip install --only-binary=:all: --python-version 3.10.11 --target ./.venv/lib/python3.10/site-packages/ flekspy
- Launch ParaView with the virtual environment
./bin/paraview --venv .venv
- In Tools > Manage Plugins, load the
BATSRUSReaderplugin.
License
flekspy is licensed under the terms of the MIT license.
1 maintainer
Metadata
1 maintainer
Release files for flekspy 0.7.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| flekspy-0.7.6.tar.gz | 79.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flekspy-0.7.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 169.5 kB
Release files / flekspy-0.7.6.tar.gz
| Download URL | flekspy-0.7.6.tar.gz |
|---|---|
| Size | 79.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e54047b39d76224bf09c806786d58584ac048af7ee01fc113d868477b2498ad1
|
|
BLAKE2b-256 checksum How to use checksums |
2e9d8865e8b5cfbd08c10068f49c48e4278c875463a3b2be3d03aafa79a54027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 9, 2026.
Transparency logRelease files / flekspy-0.7.6-py3-none-any.whl
| Download URL | flekspy-0.7.6-py3-none-any.whl |
|---|---|
| Size | 89.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13b984e54a5073aaf599590cebb135b13a0d7eea2ff4fbe28f718314edfa551f
|
|
BLAKE2b-256 checksum How to use checksums |
3b8a1d4bf47ffd7f0037a2339800064c425d47b761d9641187597f035ead8838
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 9, 2026.
Transparency log
