vibeflow-openradioss

name	vibeflow-openradioss
description	Use when preparing, running, debugging, post-processing, or extending VibeFlow/VibeCAE OpenRadioss explicit dynamics workflows from 0-caseDict/caseDict, including Starter/Engine decks, materials, contacts, boundary conditions, loads, time controls, restart/output files, crash/impact/blast/drop studies, and reusable explicit-dynamics templates.

VibeFlow OpenRadioss

This skill treats OpenRadioss as the VibeCAE backend for explicit dynamics, impact, crash, drop, blast, transient nonlinear structure, and high-speed loading.

• Usage mode: generate Starter/Engine input decks from caseDict, run OpenRadioss, and read time-history and field outputs.
• Development mode: develop deck templates, material/contact libraries, result converters, parameter sweeps, or coupling interfaces.

When to Use

• The task is crash, impact, drop test, blast, forming, high-speed contact, large deformation, or explicit transient structural dynamics.
• _0000.rad Starter decks, _0001.rad Engine decks, time history, animation, or restart files must be handled.
• Explicit structural capability is needed as an alternative or complement to CalculiX/Code_Aster implicit workflows.

First Decide: Usage Mode or Development Mode

• Current explicit-dynamics case setup and run: use usage mode.
• Deck generators, material libraries, contact templates, converters, or Studio adapters: use development mode.
• OpenRadioss commands, environment variables, MPI, or license-free execution are abnormal: hand off to vibeflow-toolchain first.
• Mesh, part, or set definitions are not prepared: hand off to mesh or geometry first.

What to Read First

• Materials, parts, contacts, constraints, loads, initial velocity, end time, output objectives, and safety metrics in 0-caseDict/caseDict.
• references/openradioss-playbook.md
• references/openradioss-practical-tips.md: software knowledge base, key concepts, failure interpretation, and adapter design notes.
• Parts, sets, shell/solid elements, and units under B-mesh/.
• Existing C-run/openradioss/ and Ref/ material.

Input

• 0-caseDict/caseDict
• OpenRadioss decks, mesh, part/set definitions, material parameters, contacts, and loads

Output

• C-run/openradioss/case-*/case_0000.rad
• C-run/openradioss/case-*/case_0001.rad
• C-run/openradioss/case-*/Allrun / Allclean
• .out, time-history data, animation, restart files, and logs
• D-post/openradioss_postprocess.py

Recommended Structure

C-run/openradioss/
`-- case-1/
    |-- case_0000.rad
    |-- case_0001.rad
    |-- include/
    |-- logs/
    |-- results/
    |-- Allrun
    `-- Allclean

Usage-Mode Workflow

1. Map caseDict to OpenRadioss decks: units, nodes/elements, parts, materials, properties, contacts, BCs, loads, initial velocity, time step, and output.
2. Clearly separate the responsibilities of the Starter deck and the Engine deck.
3. Check unit system, material model, contact definitions, mass scaling, and termination time.
4. Run Starter and confirm deck parsing and model checks.
5. Run Engine and monitor energy, time step, contact, mass change, and errors.
6. Post-process displacement, velocity, acceleration, force, energy, intrusion, failure indicators, and other target metrics.
7. Write run status, warnings, results, and limitations back to caseDict.

Development-Mode Workflow

1. Define the development target: deck template, material library, contact library, output converter, parameter sweep, or coupling interface.
2. Write a development note first, recording deck version, unit system, key cards, inputs/outputs, and validation example.
3. Templates must clearly describe units, part/set mapping, and default outputs.
4. For high-risk explicit models, validate contact and energy conservation on a small model first.
5. If developing a converter, preserve the original deck and conversion log.

Core Rules

• Explicit dynamics is highly sensitive to units, time step, material curves, contacts, and mesh quality.
• Starter success does not mean the physics is correct; Engine energy balance must be checked.
• Do not enable mass scaling by default unless caseDict or the user explicitly allows it and the impact is recorded.
• Output frequency must capture transient peaks while avoiding uncontrolled large files.

Validation

• Starter command is available and passes model checks.
• Engine can start and generate outputs.
• Energy, time step, and contact status show no obvious abnormality.
• Post-processing can read target time-history or animation results.

Fallback Rules

• Materials, contacts, or loads are unclear: return to vibeflow-case-dict.
• Mesh quality or part/set issues exist: return to the mesh stage.
• OpenRadioss environment is unavailable: return to vibeflow-toolchain.
• Energy is abnormal: check units, contacts, boundaries, time step, and materials.