Skip to content

Type to search titles, section headings and summaries across the Developer Portal.

↑ ↓ to move · Enter to open · Esc to close · searched locally in your browser

Concept

Integrations

Technologies and workflows Synthex may connect with, each with an accurate status. No integration is currently implemented and no partnership is implied.

Page type: Explains how the platform is designed to fit together.

Integration status key

Implemented and Verified
A working integration exists and has been tested.
Experimental
Prototype integration work exists but is not supported.
Exploratory
Being researched as a candidate technology; no integration code exists.
Proposed
An intended interoperability target; nothing is implemented.

Machine learning

Training stays in your environment, with your framework. Synthex's intended role is to supply datasets in open formats and to evaluate the resulting models.
Machine learning integrations and their status
TechnologyStatusPossible pattern
PyTorchOpen-source deep learning framework.ProposedLoad packaged datasets through a standard Dataset class that reads the manifest, images and labels.
TensorFlowOpen-source machine learning platform.ProposedRead the same files with tf.data pipelines; no framework-specific export is required.
Common computer vision workflowsClassification, detection and segmentation training and evaluation scripts.ProposedUse open annotation formats (COCO-style, YOLO-style, indexed masks) that existing tooling already reads.

Dataset formats

Open formats are the main interoperability mechanism. No Synthex exporter is released yet; the formats below are documented targets.
Dataset formats integrations and their status
TechnologyStatusPossible pattern
COCO-style JSONImages, categories and annotations (boxes, polygons, RLE) in one JSON file.ProposedDetection and instance segmentation datasets.
YOLO-style text labelsOne text file per image: class id and normalised box per line.ProposedLightweight detection datasets.
JSON annotation metadataPer-sample metadata: source, scenario parameters, seeds, licence.ProposedProvenance and filtering by condition.
Segmentation masksIndexed PNG masks whose pixel values index the class list.ProposedSemantic segmentation datasets.

Simulation

Simulators are candidate engines for scenario-based data generation and testing. None is integrated, and no vendor relationship exists.
Simulation integrations and their status
TechnologyStatusPossible pattern
CARLAOpen-source autonomous driving simulator (code MIT, assets CC-BY), built on Unreal Engine.ExploratoryUnder exploration for research scenarios: a scenario configuration would be translated into simulator settings and sensor definitions.
Unreal EngineReal-time 3D engine.ProposedPossible rendering backend for photorealistic scenes, directly or via simulators built on it.
UnityReal-time 3D engine.ProposedPossible environment for custom scenes such as agricultural fields or warehouses.
Other compatible frameworksAny simulator that can be driven by configuration and export sensor data.ProposedAn adapter boundary keeps scenario definitions independent of a single simulator.

Infrastructure

Generic infrastructure patterns, not services Synthex operates today.
Infrastructure integrations and their status
TechnologyStatusPossible pattern
Cloud object storageStorage for images, masks, manifests and reports.ProposedDatasets as immutable, versioned prefixes referenced by manifests.
Containerised processingGeneration, validation and evaluation steps packaged as containers.ProposedReproducible environments with pinned dependencies.
Batch compute systemsQueued, asynchronous execution of long-running jobs.ProposedSee the batch processing concept in Architecture.

Experiment tracking

Reproducibility depends on recording exactly what was run.
Experiment tracking integrations and their status
TechnologyStatusPossible pattern
Versioned experiment manifestsJSON configuration recording model, dataset version, protocol, metrics and seed.ProposedSee the experiment configuration in the Evaluation Engine guide.
Common ML evaluation practicesHeld-out test sets, fixed protocols, per-condition reporting.ProposedApplied in documentation examples and the research methodology.

Interoperability principles

  • Open formats first: datasets should be usable with existing tools without a Synthex dependency.
  • Explicit manifests: datasets, scenarios and experiments are identified by id and version, not by file paths.
  • Customer-controlled environments: training and sensitive data stay where their owners keep them.
  • Adapters at the edges: simulator- or framework-specific code stays behind a narrow boundary.