dsh-cst-tools

LIMITATIONS

Known limitations

* **Windows only.** The launcher and the CST Python API integration are Windows-based. * **You must own CST.** CST Studio Suite is not part of this project; CST_AI is a client of an installation you license separately. * **One live Design Environment at a time.** CST_AI attaches to a single live DE and reports ambiguity instead of picking one arbitrarily. * **Existing results are required for the read-only capabilities.** `FARFIELD_*`, `DIRECTIVITY`, `GAIN`, `REALIZED_GAIN`, `BEAM_DIRECTION` and `HPBW` activate a *stored* farfield result; they never re-solve to obtain one. * **Farfield readback depends on result activation.** The angular data is read through the documented farfield evaluation-list chain after selecting the stored tree item. The CST-native `GetMainLobeDirection` / `GetAngularWidthXdB` getters are documented for `.Plottype "Polar"` only and raise on the results this plugin reads, so beam direction is taken from the read grid and HPBW is computed from it. * **No optimisation.** `PARAMETER_SWEEP` evaluates the points you list; it does not adapt parameters, search a space or claim a "best" point. * **No natural-language input.** You write the TaskSpec. (See the roadmap.) * **Fixtures are yours.** CST project geometry is not redistributable, so this repository ships the *shape* of a fixture definition, not ready-made CST models. * **Repeatability is bounded by physics and by the solver.** A numerically identical re-read of a stored result is exact; a new solve is as reproducible as CST itself.