rtemis (version 1.4.3)

session_timeline: Session Execution Timeline Table

Description

Flatten the execution graph captured in a SupervisedSession (from train()) into a timeline (Gantt) table: one row per recorded node, ordered as a depth-first walk of the execution tree, with start/end offsets in milliseconds from session start.

Usage

session_timeline(x)

Value

data.table with one row per node in depth-first order and columns:

• label Character: Unique display label, indented two spaces per tree depth (duplicates disambiguated with " #<n>" suffixes).

• start Numeric: Node start, milliseconds from session start.

• end Numeric: Node end, milliseconds from session start.

• kind Character: Node kind (e.g. "tune", "grid_cell", "train_alg").

• status Character {"ok", "error", "aborted", "running"}: Node status.

• failed Logical: TRUE when status is "error" or "aborted".

• tip Character: Preformatted tooltip text ("name -- duration [status]").

Arguments

x

Supervised or SupervisedRes model, or the SupervisedSession it carries.

Author

EDG

Details

This is the single source of the tree-walk, labeling, and status logic for timeline renderers. rtemis.server consumes it for the job.result session slice, which the rtemislive web UI draws; pair it with session_kind_colors() to color bars by node kind.

Nodes that never closed (status "running" or "aborted" with no end time) are drawn up to the session finish time when known, else to the latest recorded node start. A session that recorded no nodes, and a model that carries no session, have a timeline of zero rows.

Examples

mod <- train(iris, hyperparameters = setup_CART())
# One row per recorded node, depth-first: the run, then the steps under it.
session_timeline(mod)