Logs and Run Analysis

The Run Logs tab in the moderator dashboard is used after a run has started or finished. It helps course staff review what happened, export data, compare repeated runs of the same game, and prepare analysis text for an external AI assistant.

Run logs are organized by run. A run is one moderator start of one game definition, and it may contain one or more sessions.

Run Log List

The list shows recent runs grouped by date. A row may include:

• start time,
• game name,
• session label,
• run status,
• participants,
• available files and analysis views.

Live or incomplete runs may still be changing. Some analysis buttons are intended for completed runs, where the full event sequence is available.

Main Analysis Views

The first row of actions is intended for regular review:

• timelineCsv: a time-ordered view of session start, player login, decisions, inputs, selected outcomes, payoffs, and session end.
• variablesCsv: recorded input, calculated, result, payoff, and state variables when the runtime can expose them.
• summary: a compact run summary.
• sessions: per-session summary inside the same run.
• compare: comparison with other finalized runs of the same game definition.
• charts: basic visual summaries such as activity and payoff views.
• aiInput: a Markdown report designed to paste into an external AI assistant.

The user interface uses teaching-oriented names in summaries: Extensive Form Game for tree games and Strategic Form Game for matrix games.

AI Input

The aiInput action prepares a text report that combines run metadata and the available analysis tables. The report asks an external AI assistant to summarize the run, identify important decisions and outcomes, compare sessions when possible, and state uncertainty when the data is not sufficient.

Some browsers allow the application to copy the text directly to the clipboard. Other browsers may block clipboard writes; in that case the text is selected in the panel so it can be copied manually.

For Extensive Form Games, remember that only decisions on the reached path are logged as player decisions. A player can receive a payoff even if that player did not act on the reached path.

Deleting Logs

The dashboard may offer a delete action for a run log. Deleting asks for confirmation. Use it carefully, especially after real classroom runs.

Interpreting Results

Logs are evidence of what the server recorded during the run. They are useful for checking player joins, submitted decisions, selected outcomes, payoffs, timing, and unusual sequences.

If a run is interrupted, incomplete, or still live, treat analysis as partial. If a table looks inconsistent with the visible game result, keep the run log and contact the project maintainer.