How ggiraldo/openradioss works
OpenRadioss is a nonlinear dynamic finite-element simulation code. The principal workflow is to provide an input deck, have Starter read it, run the Engine, and produce results for post-processing. The tree also identifies input-model parsing, element kernels, coupling adapters, user extensions, Python integration, and H3D output as distinct capabilities. Several runtime relationships are only implied by the repository layout and README; those links are marked dashed with no evidence path because the relevant call sites were not sampled.
Main entry points: engine/source Engine · starter/source Starter · KERNEL Config kernel · MODEL_IO Model reader
Components 15
Input processing
- Starter
starter/source - Model reader
reader/source/cfgio/MODEL_IO - Config kernel
reader/source/cfgkernel/KERNEL - Units
reader/source/cfgkernel/MUNITS/mu_quantity_manager.cpp - Expression operators
reader/source/cfgkernel/UTILS/mv_operator_manager.cpp
Simulation
- Engine
engine/source - Shell kernels
engine/source/elements/shell/coque
Extensions and coupling
- Coupling adapters
engine/source/coupling - Radioss coupling
engine/source/coupling/rad2rad/rad2rad_c.c - User extensions
engine/source/user_interface/dyn_userlib.c - Python interface
common_source/modules/cpp_python_funct.cpp
Results and runtime
- Binary file I/O
common_source/tools/input_output/write_routines.c - H3D output
engine/source/output/h3d/h3d_build_cpp - Post-processing tools
Other components
- Analyst
Connections 14
- Analyst → Starter: provides deck
README.md - Starter → Model reader: reads models
- Model reader → Config kernel: interprets configuration
- Config kernel → Units: uses units
- Config kernel → Expression operators: uses operators
- Starter → Engine: passes model
- Engine → Shell kernels: uses kernels
- Engine → Coupling adapters: dispatches coupling
- Coupling adapters → Radioss coupling: offers adapter
- Engine → User extensions: invokes hooks
- Engine → Python interface: uses interface
- Engine → Binary file I/O: writes data
- Engine → H3D output: writes results
- H3D output → Post-processing tools: supplies results