Skip to content

FE-1719: Polish Experiment and Optimization results - #9726

Closed
kube wants to merge 10 commits into
codex/fe-1718-experiment-creation-polishfrom
codex/fe-1719-experiment-results-polish
Closed

kube wants to merge 10 commits into
codex/fe-1718-experiment-creation-polishfrom
codex/fe-1719-experiment-results-polish

Conversation

@kube

@kube kube commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Important

Experimental
Sweep controls require Parameter sweeps. Optimization progress and Sensitivity analysis also require In-browser optimization. The header and Details improvements apply to all experiments.

Summary

Experiment results now keep the name, status, and relevant progress in the header. Configuration and compute information are available in Details, including an explanation that a sweep's run count is a sampling limit for the selected parameter values or ranges.

Links

Blocked by

Changes

  • Plain experiments show completed runs; optimized sweeps show completed optimization steps, with failed runs visible when any occur
  • Details includes the scenario, sampling limit, simulation timing, compute backend, active batches, and search summary, and closes when switching experiments
  • Parameter controls distinguish testing an optimization step from sampling a selection and wrap in narrow panels
  • Surface and sensitivity summaries use shorter labels, with method information available through help
  • Sensitivity analysis orders parameters by descending Share, keeps ties stable, and places missing estimates last while preserving correlations and confidence indicators
  • The experiment guide describes the updated controls, and a patch changeset covers the published package

Test coverage

  • Results-model and panel tests cover progress labels, failure counts, Details contents, experiment switching, optimization controls, and chart layout
  • Importance-view and visited-field tests cover descending shares, ties, missing estimates, confidence indicators, and chart summaries
  • Existing panel and navigation tests cover fullscreen transitions and retained panel state

Builds, unit tests, TypeScript checks, and lint passed for Petrinaut and the website: 20 tasks in total. Repository formatting and architecture checks also passed.

How to test

All experiments

  • Open Simulate > Experiments and run an experiment
  • Open its results and check that the header shows the name, status, and completed-run progress
  • Open Details and inspect the scenario, requested runs, timing, and compute backend
  • Switch to another experiment and confirm Details closes

Sweeps and optimization

  • Enable Parameter sweeps and In-browser optimization in settings
  • Create an optimization with multiple swept parameters
  • Check that the header counts optimization steps and the parameter controls show the current step's sampled runs
  • After optimization completes, move a parameter control and confirm the status shows sampling progress for the new selection
  • Open Details and confirm the sampling limit is explained separately from optimization progress
  • After importance estimates arrive, confirm the Sensitivity analysis rows descend by Share
  • Expand the results to fullscreen, then return to the panel and check that chart choices remain selected

@kube
kube added this pull request to stack #9699 September 15, 2026 00:43
@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
hash Ready Ready Preview Sep 15, 2026 10:32pm UTC
petrinaut Ready Ready Preview Sep 15, 2026 10:32pm UTC
petrinaut-docs Ready Ready Preview Sep 15, 2026 10:32pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
hashdotdesign-tokens Ignored Ignored Preview Sep 15, 2026 10:32pm UTC

Request Review

@github-actions github-actions Bot added area/infra Relates to version control, CI, CD or IaC (area) area/libs Relates to first-party libraries/crates/packages (area) type/eng > frontend Owned by the @frontend team labels Sep 15, 2026
@kube kube self-assigned this Sep 15, 2026
@kube kube changed the title codex/fe 1719 experiment results polish FE-1719: Polish Experiment and Optimization results Sep 15, 2026
@kube
kube removed this pull request from stack #9699 September 15, 2026 01:16
@kube
kube force-pushed the codex/fe-1718-experiment-creation-polish branch from 694d65b to c9e1393 Compare September 15, 2026 01:17
@kube
kube force-pushed the codex/fe-1719-experiment-results-polish branch from c175403 to 520e7fe Compare September 15, 2026 01:18
@kube
kube added this pull request to stack #9730 September 15, 2026 01:18
@kube
kube removed this pull request from stack #9730 September 15, 2026 02:00
@kube
kube force-pushed the codex/fe-1719-experiment-results-polish branch from 520e7fe to a0263db Compare September 15, 2026 02:01
@kube
kube force-pushed the codex/fe-1718-experiment-creation-polish branch from c9e1393 to 8907f84 Compare September 15, 2026 02:01
@kube
kube added this pull request to stack #9731 September 15, 2026 02:02
@kube
kube removed this pull request from stack #9731 September 15, 2026 02:30
@kube
kube force-pushed the codex/fe-1718-experiment-creation-polish branch from 8907f84 to ad30c2e Compare September 15, 2026 02:30
@kube
kube force-pushed the codex/fe-1719-experiment-results-polish branch from a0263db to 72bc415 Compare September 15, 2026 02:30
@kube
kube added this pull request to stack #9733 September 15, 2026 02:31
@kube

kube commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

Consolidated into #9725, which now contains the experiment creation, results, and optimizer-control changes. The active stack is #9752, with #9728 based directly on #9725.

@kube kube closed this Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/infra Relates to version control, CI, CD or IaC (area) area/libs Relates to first-party libraries/crates/packages (area) type/eng > frontend Owned by the @frontend team

Development

Successfully merging this pull request may close these issues.

1 participant