Strategies示例数据 · SAMPLE/strategies

Annotations: ① Opens the Add strategy dialog (see 03b / 03c). ② Clicking a strategy row (or its name) opens the strategy page /strategies/:id which shows the latest completed backtest (03e; no page tabs, all runs in the Backtests drawer, 03g; see 03e–03l). A strategy with no completed backtest lands on the empty state with Run first backtest (03e variant ⑯). Its display name defaults to the class name with a trailing "Strategy" / "Algorithm" suffix removed. ③ Algorithm: the full class name with namespace, i.e. Lean algorithm-type-name, with assembly, version number (vN, a new version each time the algorithm fingerprint changes) and parameter count underneath. ④ Status is the lifecycle of the strategy itself and is derived from version activation. A newly added strategy is Draft (no activated version yet): it can be edited and backtested but cannot have bots. Activating a version from a completed backtest (version line of the run card, 03e ⑦) makes it Active automatically; later unactivated dev versions (VegasTunnel v7) do not change it. Deactivating the last activated version (only possible while no bot, running or stopped, uses it) turns it back to Draft; a manually set Inactive or Archived stays unchanged. Inactive is manual: Set inactive… in the strategy header ⋮ menu (03e ④) pauses it (no bots can be added, running bots keep running) and Reactivate in the same menu makes it Active again; Archive… is there too. Active and Draft are never set by hand. Archived (from Draft, Active or Inactive, only when no bot is running): read-only, hidden unless shown via list settings (⑧). ⑤ Bots are running instances of a strategy: a pinned version (never the latest automatically) + parameters + broker / exchange account + runner (Local for now) + paper or live mode. One strategy can have several bots (e.g. VegasTunnel on Binance and on Bybit); the column summarizes their run state and links to the Bots page (sidebar QUANT › Bots) filtered by this strategy. Bots are added only on the Bots page, not from this list or the strategy page. ⑥ Row actions are three icon buttons with tooltips (Backtest tooltip shown on hover, row 1): Edit, Backtest, Archive. The Backtest icon runs a backtest immediately with the last settings of that strategy (latest version from source; last period, the first time the dates in code), with no dialog; a Snackbar Run #43 started · VIEW appears and the run shows on the strategy page (opened on the running run, and at the top of the Backtests drawer). There is no row menu and no Run with options… on the list: choosing version and period is only in the strategy header split button (03e ③, dialog 03i). On archived rows Edit and Backtest are disabled and Archive is replaced by Unarchive, so restoring a strategy stays one click away (it returns to its previous status). Version activation lives on the version line of the run card on the strategy page (03e ⑦); a version can be deactivated from its ✓ Activated chip only while no bot uses it; Set inactive… (no bots can be added) and Archive… are in the strategy header ⋮ menu (03e ④). ⑦ Filter card: Name (matches display name or full type name), Market, and Status (options Draft / Active / Inactive; Archived is not a filter option). Search applies the filters to the table; Reset clears them back to the defaults (empty search, All, All) and reloads. ⑧ List settings (gear) opens a dialog (see 03d) with one setting, Show archived strategies (off by default, remembered per user). In this mockup it is on, so the archived OldBreakout row is shown and the toolbar says "Showing archived"; when off, archived rows are hidden.
Sample data: the strategy list, versions, statuses and bots are for illustration only. VegasTunnel is a hypothetical spot long-only example.