Skip to main content
Change of provenance

The repository or configuration that created this release differ from a previous release. View details.

Hertzforge

Hertzforge will be one toolset for structural dynamics testing, from acquiring the data to analyzing it. It is being built by merging two existing projects: Kevin Cross's data acquisition software, and Visual Dynamics, Brandon Zwink's structural dynamics toolset (https://visualdynamics.org).

Visual Dynamics' analysis core is in this repository now, under src/hertzforge/. The hertzforge package on PyPI at 0.0.1 predates it and installs only a command that prints its version; 0.1.0 is the release that carries the core, and the desktop app of the same number is on hertzforge.com.

pip install hertzforge
hertzforge --version

The First Vertical Slice

The rest of this repository is the first slice through every layer of the merged toolset, built as the foundation rather than a demo. Its code still carries the working name sds; renaming it into the hertzforge package layout is a mechanical change that comes next.

Path Language Owns
src/hertzforge/ Python The hertzforge package: the analysis core from Visual Dynamics, its readers and writers, reports, and the hertzforge command
src/hertzforge/service/ Python The analysis service: the core behind the protocol, started by hertzforge serve
schema/ JSON The protocol (PROTOCOL.md, protocol.schema.json) and golden frames every codec is tested against
crates/sds-control/ Rust The control service. Runs closed-loop Random on the simulator or on NI-DAQmx hardware, on loopback
crates/hertzforge-*/, modules/, abi/ Rust, C header The controller: control laws, the hardware abstraction with its Sim and NI backends, data formats, and the module ABI
ui/ TypeScript, Svelte 5 The shell: workspaces, command palette, the viz kit, and panels built from operation descriptors
desktop/ Rust The desktop app: the shell in a window of its own, with both services and a bundled Python
tools/demo-video/ JavaScript A scripted walkthrough of the shell, recorded to video
tools/e2e-sim/ JavaScript Closed-loop Random on the simulator, end to end through the real control service and the shell
scripts/ shell Developer entry points
site/ HTML The hertzforge.com page, deployed by .github/workflows/site.yml when it changes on main

The control service and the controller crates are one Cargo workspace (cargo test --workspace). The NI backend loads the NI-DAQmx driver at run time, so building and testing need no NI software installed.

Layer Rules

  • Rust owns anything the real-time loop or the simulator executes, the hardware backends, and kernels shared by control and analysis.
  • Python owns everything offline: analysis, modal fitting, FEM, specification tools, reports, and the scripting API.
  • TypeScript owns every pixel and no numerics. A view asks a service for a result and draws it.
  • Spectra are plotted the way they are calculated: a density per line is drawn flat across its bin, one df wide, as Visual Dynamics draws it. The service that computed the data says how it is drawn.
  • The control loop and abort path never depend on the GUI, the network, or Python.
  • A simulated run is always marked source: "SIM" and is never presented as a hardware result.
  • No employer, client, laboratory or partner names anywhere in the tree.
  • Dependencies are permissively licensed (MIT, BSD, Apache-2.0, ISC, Zlib; OFL-1.1 for bundled fonts; MPL-2.0 reviewed case by case). No copyleft packages. The one exception is Intel's oneMKL, which the sparse modal solve factors with on x86-64 Windows and Linux (THIRD_PARTY_NOTICES.md).
  • The app makes no network requests beyond its own services: fonts and assets are bundled, because test labs run on closed networks.

Run

pip install -e .
scripts/fetch_testdata.sh
scripts/dev.sh

The first line installs the package with the analysis service into the active environment, the second fetches the plate test data the tests read (and scripts/make_examples.py turns into the example projects on hertzforge.com). scripts/dev.sh then starts the analysis service on 8791, the control service on 8792 and the shell on http://127.0.0.1:5191/. ?mock=1 runs the shell alone, its control side on synthetic data.

The desktop app (desktop/) carries the shell, both services and its own Python, so it needs nothing else installed. desktop/packaging/build.sh builds it and its installers; docs/desktop-app.md says what they contain and how the app stops a run when it quits.

The end-to-end check drives Random on the simulator through the real control service, in the installed Chrome. It starts both services itself on free ports, takes about three minutes, and is not part of npm --prefix ui test:

npm --prefix tools/e2e-sim ci
node tools/e2e-sim/random_sim.mjs --shots <folder for screenshots>

License

Hertzforge is released under the MIT License (LICENSE). The source is at https://github.com/hertzforge/hertzforge.

Metadata

Release files for hertzforge 0.1.1

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

Change of provenance

The repository or configuration that created these release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Source distribution (sdist)

Source distribution for hertzforge 0.1.1
File Size Uploaded Provenance Actions
hertzforge-0.1.1.tar.gz 3.1 MB With provenance Details for hertzforge-0.1.1.tar.gz

Built distribution (wheel)

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

Total release size: 5.2 MB

Release files / hertzforge-0.1.1.tar.gz

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL hertzforge-0.1.1.tar.gz
Size 3.1 MB
Tags Source
SHA-256 checksum
How to use checksums
f247a9cdd6b711988d1277b166d80dc652e2446eaf7ea1023f64e95d792e33bf
BLAKE2b-256 checksum
How to use checksums
3266a3be0865bb2f893cf378ac42c8920105d9e2bc5a90c81d5e01eace27c986
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 Nov 10, 2026.

Transparency log

Release files / hertzforge-0.1.1-py3-none-any.whl

Change of provenance

This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.

We recommend inspecting the repository and configuration before proceeding. View details.

Download URL hertzforge-0.1.1-py3-none-any.whl
Size 2.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
f2b3b0aad59ac289cb1e3e825969af309971d53d331a772e9ebb8e3d3d674976
BLAKE2b-256 checksum
How to use checksums
1093dde6ae9d7f38bdb3ec1db06762ab4bc67022aee0c93de15343fc8900f24e
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 Nov 10, 2026.

Transparency log

Security for hertzforge 0.1.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.

Change of provenance

The repository and configuration that created this release differ from a previous release.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Select from 2 files

Attestation for hertzforge-0.1.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 Nov 10, 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