Skip to content
MeghaOS

Select language

MeghaOS speaks over 100 languages on your own machine. This site is available in full in every language listed here; our legal pages and blog posts stay in English.

FIG 3.5 · Simulation Studio

Turn a prompt intoa running model.

Describe a system and get an interactive simulation: 3D rendering, live parameters, and real-time editing. The code behind it is generated just in time, sandboxed, and yours to export.

FIG 3.6 · A simulation, live

A chaotic system, integrated in your browser.

The canvas below is a real double pendulum integrator, not a video. Drag the page away and it pauses itself.

Show me why a double pendulum is chaotic

try
Two arms, one hinge, no closed form
arm one arm two
Fixed pivot
Free hinge
Second mass

Change something

These controls are live. The renderer holds their state, not a server.

Mass ratio50%
1100
Gravity10 m/s²
120
Damping6%
040
Draw the trace
Two runs, one thousandth of a radian apart
separation (rad)
0s10s20s30s40s50s60s70s
FIG 3.6b · The surface

And this is Simulation Studio as it ships.

A 3D viewport with an Entities and Systems outliner, a mode toggle, and a transport row. Describe a change in plain language and it edits the running scene.

Simulation Studio
3D2DAuto
Generate

Entities · 1

knot

Systems · 2

spin

float

Speed1.0x

Interface, rebuilt in the page · v0.1.10

FIG 3.7 · Not a black box

The simulation is code, and you can take it with you.

A generated simulation is not a rendering the agent hands you; it is a module it wrote. You can read it, change it, break it, and export it into your own work. Nothing about the result is locked to MeghaOS.

  • Parameters are live: change one and the integrator responds immediately
  • Generated source is inspectable, editable, and exportable
  • Runs entirely on your hardware, so there is no per-simulation cost
  • Sandboxed like any other just-in-time code on the system
pendulum.py
# Every simulation is real code you can keep.
from megha.sim import Scene

scene = Scene("torus knot")
scene.entity("knot", geometry="torus_knot", p=2, q=3)
scene.system("spin", target="knot", rate=0.4)
scene.system("float", target="knot", amplitude=0.2)

scene.run(speed=1.0)
scene.export("knot.mp4")
FIG 3.8 · Where it fits

Useful when the answer is a behaviour, not a number.

Teaching and understanding

A system you can perturb teaches more than a plot of one run. Change gravity, watch the divergence, build the intuition.

Sensitivity, made visible

Run near-identical initial conditions side by side and see where they separate: the practical definition of a chaotic system.

Rapid what-if

Model a queue, a supply chain, a rate limiter. Anything where the interesting question is what happens over time.

Prototyping before committing

Generate a rough model in a minute, decide whether the real implementation is worth a week.

Run it on your own machine.

Free to download. Nothing leaves the device unless you connect it. Enterprise deployment is a conversation away.