Start LIVEX from source.
No installer is distributed yet. Here is how to run the SYNE + ECHOS stack from the repository, locally — a development environment, not a public service.
Read first. The development services run locally (127.0.0.1) and are not hardened for public exposure.
The prerequisites at a glance.
| Tool | Version | For |
|---|---|---|
| .NET SDK | 10.0.4xx | SYNE engine |
| Python | 3.11+ | ECHOS (observation, API) |
| Node.js | 20+ | syne-mock (integration) |
| Unreal Engine | 5.8 | PRISM and the PRISM-LDK plugin (outside V0.2 scope) |
| curl | — | Availability checks |
Three tools are enough for the full stack: .NET SDK, Python and Node.js. Unreal Engine is only needed for PRISM, which is outside the scope of V0.2.
The stack in one command.
From the root of the repository:
./scripts/dev-stack.shThe script prepares the Python environment, compiles SYNE, then starts the ECHOS API (port5000), SYNE (control 5181, WebSocket 5180) and ECHOS ingestion in order. It does not launch any simulation: SYNE remains in the Idle state until theStart command.
The API documentation is then available at http://127.0.0.1:5000/docs.
The mock for integration.
To advance Unreal integration without starting SYNE:
cd syne-mock
npm ci
npm start -- config_prism.jsonThe mock follows the SYNE observability contract, but simplifies deliberation and pathfinding: it serves integration tests, not scientific results.
Everything stays local.
| Service | Address | Role |
|---|---|---|
| SYNE WebSocket | 127.0.0.1:5180 | Snapshots and events from a controlled run. |
| SYNE HTTP | 127.0.0.1:5181 | Control of the server and starting runs. |
| ECHOS API | 127.0.0.1:5000 | Runs, metrics and analyses (API only). |
| syne-mock | 127.0.0.1:5180/5181 | Integration server (launched separately). |
No service is exposed outside your machine: all four addresses above point to127.0.0.1.
Check that everything works.
# SYNE
cd syne && dotnet test Syne.sln --configuration Release
# ECHOS (from the root)
echos/.venv/bin/python -m pytest -q
# Launcher
cd launcher && dotnet test Launcher.Tests.UnitExperimental Measured on 19 octobre 2026: 0 failures across these three suites. The paths remain indicative and follow the development repository.