feat: add deterministic office robot jobs
This commit is contained in:
@@ -74,9 +74,10 @@ npm run dev
|
||||
|
||||
## Headless RL environments
|
||||
|
||||
Tera also exports a versioned, renderer-independent Arena contract with four
|
||||
Tera also exports a versioned, renderer-independent Arena contract with five
|
||||
deterministic environments: US-101/I-5 driving, Frontier Valley office
|
||||
navigation, crow waypoint flight, and California electric-aircraft flight.
|
||||
navigation, seeded SF/LA office robot jobs, crow waypoint flight, and California
|
||||
electric-aircraft flight.
|
||||
They share the client controllers and office plan, but require no canvas, DOM,
|
||||
Three.js scene, network service, or new runtime dependency.
|
||||
|
||||
@@ -85,6 +86,11 @@ component rewards, safety terminals, maximum steps, snapshots, checksummed
|
||||
traces, exact replay and executable inaction/scripted baseline proofs are
|
||||
documented in [ARENA.md](ARENA.md).
|
||||
|
||||
The visible SF and LA office robots use that same fixed-step job state. Their
|
||||
patrol, parcel, inspection, and charging loops are authored demonstration
|
||||
scenarios—not presence, telemetry, or evidence of real company work—and the UI
|
||||
labels them as a seeded simulation.
|
||||
|
||||
## Using the engine
|
||||
|
||||
```ts
|
||||
|
||||
Reference in New Issue
Block a user