hypermesh-new-interface

name

hypermesh-new-interface

description

Use when Codex needs to explain, teach, troubleshoot, or guide Altair HyperMesh 2023 and newer interface workflows, especially HyperMesh 2025/2025.1 meshing, tool locations, ribbon/browser/guide-bar/microdialog usage, legacy-panel-to-new-workflow migration, geometry cleanup before meshing, 1D/2D/3D mesh creation, Mesh Controls, BatchMesher, surface meshing, volume meshing, FE geometry, element quality checks, and official Altair documentation lookup. Trigger on HyperMesh, HyperWorks, HM 2025, HM 2023 new UI, mesh generation, mesh controls, BatchMesher, midsurface/midmesh, shell mesh, solid mesh, tetra/hex mesh, element quality, or requests asking where a legacy HyperMesh panel/tool moved in the new interface.

HyperMesh New Interface

Purpose

Guide HyperMesh 2023+ users through the new unified interface, with HyperMesh 2025/2025.1 as the default reference version. Prefer official Altair help, release notes, and learning pages over third-party tutorials.

Respond in Chinese by default when the user asks in Chinese, but keep official UI names in English and add short Chinese explanations after them.

Source Policy

Use official Altair sources first:

• Read references/official-docs.md to find official help entry points and targeted documentation links.
• Use current web lookup when the user asks for exact tool behavior, version-specific changes, or a page-level citation.
• Prefer 2025.1 docs for current 2025 workflows when available; use 2025 docs when 2025.1 pages are absent; use 2026 only as a signal that docs have moved or terminology changed.
• Treat non-official videos, blogs, forums, and Reddit as secondary hints only. Do not base final procedural guidance on them unless official docs are missing and clearly say the source quality.

When citing sources, cite the specific Altair help page used and keep quotes short. Paraphrase the workflow in practical step form.

Workflow

1. Identify the user's model target:

   • Solver/interface: OptiStruct, Radioss, Abaqus, Nastran, LS-DYNA, Ansys, or unknown.
   • Mesh type: 1D, 2D shell/surface, midsurface/midmesh, 3D tetra, hex, voxel, adaptive wrap, or BatchMesher.
   • Input state: clean CAD, dirty CAD, existing FE mesh, FE geometry, imported solver deck, or screenshots only.
   • Desired output: learning explanation, exact tool location, step-by-step operation, quality troubleshooting, or parameter recommendation.

2. Map the requested operation to the new interface:

   • Use ribbon names, tool names, guide-bar actions, browser names, context menus, selectors, and microdialogs.
   • If the user remembers an old panel, consult Tool Finder guidance in references/new-interface-navigation.md.
   • Avoid saying only "go to the old panel"; translate old-panel language to the new workflow.

3. Give a practical meshing path:

   • Start with import, solver interface, unit/scale sanity check, component organization, display/selection setup.
   • Clean topology or create FE geometry before meshing when needed.
   • Choose mesh method and controls.
   • Generate mesh.
   • Check quality against solver-relevant criteria.
   • Fix failures by adjusting topology, local controls, element size, feature capture, and quality criteria.

4. Ask for missing essentials only when the next step depends on them:

   • Solver target.
   • Desired element size or smallest feature to retain.
   • Geometry type and thickness handling.
   • Required element type or quality criteria.

References

• Read references/new-interface-navigation.md for UI concepts, Tool Finder use, display and selection details.
• Read references/meshing-workflow.md for meshing procedures, quality checks, and troubleshooting.
• Read references/official-docs.md for official Altair documentation links and search patterns.

Response Style

For operation guidance, use this shape:

1. "Goal": briefly identify the likely workflow.
2. "New interface location": ribbon/tool/browser path.
3. "Steps": numbered steps.
4. "Key parameters": element size, min/max size, criteria, controls, or selection modes.
5. "Check and fix": quality checks and likely fixes.
6. "Official basis": links or page names when verified.

Keep UI terms exact, for example Mesh ribbon > Mesh Controls, Mesh Controls Browser, guide bar, microdialog, QI Range, Tool Finder.