Vis Automations · In-app tool, Automation Scripts menu
Model Inspector
A Python tool that Vis lists in its own Automation Scripts menu: it attaches to the open session, reads every part, selects the largest, retitles the view, adds a snapshot and writes a report.
Verification NOT fully passing on Vis 2606.0 build 26134 + 2606.2610 · 2026-10-29 · repo tc-vis-automation 9f1b0af · The tool, the menu launch and restart persistence work; registration by registry does not.
Two kinds of run on the engine example. First the script launched through its .py file association against a Vis started by hand, which is exactly what the menu’s ShellExecute does. Then the real menu: the script added once through Manage Scripts and clicked from ☰ Menu › Automation Scripts. Every result is read back from Vis or the operating system: the process id, the selected-node count, the window title, the snapshot count, the capture’s pixels.
- Vis
- 2606.0 build 26134 + 2606.2610
- Run
- 2026-10-29 · EXERCISED
- Checks
- 7 of 8 hold
- Overall
- Not fully passing
- Source
- tc-vis-automation README.md (In-app tool: Claude Model Inspector, follow-up and correction) at commit 9f1b0af
| Result | Check |
|---|---|
| Holds | Runs in the existing session, no second VisVisView_NG pid 52612 before and after a launch through the .py file association (what ShellExecute does). |
| Holds | Reads every part and selects the largest67 parts read; largest Case_r:123-200 selected; 1 selected node read back; drawn in the selection highlight in the capture. |
| Holds | Retitles the viewThe OS window title of pid 52612 changed to "Claude Model Inspector: largest = Case_r...". |
| Holds | Adds a snapshot, state persists in the sessionSnapshot count 0 to 1 on the first run and 1 to 2 on the second. |
| Holds | Added through Manage Scripts and launched from the menuRun log run_20261029_185527.json: argv is the bare script path (Vis's ShellExecute), VisView_NG pid 60964 before and after, 67 parts, largest selected, title changed, snapshots 0 to 1, capture 0.11 geometry, report opened. A person clicked the menu entry in the Vis window. |
| Holds | Vis's own profile matches this repo's XML formatByte-for-byte apart from the name Vis picked. |
| Fails | Registry registration (Register-VisInspector.ps1)With the profile and both FileLocation keys written and Vis restarted, the submenu lists only Manage Scripts... (HKCU, both roots tried). |
| Holds | Menu entry survives a Vis restartCorrected 2026-10-29: after a restart the Manage Scripts dialog opened already holding model_inspector.py. Where Vis stores the profile location is still not found (no file, no HKCU Siemens value in any encoding). |