Skip to main content

Overview

run_plot_job renders an HTML chart via SingleBlockGraphsMCP. Pick a block_name (family) and a tool_name (specific chart), plus params. Ask in chat (“equity curve for my last PO”, “AAPL close prices”) — skills fill block_name / tool_name for you.

Chart catalog

Prices (prices_graphs)

Input: data_extractor_*.json

Features (feature_graphs)

Input: feature_engine_*.json

ML predictions (ml_visualization)

Input: ml_engine_*.json (or compatible DL artifact with the same prediction fields)

Portfolio P&L (profit_and_loss_graphs)

Input: portfolio_optimization_*.json, or data_extractor_*.json with optional params.portfolio_weights (else equal 1/N)

Weights (weights_graphs)

For portfolio weights from a standard PO blob, prefer run_risk_job with function: "dynamic_weights". plot_weight_dynamics expects a wrapped weights.dates / weights.values shape, not raw PO Weights alone.

Parameters

string
required
Blob URL for the stage that matches the chart family (see table above).
object
required

Example


Returns

The file is named plot_<block_name>_<tool_name>_<id>.html, so you can tell from the link which chart it holds.

Next Step

A chart is usually the end of a branch, with one exception: run_ptl_job reads these HTML files as its input.
  • An equity curve (profit_and_loss_graphs / plot_equity_curve) goes in as equity_url and runs the curve test.
  • A weight-dynamics chart goes in as weights_url and runs the full permutation test.