Skip to content

Hertzon v0.2.10

Choose a tag to compare

@github-actions github-actions released this 01 Nov 20:26
0ed77bd

Highlights

  • Tune with sliders, live: compute the derivatives once, then move design variables with sliders and every
    open report (S-parameters, Smith chart, radiation pattern, antenna parameters) follows in real time. It works
    with Hertzon's own mesh deformation instead of remeshing, which suits optimization very well; more built on it is coming.
    (Introduced in 0.2.9.)
  • New optimizer, Derivative Trust Region: minimizes the goals on the derivative tuning model and checks each
    step with one solve. The patch antenna wizard (Tools > Antenna Design > Rectangular Patch) starts from the
    textbook design formulas and is optimized after only 2-3 simulations.
  • Solving in the cloud: Hertzon starts a cloud server, solves there and deletes it again. Tested with Hetzner
    Cloud; Amazon Web Services, Google Cloud and Microsoft Azure are implemented but untested, feedback welcome.
    Large servers and HPC clusters for studies are in progress.
  • Apply to Design keeps the solution, and Solution Data lists every variation and optimization evaluation.
  • Wave ports with several modes and eigenmode setups fixed.

Added

  • Showcase project brought up to date: Derivative Trust Region optimizations (goals on S-parameters, antenna parameters and output variables), output variables with S, Y, Z and VSWR, reports against a design variable, report axis settings, bandwidth and delta markers, SPARTA matrix solvers, ports-only setups, Edit Sources, Rotate / Sweep Around Axis in a coordinate system, and two new designs: a terminal differential pair (reference conductor, mixed-mode S-parameters) and a waveguide with two-mode wave ports (TE10 and TE01). The iris filter's first port has one mode again (the half model has no second mode, the solve failed) and the geometry zoo solves again (loft to an ellipse, a gap around the kept Subtract tool).
  • Tools > Antenna Design > Rectangular Patch optimizes patch length and inset at the design frequency
    only, on the adaptive solution (no sweep is solved per evaluation), with the Derivative Trust Region
    instead of Conjugate Gradient (named PatchOpt). The dialog no longer asks for a bandwidth, a return loss
    over the band and the sweep span: they only served the band goal; the ±15 % sweep stays for looking at
    the resonance.
  • Solver image for cloud computers: ghcr.io/c8501024/hertzon-solver (:<version>, :dev) holds the
    headless solver with the remote service and precompiled kernels; a Linux computer with Docker solves for
    the GUI without a Hertzon installation (docker run ... -e HERTZON_TOKEN=..., see docs/REMOTE.md). Built
    by .github/workflows/solver-image.yml.
  • Solving in the cloud (Hetzner Cloud): Tools > Options > Cloud with the project's API token; the first
    analysis creates a server (location and type with prices from the account), further ones use it, Hertzon
    deletes it when it closes and the server deletes itself when idle, hung or without a GUI (watchdog). The
    connection is an SSH tunnel with a host key known in advance. Solve on offers the cloud next to this
    computer and a remote computer. See docs/REMOTE.md.
  • Amazon Web Services, Google Cloud and Microsoft Azure are marked (untested): only Hetzner Cloud has
    been tried with a real account; the Cloud tab warns to use the others at your own risk.
  • Solving in the cloud on Amazon Web Services: Tools > Options > Cloud > Provider Amazon Web Services
    with the access key of an IAM user (policy in docs/REMOTE.md), region and instance type with vCPUs,
    physical cores, memory and on-demand price. Hertzon starts an Ubuntu instance in the default VPC that
    installs Docker and the solver image; the access key stays on this computer, the instance deletes itself
    by shutting down (terminate on shutdown). A sold-out zone is retried in the other zones of the region; the
    vCPU limit of new accounts gets a clear message.
  • Solving in the cloud on Google Cloud: Provider Google Cloud with the JSON key of a service account
    (roles in docs/REMOTE.md), or, where the organisation forbids service account keys, with the gcloud login
    (gcloud auth application-default login; Hertzon finds its file and asks for the project ID); zone and machine type with vCPUs, cores and memory. Hertzon signs in with the key
    itself (no extra package), starts an Ubuntu instance that installs Docker and the solver image, reads its SSH
    host key through the API and tries the other zones of the region when a zone is full. The key (or the gcloud
    login) stays on this computer; the instance deletes itself with its own service account.
  • Solving in the cloud on Microsoft Azure: Provider Microsoft Azure with a service principal (the JSON of
    az ad sp create-for-rbac, Contributor on the resource group hertzon) and the subscription ID; region and
    size with vCPUs, cores, memory and the pay-as-you-go price in EUR. Hertzon creates the network once per
    region and per server an address, a network card and an Ubuntu machine that installs Docker and the solver
    image; deleting the machine deletes the rest. The server deletes itself with the service principal.
  • S Parameter menu on the Equation page (Fields Calculator, new Network group): lists S(i, j) for every
    port pair, with Y, Z and VSWR in submenus, from the solved data or the design's ports; a click inserts the
    term into the equation.
  • Optimizer "Derivative Trust Region": every round solves the design, computes its derivative tuning
    model and minimizes the goals on the model (milliseconds per evaluation) within a part of the tuning
    range; the step is checked with a solve, and the region grows or shrinks with the agreement. On the patch
    antenna (Lp, inset) from Lp = 31 mm, inset = 4 mm (dip at 2.275 GHz) to S11 ≤ −15 dB from 2.43 to 2.47 GHz:
    six solves and five tuning models, dip at 2.45 GHz with −34.9 dB. At most 6 variables. A tuning model that
    fails (for example out of memory) ends the run with the best design so far. See
    docs/TUNING.md.

Fixed

  • Wave ports with several modes (modal solution) absorb every mode with its own propagation constant, as terminal ports already did. Before, all modes used the first mode's constant: in an empty 22.86 x 15 mm guide at 12 GHz, TE01 was reflected with |S22| = 0.34. Gamma and Zo of every mode row are now the mode's own (they showed the first mode's for all rows), which also corrects their de-embedding.
  • Eigenmode setups solve again: the mesh is sized at the minimum frequency (the solve stopped with 'Frequency'), and the eigen search climbs from the minimum frequency until the wanted number of modes is found. A search below the first resonance returned only the static null space, so no modes were listed.
  • A wave port with more modes than its face carries (for example two TE modes on a WR-90 port at 10 GHz) now stops with a message naming the port and the number of modes it has, instead of a division by zero in the S-parameters.
  • Optimization > Apply to Design takes the solution of the applied evaluation over as the solution of
    the setup, without solving again: reports, Solution Data, field overlays and Derivative Tuning (on the
    evaluation's adaptive mesh) work on it as after an analysis. The best evaluation keeps its mesh and the
    fields at the adaptive frequency; the other evaluations keep S-parameters, passes and log. Before, the
    design had to be analyzed again.
  • Results > Solution Data has a Design Variation list: next to the current design it shows every
    solved parametric variation and every optimization evaluation, with its passes (Convergence), Matrix
    Data, Profile and Mesh Statistics, without changing the design. While an optimization runs and the design
    has no solution of its own, it shows the evaluation being solved and follows its passes.
  • Tools > Options opens at once. It used to wait for the check whether this computer's remote service
    runs (on Windows a refused connection to this computer alone takes about two seconds), for the host name
    lookup of the share addresses and for the scan of the installed SPARTA version. These now run in the
    background; their fields show "Checking ..." for a moment and the buttons that depend on them wait.
  • A parallel frequency sweep with the matrix solver set to PARDISO warned for every frequency that
    the solver "cannot be used in MultiThreading as it does not release the GIL". The worker threads use
    PARDISO through the automatic choice anyway; the warning is gone and the results are unchanged.

Windows installer (Hertzon-Setup-*.exe) and Linux package (Hertzon-*-linux.tar.gz).

Hertzon is built on EMerge, the open-source FEM solver by
Robert Fennis, which provides the finite-element core.