annotate-control-panel

Annotate Control Panel

This skill writes the Wolfram control-panel (Explore) annotation into a Modelica .mo file so a model carries its own interactive panels — the sliders, checkboxes, input fields and popup menus that Simulation Center's Explore view shows for driving parameters and start values, plus the plots to display:

annotation(__Wolfram(ControlPanels(
  Panel(
    identifier = "id1",
    title = "Controller tuning",
    elements = {
      Slider(variable = Kp, label = "Proportional gain", min = 0, max = 100),
      Slider(variable = Kd, min = 0, max = 20, scale = Log()),
      Checkbox(variable = useFeedforward, label = "Feedforward")},
    figures = {"response"})));

It is a self-contained source transform: Claude assembles a control-panel spec (JSON) — from the user's request, or suggested from the model's parameters — and the Python engine renders it to the __Wolfram(ControlPanels(...)) vendor annotation and splices it into the class annotation. The engine is pure Python (standard library only); WSMKernelX is used only afterwards as a validation gate.

This is a vendor-specific annotation (Modelica spec §18.1): other tools ignore it and preserve it on save, and it does not affect flattening — it just tells System Modeler how to build the Explore panels. It sits directly inside annotation(...), as a sibling of experiment and Documentation (never nested inside Documentation).

It is idempotent: a class that already has control panels is skipped unless you pass --force (which strips the old ControlPanels block and regenerates). By default it prints a dry-run diff; nothing is written until --write.

--force is destructive — ask the user first. It deletes the class's existing control panels before regenerating, so any hand-tuned panels there are lost. Don't pass --force on a class that already carries control panels without confirming that discarding them is intended. Review the dry-run diff (no --write) to see exactly what would be removed.