Skip to content

y and yhat from ProphetForecast don't make sense, and are very far apart #270

@rebecca-burwei

Description

@rebecca-burwei

The ProphetForecast writes a components table to BigQuery. The components table has 2 columns called y and yhat. When I query this table in BigQuery, I see the following issues:

  • y and yhat are very far apart, differing by up to 4 orders of magnitude.
  • based on common sense about what these metrics mean, y is wrong. this is concerning because y is supposedly the target data used to train the model.
  • based on how yhat is set, yhat should be list of 1,000 numbers, but in the BigQuery table, there is only 1 number.

Other suspicious things you could try investigating as a way to resolve the 3 issues above:

  • Maybe the wrong aggregation is getting used on y. It's not obvious to me why we'd apply the same aggregations to both y and yhat.
  • This comment sounds like it's doing the wrong thing. What does this sentence even mean? In overlapping periods, the forecasted value will always be larger because it is the sum of the observed and forecasted values.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions