Add a simulation object (SimWorks add* only; configure with set_property).

After success, the reply includes Name='...'. Record that exact name for later select / set / delete. Do not call add again for an object that already exists (especially port_group, mode_port, fdtd) — if select fails, use object_action path forms instead of re-adding. Docs: https://simworks.net/knowledge-base/Script-Commands_setting-objects

Manipulate selection and objects in the project tree (SI meters for vertices).

Select cheat-sheet (SimWorks select / selectpartial / shiftselect*):

• Structures at root: select('Ring').

• Under FDTD: select('FDTD::MonitorName').

• Mode ports: select('FDTD::Ports::Port_input') — include solver + port group + port. Omitting FDTD:: is the usual reason select fails.

• Discover group: select_partial('::Ports') or select_partial('FDTD::Port').

• Multi-select: shift_select / shift_select_partial add without clearing (same group only); then set_property applies to all selected.

• If select fails: retry with FDTD::<Group>::<Child>; never re-add or disable.

Switch the CAD camera or view plane.

Switch between run and design layout modes.

Workflow: run simulation → (extract results) → switch_layout('design') before further edits → switch_layout('run') only when you need the run/results UI again. Never assume set_property works while still in run layout after a solve.

Run solvers, sweeps, or analysis scripts.

Confirm with the user before action=run / run_sweep / eme_sweep. If the call blocks until done and the MCP request times out, the solver may still be running in SimWorks — do not issue a second start to "retry" a timeout.

Open, save, or create a simulation project. Prefer absolute paths.

Set one property on the currently selected object(s).

Prefer calling directly when you know the exact SimWorks property name. Numbers are SI only. On failure, get_info(kind="property"), then retry only the failed property — do not invent names from similar software. If you set name, remember the new name for later object_action select (use Parent::Child when nested).

After a simulation finishes, many properties can only be set in design layout. If set fails with a design-layout / inactive message, call switch_layout(layout="design") (confirm first if results would be lost), then retry — do not re-add objects to work around this.

Add the selected object to a group, or remove it from its current group.

Configure a setup, parameter, or result variable on the selected group.

Assign a user-defined time-domain signal to an existing source (setsourcesignal).

Used in FDTD / FDFD for custom pulses (modulated Gaussian, multi-peak, etc.). This is not set_property — ordinary wavelength / pulse settings still use set_property on the selected source.

t, amplitude, and phase must be equal-length 1D vectors (SI: s, —, rad). Prefer starting t at 0 so the initial field is zero.

Set one parameter on the EME Analysis Window (setemeanalysis).

Use this before run_action(eme_sweep) / eme_propagate when you need to configure sweep type, wavelength range, cell group span, tolerances, energy conservation, etc.

This is not set_property: it does not touch the selected object and get_info(kind="property") will not list these names. Read back with get_info(kind="eme_analysis"). After a sweep, fetch results with get_results(kind="eme_sweep").

Discover properties and metadata. Prefer this before inventing property names for set.

kind=eme_analysis calls getemeanalysis(name) for the EME Analysis Window (not object get). Pair with set_eme_analysis; sweep results use get_results(kind="eme_sweep").

Extract simulation results. For kind=data, call with no dataset/data first (LIST MODE) to discover available names, then call again with object_name + dataset_name [+ data_name].

kind=eme_sweep: getemesweep(dataset_name) after run_action(eme_sweep). Configure the analysis window with set_eme_analysis / get_info(eme_analysis).

List, add, set, or query materials. Do not invent material names — list first if unsure.

Manage the simulation job queue.

Clear workspace variables or the script console.

Load a script file, data files, or import NK / raw arrays into the workspace.

• kind="script": SimWorks load('file_path') — loads and runs a script (e.g. .msf). Prefer an absolute path.

• To open a project (.sim / .mpps etc.), use project_action(action="open").

• Other kinds load data into the workspace (mdf/mat/h5/…), not scripts.

Save workspace variables to a file. Use project_action(save) to save the .sim project.

Low-level file open/close/write helpers.

Query parameters or attributes on a dataset object (not fd_instance).