Workflow

From an image to annotations and a program

Images, video or screen recordings are stored in a project with annotations, descriptions and computer vision results. Selected materials can be used in Screph Code, external tools and Automation Runtime. Code development and script execution use separate commands.

01
Program Mode

Program mode

The mode determines the available object types and tools. General and GUI Automation support basic workflows; Industrial and UAV remain experimental.

In the project: mode and compatible settings of Selector and computer vision.
02
Capture

Visual source

The source can be a screen region, window, monitor, camera, network stream, image, video or folder. Capture preserves each frame’s source and position on the timeline.

Output: frames, source information and timestamps.
03
Selector

Annotation and relations

In Selector, you create elements, features, regions of interest, annotations and typed relationships. Annotation changes can be undone and redone.

Output: editable main project markup.
04
Computer vision

Computer-vision results

A single method, sequence, or graph of methods can create masks, outlines, detections, recognized text, metrics, and a log. Methods with models require a prepared environment and model files.

Output: masks, detected objects, text and other data to compare with the source image.
05
Review

Checking the result

Preview, overlay, mask and metrics help you evaluate the result. In supported processes, a proposed change can be accepted, modified, rejected, or recalculated.

Important: the result of the method does not change the underlying markup without the user's decision.
06
Main project

Main project

The project stores the format version, source images, markup, links, groups, descriptions and links to attached results. When loading, the structure and associated files are checked.

Output: a project that can be reopened and edited.
07
Code and execution

Code and execution

Screph Code and supported external tools receive selected task data. Automation Runtime uses the main project along with a separately prepared script.

Launch: work with code and input actions begin only on a separate command.
Data structure

Markup, methods and recording of actions

Project relation graph

Stores typed relationships between elements and features of the main markup.

Processing graph

A processing graph with typed inputs and outputs and an execution log. It transforms visual data.

Action trace

Contains user actions and associated frames. Action CV saves proposed results alongside the original recording.

Documentation

First project: source, markup and saving

Getting started