Skip to content

Notebook Algorithm Toggle Coverage

Experiment notebooks that call notebooks.marimo_cli.apply_cli_overrides(...) must declare every supported top-level run_* algorithm toggle in their local config dict, even when a variant defaults to False.

Why this matters:

  • apply_cli_overrides(...) only accepts top-level or one-level nested override keys that already exist in the notebook config.
  • Missing toggles are therefore not just hidden in the UI; they cannot be enabled from the notebook CLI at all.

Current convention:

  • Notebook configs should list the full algorithm family supported by the underlying experiment helper.
  • Every algorithm toggle should default to False; local and scheduled runs opt into only the algorithms they intend to execute.
  • Temporal-game style suites should expose: run_ippo, run_ippo_cer, run_pr2_ippo, run_pr2_ippo_cer, run_iql, run_iql_cer, run_pr2_iql, run_pr2_iql_cer, run_nashq, run_nashq_cer, run_hc_ippo, run_hc_pr2_ippo, run_hc_iql, run_hc_pr2_iql, and run_hc_nashq.

The launcher policy in notebooks/experiments/scripts/support.bash owns the same 15 IDs. Keep notebook toggles, ALGORITHM_ORDER, launcher IDs, and regraph directory mappings synchronized when adding or removing an algorithm.

When backfilling older notebooks, add missing toggles with False defaults. This exposes the full choice set without silently running algorithms that were not explicitly selected.