OpenCourant cloud solver

OpenCourant โ€“ explicit dynamics

Crash, impact and drop tests in the cloud with OpenCourant

OpenCourant is the open-source explicit finite element solver that carries on the OpenRadioss code. Upload your Radioss or LS-DYNA input deck, choose the number of cores and launch: cloudHPC runs the starter and the engine files in sequence and converts the animations for ParaView. You pay only while the machine runs.

Animation of a vehicle crash simulation run on cloudHPC
.rad + .keyRadioss and LS-DYNA input formats
MPI + OpenMPevery core and hardware thread used
0 โ‚ฌlicence: open source (AGPL v3)
300 hfree vCPU hours for new users
What is OpenCourant

The open-source future of the OpenRadioss solver

OpenRadioss, the open-source release of the Radioss solver, was discontinued by its owner in October 2026. OpenCourant continues it from the last open-source code base, with the full commit history, as an incubator project of the Rocky Enterprise Software Foundation. Its name honours Richard Courant and the Courantโ€“Friedrichsโ€“Lewy condition behind every explicit solver. Your existing OpenRadioss models keep running, and cloudHPC had OpenCourant online within days of its first release.

1

Crashworthiness

  • Full-vehicle and component crash
  • Occupant safety and energy absorption
  • Large models with millions of elements
2

Drop tests and impact

  • Electronics, packaging and consumer products
  • Damage, deformation and failure prediction
  • Ballistic and high-velocity impact
3

Explicit time integration

  • Highly non-linear, short-duration events
  • Large deformations and rotations
  • Robust for problems where implicit solvers struggle to converge
4

Materials

  • Elasto-plastic, viscoelastic and hyperelastic laws
  • Damage and failure models
  • Strain-rate dependent behaviour under dynamic loads
5

Contact

  • Self-contact and contact between parts
  • Friction and separation
  • Tied interfaces and rigid bodies
6

ALE and SPH

  • Arbitrary Lagrangianโ€“Eulerian and smoothed particle hydrodynamics
  • Fluidโ€“structure interaction with large deformations
  • Water impact, sloshing and blast events
On cloudHPC

How an OpenCourant run works

What you upload

  • Radioss format: the starter *_0000.rad and one or more engine files *_0001.rad, *_0002.radโ€ฆ
  • LS-DYNA format: a .key input deck
  • Include files and material data in the same folder
  • Prepared in HyperMesh, ANSA or any tool that writes these formats

What cloudHPC does

  • Runs the starter, then every engine file one after the other
  • Uses MPI on every physical core and OpenMP on every hardware thread
  • Converts the animation files to VTK at the end, ready for ParaView
  • Keeps the starter and engine logs for each run

Control the run while it is going

  • Send engine commands to a running job with a .ctl file
  • /ANIM or /H3D to write output now, /CHKPT to write a restart
  • /STOP or /KILL to end the run cleanly or immediately

OpenRadioss models

  • OpenRadioss is still available on cloudHPC, with the same set-up as OpenCourant
  • Rerun older projects on the solver they were built with, or move them to OpenCourant with no changes
Why in the cloud

What changes compared with your workstation

StepOn a workstationOn cloudHPC
InstallationBuild the solver, MPI and the tools for each new releaseOpenCourant and OpenRadioss pre-installed and maintained
HardwareA full-vehicle crash keeps your PC busy for daysUp to 224 vCPU per run, only while it lasts
Load casesImpact speeds and angles run one after anotherEvery load case on its own machine, at the same time
OptimisationFew design iterations in the time availableMany variants in parallel, driven by the API
Post-processingDownload large animation filesParaView on a remote desktop, on the same storage
Choosing the machine

How many cores does my model need?

Rule of thumb

  • Plan for about 20,000โ€“30,000 elements per core
  • Hyperthreaded machines are used in full: MPI on the cores, OpenMP on the threads
  • hypercore gave the best cost/performance in our benchmarks

Good to know

  • A .ctl file left in the folder stops the engine sequence: delete it before relaunching
  • Test the model on a short end time before the full run
  • More details in the scalability guide
Why cloudHPC

Explicit dynamics without the IT work

Expert support

Our engineers run structural and multiphysics simulations every day and can help you set up, size and debug your models.

Pay per use

No subscription and no licence: you pay per vCPU hour, only while the machine runs. Check the cost with the price calculator.

Automate with the API

Launch whole load-case matrices from your own scripts with the cloudHPC API. The platform is ISO 27001 certified.

Get started

Your first OpenCourant run in five steps

  1. Register on cloudHPC and activate your account.
  2. Prepare the Radioss or LS-DYNA deck in your pre-processor.
  3. Upload the input and include files to a storage folder.
  4. Choose the cores and launch OpenCourant.
  5. Post-process the VTK results in ParaView on a remote desktop, or download them.

Run your next crash or impact model in the cloud

Create your account and get 300 free vCPU hours to try OpenCourant on your own model.

OpenCourant is an incubator project of the Rocky Enterprise Software Foundation, released under the GNU AGPL v3. Radioss is a trademark of its respective owner. cloudHPC is not affiliated with or endorsed by the OpenCourant project, Siemens or Altair.