Automotive CAE · evidence build 01

Millions of elements.
Zero invented results.

physicsbase ingested the public 2.27-million-element Toyota Camry crash model, verified its archive byte-for-byte, and built an OpenRadioss execution path. This page separates that full-vehicle reference from the smaller impact case actually executed on the available four-core worker.

2,277,283Camry elements
2,273,631Camry nodes
56 km/hNCAP reference speed
60 hofficial 4-core runtime estimate
Claim boundary. The Camry numbers and validation targets below come from CCSA’s published model and test comparison. They are not relabelled as a new physicsbase solve. The component probe reached 14.9 ms before the 721.6 s session cap, with its last complete H3D frame at 14.0 ms. It is an interrupted execution trace, not a completed 20 ms result.

Interrogate the solver evidence

The interactive field below is a physicsbase-native, verification-checked static solve of a representative bumper crush beam — a 3D hex8 solid mounted at both crash-rail ends under a central barrier load. It is our own result, orbitable and colour-mapped. It is deliberately separate from the full-vehicle Camry run, whose OpenRadioss-derived spatial fields stay licence-withheld; that run appears here only as the interrupted energy trace.

CHECKING ARTIFACT
Waiting for artifact.

Spatial field: physicsbase-native bumper solve (drag to orbit · scroll to zoom) · Camry/OpenRadioss spatial fields remain licence-withheld

What was actually done

Full vehicle: ingested

The 63.6 MB CCSA archive was downloaded and matched its published SHA-384. The expanded 288 MB deck contains vehicle geometry, materials, 1,106 parts, instrumentation, initial wheel/vehicle velocity and contact definitions.

HASH VERIFIED

Component impact: traced

OpenRadioss Starter completed with zero errors and one initial-penetration warning. Engine advanced 14,900 cycles at a 0.001 ms step; the last reported energy error was −0.1% and relative mass change was 2.1151×10⁻⁴. The session cap interrupted the run before its declared end.

INTERRUPTED TRACE

Full crash: gated

The official OpenRadioss case page estimates roughly 60 hours on four cores. This worker had about 2.65 GB available RAM. physicsbase rejected a full launch rather than produce a partial or fabricated “completed crash.”

HPC REQUIRED

Representative component: solved

Rather than fabricate a full-vehicle field, physicsbase solved a representative bumper crush beam with its own verified solver — a 3D hex8 solid, both ends mounted, central barrier load. The result above is that solve: real geometry, real von Mises and displacement, self-check verdict attached. It is a component demonstration, not a Camry crash.

PHYSICSBASE VERIFIED

Published full-vehicle reference

QuantityPublished referenceProvenance in this page
Vehicle model2,277,283 elements · 2,273,631 nodes · 1,106 partsCCSA 2015 Camry model page and downloaded README
Crash conditionNCAP rigid wall · 35 mph / 56 km/h · 120 msCCSA 2012 Camry technical summary
Published response scale≈900 kN peak wall force · ≈650 mm maximum crushCCSA/LS-DYNA result; not physicsbase output
Published computeLS-DYNA MPP-S R8.0.0 · 16 processors · ≈11 hCCSA technical summary

Multiphysics and multiscale scope

The implemented workflow contract links a macro explicit crash to plastic-work-driven adiabatic heating, critical-zone submodel extraction, and coupon/RVE material calibration. Those transfers require a completed macro result plus conservation and mapping checks. No Camry temperature, residual-stress or damage field is published here until those prerequisites exist.

Sources and reproduction

GET /demo/automotive returns the same machine-readable claim boundary. A full run belongs on a worker with adequate memory and wall time; the backend is available under femengine.backends.openradioss.