Heavy jobs: what they do, where to click, and who triggers them (you, API, or cron). Copy in webShares/admin_automation_catalog.py.
| Control | Where | How triggered | Notes |
|---|---|---|---|
| Strategy experiments (rank & backtest candidates) | Strategies tab → workbench |
Manual
API
Started from the UI, or by scripts posting to the API. |
Runs deterministic backtests on the ranked shortlist for a chosen day—different weights, filters, or horizons—and stores each outcome as a recorded run. Endpoints: /api/experiments/run/, /api/experiments/design/, /api/experiments/recent/. No cron job in this repo starts these automatically. |
| Effectiveness reports (timing, ranking, recommendations, liquidity) | Operational reporting (CLI/API) |
Scheduled
API
Manual
After live candidate generation, or on demand via management command/API. |
Persists the Candidates shortlist daily via `persist_daily_candidate_shortlist`, then computes investment-outcome cohort reports via `compute_effectiveness_reports`. Staff API: /api/reports/effectiveness/. Automatically invoked at the end of `generate_live_candidates` unless `--skip-shortlist-persist`. |
| Outcome measurement (effectiveness → optimisation signals) | Strategies tab → Model Center (outcome signals API) |
Scheduled
API
Weekly cron via scripts/scRunOutcomeMeasurement.sh (Saturday 07:45). |
Primary path: `manage.py run_outcome_measurement` persists OptimizationOutcomeSignal rows and applies planner_state deltas on lane configs — no approve/reject queue. Staff APIs: /api/model-center/outcome-signals/ and /api/model-center/outcome-signals/dashboard/. See docs/plans/optimization-operating-model.md. |
| Model Center retest automation (retired) | Removed — use Strategy optimiser below |
Retired
Retired Phase C. Cron line removed from scripts/crontab-current.conf. |
RETIRED: champion-vs-challenger retest removed. `/api/model-center/automation/*` returns HTTP 410; `manage.py run_model_center_automation` is a no-op. Use Strategy optimiser and outcome signals instead. See docs/plans/optimization-operating-model.md. |
| Strategy optimiser (primary policy search) | Strategies tab → Automated policy search / Regression config |
Primary
Scheduled
API
Host cron drains the queue after close; UI sets global Automation On/Off (cron executes, not in-app timer). |
PRIMARY: searches weights, triggers, and (eventually) shortlist gates; one promotion recommendation per lane. Host runs `manage.py run_strategy_optimization_schedule` via scRunStrategyOptimisationTick.sh (weekdays 23:30 due check + drain; 03:00 queue safety net — see scripts/crontab-current.conf). Manual enqueue: POST /api/model-center/optimization/trigger/. Global toggle: POST /api/model-center/optimization/automation/. Outcome signals steer planner_state before due runs. |
| After-hours batch (prices, analysis, mail) | This page → Daily close pipeline |
Shortcut
Same as cron
Same workload as the nightly cron; this tile reruns it on demand. |
Downloads prices, refreshes analysis, updates watchlists, and sends summary mail for the post-close routine. Host wrappers and recovery flows are described in scripts/README.md (for example scStockBatchRunClose.sh, scRecoverMissedCloseBatch.sh). |
| Live candidate refresh | This page → Daily close pipeline |
Shortcut
After rankings
Normally follows the ranking step after close; use this to regenerate sooner. |
Rebuilds the saved candidate rows the workspace reads from. scripts/README.md explains generate_live_candidates and how it relates to the overnight batch. |
| Trading dry-run | This page → Command Execution |
Manual
Started manually from here unless you wire your own cron. |
Runs trading-batch checks without sending live orders—useful before trusting automation. |
| Platform regression tests | This page → Command Execution |
Manual
Started manually from here unless you wire your own cron. |
Runs the pytest suite through the legacy menu runner. |
Can outcome measurement and policy search run? Pipeline issues here block optimisation — funnel and ranking actions live on the Strategies tab.
System events, error summary, AI diagnosis, broker gateways, and MySQL status.
Loading...
Loading AI diagnosis...
Loading...
Broker reconciliation has not run yet.
Click Refresh to load the report.
Running reconciliation...
Usually under a minute; may take up to 2 minutes when syncing many orders.