Skip to main content
The Runs Service in the Galtea SDK allows you to manage runs for your products. A run groups the sessions and evaluations of one launch, so a nightly job, a colleague’s launch and a rerun stay separate. This Service is exposed by the galtea.runs object.
Remember that we will be using the galtea object. More information here.

Quick Example

First, initialize the Galtea SDK:
Open a run and put work inside it:
Find the run again by the label you gave it:

Joining work to a run

These methods accept a run_id: sessions.create, sessions.get_or_create, evaluations.create, evaluations.create_single_turn, evaluations.run and traces.create_and_evaluate. Inside a with galtea.runs.start(...) block you can leave run_id out: the SDK reads the open run from the block. An explicit run_id always wins over the block.
You only close a run you opened yourself. A run that a launch opened ends on its own when its last launch ends, so close() finds it already ended and refuses it.

Service Methods

Run

The record of one evaluation launch