GARMO SOFTWARE STUDIO

From input.
To something useful.

Follow a real recorded execution, inspect the result, then run your own bounded scenario in the included software playground.

2Included live engines
10Protected release archives
42Software & platform offerings
RECORDED ENGINE EXECUTION · 1.2.0

DieWeaver

A place for each task. A reason for every choice.

Run DieWeaver ↗
dieweaver / actual captured application output
Actual local dieweaver software interface after executing the archived engine on the supplied synthetic input.
01 / INPUT

A resource-placement problem

Capabilities, health, failure domains and a power budget define the supplied scenario.

02 / RESULT

Resources b and c

The recorded engine selects two failure domains using 18 scenario power units. These are scenario values, not measured chip power.

03 / NEXT STEP

Change the constraints.

Run a different bounded input, inspect failure as well as success, and save the product in your engineering project.

{
  "requirements": {
    "caps": 3,
    "count": 2,
    "health_min": 70,
    "max_latency": 10,
    "max_total_power": 20,
    "min_failure_domains": 2,
    "weights": {
      "diversity": 25
    }
  },
  "resources": [
    {
      "caps": 7,
      "failure_domain": "die0",
      "health": 95,
      "id": "a",
      "latency": 4,
      "power": 8,
      "score": 90,
      "valid": true
    },
    {
      "caps": 3,
      "failure_domain": "die1",
      "health": 88,
      "id": "b",
      "latency": 5,
      "power": 9,
      "score": 87,
      "valid": true
    },
    {
      "caps": 7,
      "failure_domain": "die0",
      "health": 96,
      "id": "c",
      "latency": 3,
      "power": 9,
      "score": 99,
      "valid": true
    }
  ]
}
Download this recorded execution ↗

This is a recorded local execution of the archived engine. The screen capture and JSON describe the same supplied case. Open the playground for fresh execution; the offline preview does not execute backend software.

RECORDED ENGINE EXECUTION · 1.2.0

ModelNative

A model plan that knows its available resources.

Run ModelNative ↗
modelnative / actual captured application output
Actual local modelnative software interface after executing the archived engine on the supplied synthetic input.
01 / INPUT

Prefill and decode requirements

The supplied scenario describes model phases, available engines, memory fit and latency objectives.

02 / RESULT

Two planned phases

The output reports memory fit, selected engines and estimated latency. The estimates are model outputs, not measured semiconductor performance.

03 / NEXT STEP

Change the constraints.

Run a different bounded input, inspect failure as well as success, and save the product in your engineering project.

{
  "engines": [
    {
      "bandwidth_gbps": 800,
      "caps": 7,
      "energy_per_work": 0.005,
      "health": 95,
      "id": "m0",
      "memory_mb": 3072,
      "tops": 100,
      "valid": true
    },
    {
      "bandwidth_gbps": 600,
      "caps": 7,
      "energy_per_work": 0.004,
      "health": 92,
      "id": "m1",
      "memory_mb": 3072,
      "tops": 90,
      "valid": true
    }
  ],
  "phases": [
    {
      "io_gb": 4,
      "latency_slo_us": 200,
      "memory_mb": 4096,
      "name": "prefill",
      "parallelism": 2,
      "required_caps": 1,
      "work_units": 3000
    },
    {
      "io_gb": 2,
      "latency_slo_us": 150,
      "memory_mb": 2048,
      "name": "decode",
      "parallelism": 2,
      "required_caps": 5,
      "work_units": 1000
    }
  ]
}
Download this recorded execution ↗

This is a recorded local execution of the archived engine. The screen capture and JSON describe the same supplied case. Open the playground for fresh execution; the offline preview does not execute backend software.

Your next big idea.
Let’s build it together.

Start with a chip, a software release or a single IP block.