Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Include information about model performance in easier to access format

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by examining the existing data components and the general to_df() output to understand which forecast, observed, detrended, holiday, country, and date values are already available. Compare that structure with the proposed performance_df() option and the listed analysis questions. Done means a consistent DataFrame format exposes the requested absolute and relative comparisons, with its intended scope distinguished from Prophet's performance_metrics.

Written by the indexing model from the issue text.

Description

I think this is something that can be calculated from existing data components, but might not currently be packaged up in one consistent format.

Here were some of the analysis questions I encountered that I could not immediately figure out how to address with the current data structure:

  • Was the effect of X holiday larger or smaller this year than prior year(s)? By how much? (In absolute count and in relative percent)
  • When comparing trends (i.e. across multiple dates), is the gap between forecast and observed growing, shrinking, or staying level?
    • E.g., if a model underestimated holiday impact, do the trends re-converge in the following days or does that gap persist as a step-change?
  • Within each country/population, how far off was the forecast value from the observed value on a given date? (In absolute count and relative percent)
  • What exactly was the impact of holiday(s) on the forecast value for a given date? (In absolute count and relative percent)
    • This may just be the difference between the detrended forecast and the final forecast.
  • What was the estimated impact of holiday(s) on a historical observed value for a given date? (In absolute count and relative percent)
    • This may just be the difference between the detrended amount and the observed amount.

Ideally, this could be included in a simple DataFrame -- either as additional columns in the same general DataFrame output from the general to_df() function, or maybe as a separate dedicated function for performance_df().

(Also acknowledging that this might be different than some other object that stores overall measures of model performance -- things that might come out of Prophet's performance_metrics).

Dominant language
Python
Stars
3
Forks
3
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/mozaic-forecasting

All issues in mozilla/mozaic-forecasting

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.