Skip to main content

hpckit banner

CI PyPI Python License

hpckit is a small Python CLI for orchestrating Slurm cluster workflows from a local project checkout. It manages remote tool checkouts, immutable per-SHA virtualenvs, run packets, Slurm submission and polling, receipts, artifact sync, and local run ledgers.

The tools it runs are declared in your own .hpckit.yaml — hpckit ships none of them, and depends on nothing but a YAML parser itself.

Its companion renderer is quadros, which turns simulation field snapshots into frames and video. Add it with the renderer extra if you want to render as well as submit:

pip install hpckit              # submit jobs only
pip install 'hpckit[renderer]'  # ...and render locally

It stays optional on purpose: quadros brings VTK, roughly 700 MB, and a machine that only submits jobs should not pay that.

Configuration lives in the project you run it from, not in this repository, so one installation drives any number of projects.

Install

For local development:

uv pip install -e .

For command-line use from another checkout:

pipx install git+https://github.com/openfluids/hpckit.git

Quickstart

cd /path/to/your/project
hpckit init --project myproject
hpckit doctor

Configure

Create .hpckit.yaml in the project where you run hpckit (see .hpckit.example.yaml for a full template). Tools, job types, and the sparse batch script name are all config-driven:

project: myproject
remote: mycluster
work_root: /path/to/work
scratch_root: /path/to/scratch
remote_repos_root: /path/to/work/repos
remote_state_root: /path/to/work/.hpckit
ledger: HPCKIT_RUN_LOG.md
job_script: job.batch
restart_helper: check_restart.py
prologue: |                      # optional — site environment setup
  module load myenv
  export OMP_NUM_THREADS=1
slurm:
  account: myproj@cpu   # required — no default
  partition: prepost
  ntasks: 1
  cpus_per_task: 4
tools:
  sigtool:
    repo_url: git@github.com:myorg/sigtool.git
job_types:
  process:
    tool: sigtool
    command: "{venv}/bin/python -m sigtool.cli process --registry {run_dir}/registry.toml --output-root {output_dir}"
artifact_sync:
  processed: data/hpckit_processed
  renders: plots/hpckit_renders
  paper_figs: paper/figs
  receipts: hpckit/receipts

Commands

hpckit doctor
hpckit status
hpckit update-repo <tool> --ref <sha-or-branch>
hpckit submit <job_type> <case> --ref <sha>
hpckit submit sparse <case> --to <target_end_time>
hpckit poll [run_id]
hpckit sync-artifacts <run_id>
hpckit receipt <run_id>
python -m hpckit doctor

Job type subcommands (e.g. process, render, plot) come from job_types: in the config. Sparse is built-in and uses job_script / restart_helper.

Site environment setup

sbatch starts a non-login shell, so anything your login profile would normally provide — module load, an MPI or compiler environment — is absent inside the job unless you set it up there. That failure is a quiet one: the command still runs, it just cannot find the tools it expected, and you get a result that looks like a real one.

prologue: is shell run inside the generated job.sbatch, after set -euo pipefail and before the job type's command. It goes there rather than inside each command: because command templates are expanded with str.format_map, so a shell ${VAR} would raise unknown placeholder '{VAR}'; because every job type would otherwise repeat it; and because it varies with the machine, not with the job. Omit it and the generated script is what it was before.

Some environment scripts reference unbound variables and trip set -u. Fence those rather than dropping the option for the whole job:

prologue: |
  set +u
  . /opt/intel/oneapi/setvars.sh --force >/dev/null 2>&1
  set -u
  export OMP_NUM_THREADS=1

Development

uv sync --group dev
uv run pytest
uv run python -m build

The repository uses the PyPA-recommended src/ layout, standard pyproject.toml metadata, a public [project.scripts] entry point, and dependency groups for maintainer tooling.

Destructive remote cleanup is intentionally not implemented. Sparse continuation edits only the case-local restart helper knobs and records the backup name in the receipt.

Metadata

Release files for hpckit 0.2.1

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

Source distribution (sdist)

Source distribution for hpckit 0.2.1
File Size Uploaded Provenance Actions
hpckit-0.2.1.tar.gz 314.4 kB With provenance Details for hpckit-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hpckit 0.2.1
File Interpreter ABI Platform Actions
hpckit-0.2.1-py3-none-any.whl Python 3 none any Details for hpckit-0.2.1-py3-none-any.whl

Total release size: 332.9 kB

Release files / hpckit-0.2.1.tar.gz

Download URL hpckit-0.2.1.tar.gz
Size 314.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2844b40963cd081f3bea39bf368dfedd382ea1cb5b221dd933baea0951ba55f2
BLAKE2b-256 checksum
How to use checksums
66c5c5bf6eef31a875d7dff87d23e361c9a7387c106f954052615d9a835e20d5
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 Aug 5, 2026.

Transparency log

Release files / hpckit-0.2.1-py3-none-any.whl

Download URL hpckit-0.2.1-py3-none-any.whl
Size 18.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
471af9ea2dfe3258b97f361c07e20f0d32ccb199d4e1691cfb6ca718f773e7a9
BLAKE2b-256 checksum
How to use checksums
bc5450af7e0feed9c265675880a12d014e42c797f40c262abbf7b2e7f1a8e868
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 Aug 5, 2026.

Transparency log

Security for hpckit 0.2.1

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.

Select from 2 files

Attestation for hpckit-0.2.1.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 Aug 5, 2026.

Transparency log

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