vibeflow-openradioss

Generate OpenRadioss explicit-dynamics input decks from caseDict data.

12|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-openradioss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow-openradioss
Source: https://github.com/sunrise-hjx/vibeFlow-skills/tree/main/vibeflow-openradioss
Command: npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-openradioss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables OpenRadioss to be used as the VibeCAE backend for explicit-dynamics workflows, providing runnable, diagnosable, and reproducible input decks from 0-caseDict/caseDict and templates for quick setup.

Core Features & Use Cases

  • Generate Starter/Engine decks from caseDict data, mapping parts/properties/materials and setting up explicit-dynamics input files.
  • Run OpenRadioss, monitor energy balance and time-step behavior, and post-process results with standard scripts.
  • Development support for deck templates, material libraries, and adapters to connect with upstream caseDicts and Ref data.

Quick Start

Generate Starter/Engine decks from 0-caseDict/caseDict and run a minimal OpenRadioss test to validate the workflow.

Frequently Asked Questions about vibeflow-openradioss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate OpenRadioss Starter and Engine decks from caseDict data?

OpenRadioss deck generation maps parts, properties, and materials from caseDict into explicit-dynamics Starter and Engine input files. The workflow produces runnable, reproducible decks for crash, impact, drop, and blast scenarios.

Can I run OpenRadioss simulations and monitor energy balance automatically?

OpenRadioss run control monitors energy balance and time-step behavior during explicit-dynamics executions. Standard post-processing scripts then evaluate results to ensure validated, diagnosable, and reproducible simulation outcomes.

What is the best way to set up OpenRadioss explicit-dynamics for crash and impact simulations?

OpenRadioss explicit-dynamics setup for crash and impact uses caseDict templates to generate Starter and Engine decks. The workflow handles materials, contacts, time controls, restarts, and standardized reporting for quick, validated setup.

Do I need specific environment checks before running OpenRadioss explicit-dynamics decks?

OpenRadioss explicit-dynamics workflows include environment checks before running Starter and Engine decks. These checks ensure the simulation environment is ready for validated, reproducible execution of crash and large-deformation scenarios.

Does OpenRadioss deck generation support restarts and standardized post-processing reporting?

OpenRadioss deck generation supports restarts, outputs, and standardized reporting with templates and adapters. The workflow ensures reproducible explicit-dynamics simulations by providing post-processing scripts and consistent result reporting.

Why use caseDict and templates for OpenRadioss input deck generation instead of manual setup?

caseDict and templates provide a structured, reproducible approach to OpenRadioss input deck generation, avoiding manual setup errors. This method ensures consistent mapping of parts, properties, and materials across crash, impact, and blast workflows.