Semantic segmentation is not available in Geti v3.0 (adapt to instance segmentation)

[yvolokitin]

We want to inform the community about a change to supported workflows in the current release.

Geti™ v3.0 does not support semantic segmentation as a task. However, we are considering reintroducing it — with various improvements — in a later release.

What changed
Semantic segmentation is not available in v3.0.
Semantic segmentation projects cannot be recreated as-is in v3.

Action required / alternatives
Convert your use case to instance segmentation in Geti™ v3 (see migration steps below), or
Continue using Geti™ 2.13 for these use cases in the meantime.

Migrating to instance segmentation in v3
📖 For the full step-by-step guide, see the v2 → v3 migration documentation

Export the dataset from Geti™ 2.x

1. Log in to your Geti™ 2.x instance.
2. Open the project that contains the dataset you want to migrate.
3. Select the dataset, open the Export/Import menu, and click Export dataset.
4. Choose Datumaro as the export format.
5. Wait for the export job to complete, then download the resulting .zip archive.
   If Geti™ ≥3.0 is installed on a different machine, move the dataset archive there.
6. Create a new Geti™ ≥3.0 project from each dataset

Open the Geti™ ≥3.0 desktop application.

1. On the Home screen, click the Create from dataset button.
2. Upload the .zip archive exported in the previous step.
3. Confirm the task type Geti suggests (or change it), assign a name to the new project, and review the label mapping.
4. Click Create and wait for the import to finish.

For a full walkthrough of the import wizard — including label mapping and dataset statistics — see Start your project with a dataset import.

Feedback
If you have an interesting use case that involves semantic segmentation, please share details in the tracking thread