DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to chart a forecast with its prediction interval with Chronos Forecasting

Plot history, ground truth and the Chronos-2 forecast band to see where the model is confident.

Short answer: Install the package with pip install chronos-forecasting and matplotlib as the README notes; then Produce pred_df with pipeline.predict_df and quantile_levels of 0.1, 0.5 and 0.9; Plot the last part of the history, the ground truth and pred_df["predictions"] as the README example does. All steps.

Who it is forAnyone who has to show a forecast to other people.

The problemA table of quantiles does not tell you whether the forecast is sensible.

The outcomeA chart with the history, the forecast and a shaded prediction interval.

What you need first

  • Python with pip and `pip install chronos-forecasting`
  • pandas with pyarrow for the DataFrame examples
  • A CUDA GPU for the README example, which sets device_map to cuda

Steps

  1. Install the package with pip install chronos-forecasting and matplotlib as the README notes
  2. Produce pred_df with pipeline.predict_df and quantile_levels of 0.1, 0.5 and 0.9
  3. Plot the last part of the history, the ground truth and pred_df["predictions"] as the README example does
  4. Shade the interval with plt.fill_between across the 0.1 and 0.9 columns

Prompt for your agent

With amazon-science/chronos-forecasting, produce a Chronos-2 forecast for <my series> and save a chart showing history, ground truth and the 10 to 90 percent band.

Caveat. The README plotting example uses a single series; group by id when you have many.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for amazon-science/chronos-forecasting and "Chart a forecast with its prediction interval"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer