Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

Our evaluation agent draws charts, but never writes the numbers

说明与用途

Rhesis 的 Architect 现在生成图表时不再复制原始数字,而是向模型提供查询和简洁摘要,避免错误和误导性可视化。

问题

LLMs can choose appropriate chart types but struggle to accurately reproduce large numeric tables, leading to misleading or incorrect chart outputs.

结果

The new design separates chart generation from data provision, enabling accurate, non‑misleading visualizations while keeping the model focused on question formulation and narrative.

工作流

  • 1. Agent calls show_chart with a query JSON specifying entity, group_by, measures, order_by, limit, min_count, chart_type, title, x, y, target, and focus.
  • 2. The tool validates the request against allowed dimensions and measures, rejecting invalid calls with guidance.
  • 3. The tool runs the query through the insights API using the user’s credentials.
  • 4. The tool builds a chart spec from up to 200 returned rows and attaches it to the reply.
  • 5. The tool generates a short text summary of labels and values for the model to reference.
  • 6. The frontend renders the chart spec with @mui/x-charts and provides toggles for exact numbers and export options.
  • 7. The agent’s final reply includes the chart and a narrative that references the summary, avoiding tables of raw numbers.

证据

The model decides what to chart. It never supplies the numbers.

来源

The tool then: 1. Checks the request before running anything. 2. Runs the query through the same insights API behind the dashboard, using the user's own credentials. 3. Builds the chart spec from the rows that come back, capped at 200 rows, and attaches it to the reply. 4. Gives the model a short text summary.

来源

The frontend renders the spec with @mui/x-charts: line, area, bar, horizontal bar, stacked bar, scatter, radar, a shaded table for two-way breakdowns, and a single headline number.

来源

  • 记录日期: 2026-11-02T14:14:02.019Z