zrwangems/dsh-zrwang-plugin / skills/engineering/matlab/ai-and-statistics/matlab-use-experiment-manager
matlab-use-experiment-manager
UnverifiedCreate, modify, or delete experiments in Experiment Manager with live UI sync. TRIGGER when: user asks to create an experiment from code/script, wants to sweep parameters, asks to add/delete/edit experiments, or wants parameter changes reflected in the UI. Combines experiment creation (from code analysis) with frontend UI synchronization.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.0 KB |
| manifest.yaml | config | 521 B |
| references/common.md | markdown | 22.6 KB |
| references/create.md | markdown | 15.4 KB |
| references/delete.md | markdown | 2.3 KB |
| references/duplicate.md | markdown | 2.6 KB |
| references/load-project.md | markdown | 700 B |
| references/rename.md | markdown | 2.6 KB |
| references/update.md | markdown | 14.4 KB |
| scripts/+experiments/+internal/AgentFrontendBridge.p | binary | 963 B |
| scripts/+experiments/+internal/AppController.p | binary | 299 B |
| scripts/manageExperimentHelpers.p | binary | 2.9 KB |
references/rename.md
View on GitHub# Operation: Rename Experiment
> Shared rules, setup, the Modification Flow, validation, and API are in
> [common.md](common.md). Read it first.
Update an experiment's name, tree label, and tab title. **The experiment's function file is
left untouched.**
**Before renaming:** The new name must not be empty (after trimming whitespace) — reject an
empty or all-whitespace name and ask the user for a real name before doing anything. Then check
the target name doesn't already exist as a .mat file.
No confirmation needed.
**Rename the experiment only — do NOT rename the function file.** The experiment references its
function by name (`Process.FunctionSection`), and that reference is unaffected by the
experiment's name, so the function keeps working. Renaming the function too would force it to
the experiment's new name (`<oldName>.m` -> `<newName>.m`), which is wrong: it clobbers a
deliberately-named or shared function and, for a `.mlx`, needs a file move for no benefit. Leave
the function file, its signature, and `Process.FunctionSection` exactly as they are.
```matlab
clear classes
oldMat = fullfile('<projectPath>', '<oldName>.mat');
% Rename the experiment AND rebind its tab in one call. renameExperiment moves
% <oldName>.mat -> <newName>.mat on disk, updates the stored Name (tree label + tab title),
% and rebinds the OPEN tab to the new path in place — no teardown. Do NOT rename the .mat
% yourself and do NOT tear the view down: deleting the old .mat out from under a tab bound to
% it by experiment ID leaves a stale path (the tab later drops), and a hard view teardown
% orphans the JS frontend (assertion flood).
result = experiments.internal.AppController.renameExperiment(oldMat, '<newName>'); disp(result);
result = experiments.internal.AppController.syncTree(); disp(result);
```
**If `renameExperiment` returns `status: 'error'` or `status: 'timeout'`** (no live frontend —
see the graceful-degradation rule in [common.md](common.md)), it did NOT rename the `.mat` on
disk. Fall back to renaming it yourself, then tell the user to reopen the tab:
```matlab
newMat = fullfile('<projectPath>', '<newName>.mat');
S = load(oldMat, 'Experiment'); S.Experiment.Name = '<newName>';
save(newMat, '-struct', 'S'); delete(oldMat);
try, prj = currentProject; addFile(prj, newMat); catch, end
```
**After renaming:** the old `.mat` path is invalid — use `<newName>.mat` for subsequent
operations. The function file keeps its original name; if a later step needs it, refer to it by
the name in `Process.FunctionSection`, not the experiment name.
----
Copyright 2026 The MathWorks, Inc.
----
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |