Skip to content

v0.1.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Sep 22:13
· 105 commits to main since this release
v0.1.2
150e819

BEAT Engine 0.1.2 adds explicit phasor conventions and faster CUDA assembly for exterior and coupled electroacoustic solves.

Changes since 0.1.0:

  • Supports both exp(-i omega t) and exp(+i omega t) throughout assembly, solve, and field evaluation, with capability negotiation and response diagnostics. Unlabelled requests retain negative time for compatibility. Positive-time ROCm worker requests remain blocked pending AMD hardware qualification.
  • Defaults exterior-only CUDA system solves to direct Burton-Miller assembly, sharing one pivoted LU factorization across excitation right-hand sides at each frequency. Set burton_miller_assembly to operator_matrices to use the previous path.
  • Defaults coupled CUDA solves without full diagnostics to combined A/C Burton-Miller assembly, cached sparse interface projection, and fused symmetry images. Full diagnostics retain the original operator path. CPU and ROCm retain their existing assembly paths.
  • Adds coupled assembly controls and effective-mode diagnostics while preserving the existing wire-protocol and result-schema versions.

The documented 200-frequency Multi_region_SAWMOD experiment on an RTX 2080 Ti reduced warmed wall time from approximately 100.2 seconds to 72.4 seconds with combined coupled assembly and sparse projection. This is a workload-specific result, not a general performance guarantee. See coupled CUDA qualification and controls.

The release workflow requires successful Python tests, lint, Julia CPU tests, the standalone CPU reference gate, and package builds on Windows, Linux, and macOS for the release commit. Accelerator qualification remains hardware-specific.

Install the attached wheel into the application's Python environment, then prepare the relevant Julia project with python -m beat_engine instantiate --backend cpu (or cuda/rocm). Julia and GPU drivers are installed separately. Boundary Lab must update its exact package-version check and wheel URL/SHA-256 together. Restart existing application workers after upgrading. No PyPI publication is configured.

Assets 4
Loading