القائمة
Compatibility note for previewing Radia interfaces after the PySide era. Inspect the generated Simulink library, masked application blocks, and tracked MATLAB-only sample objects.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Four-machine Radia release gate. Use when the user asks for release-qud, release_quad, release_qud, post-release deploy, GitHub Release publication, or the Definition Of Done for Radia releases. Coordinates PyPI and Simulink release candidates across LAB, 100号機, mdx, and hibino via tools/release_qud.py.
Publish Radia's Simulink application library after verifying its five application blocks and tracked MATLAB-only samples. Use simulink-app-health before deploy/release-qud; Cubit's toolbar remains a separate deployment surface.
Verify Radia's production Simulink application blocks for EM, PCB, Motor, Stream Function, and IH. Use after changing buildLibrary, applicationSFunction, runApplication, application.py, a DesignSpec/calc script, the application interface manifest, or the tracked Simulink library; also use when a block does not run or leaves incomplete artifacts.
Take inventory of the radia package's proprietary Python and pybind API surface, classify API families under the Reduce Proprietary API Surface policy, and produce a committed audit plus phased reduction plan. Use after public API changes, before deprecation work, or for periodic read-only surface audits.
Historical deploy notes. Current Radia deploy/release uses release-qud plus cubit-plugin-install; do not follow old .ccl/Cubit-2025.3 recipes except for archaeology.
Verify GMSH .geo + .msh files generated by Radia panels BEFORE opening in the GUI. Catches invalid options (Mesh.Volumes), duplicate element IDs, missing Merge targets, node count mismatches. Run AFTER any calc_*.py edit that touches GMSH export, BEFORE clicking Open GMSH.
| name | panel-preview |
| description | Compatibility note for previewing Radia interfaces after the PySide era. Inspect the generated Simulink library, masked application blocks, and tracked MATLAB-only sample objects. |
Build matlab/radia_simulink_library.slx in C:\temp, open the library, and
inspect the five masked application blocks. The production artifact is the
Simulink library, not a Qt screenshot or docs notebook.
