Skip to main content

Minimal run

The object returned by dataset.eval(...) is a run (Eval):

Task requirements

@ze.task functions must:
  • Return a dict
  • Include all declared outputs
If required outputs are missing, the SDK raises a validation error.

Task outputs vs signals

  • Return task outputs in the dictionary from your @ze.task(...).
  • Emit signals during execution for runtime facts you may want to inspect or score later.

Execution controls

Use ExecutionConfig for runtime behavior:

Key knobs

  • workers: thread pool size
  • max_in_flight: max queued concurrent futures
  • timeout_s: per-row future timeout
  • retry: transient retry policy
  • failure.on_row_error: "continue" or "stop"

Checkpointing

Enable incremental persistence for long runs:
Checkpointing reduces work lost on interruption and supports strong resume behavior.

Emit runtime signals

Tasks can emit runtime observations while they execute:
Signals are attached to the current task span by default and can later be inspected in trace-aware eval views. Use signals for execution facts, then use evaluations to convert those facts into scores.

Attach run metadata

Use parameters to persist contextual metadata with the run:
Keep runs self-describing by always storing model name, dataset version, and subset in run parameters.

Health and execution summary

After execution, inspect run.health to understand whether the run completed cleanly: