GithubHelp home page GithubHelp logo

Comments (6)

sayanpatra avatar sayanpatra commented on July 20, 2024

Hi,

Can you post your code please so that we can reproduce it?

from greykite.

dromare avatar dromare commented on July 20, 2024

Hi sayanpatra,

I believe this issue can be considered a duplicate of issue #43, which is still open. The basic question is: how can we control the amount of metrics being computed rather than forcibly suppress useful warnings which are there to show us what may be going wrong ?

  • The two warnings about y_true (MAPE and medAPE are undefined) most probably refer to the train period, because that is where my response has some zero values (no zero values in the forecast period)
  • The warning about y_pred, instead, can either refer to the train period or the forecast period ( because this particular model fits the intercept term, which also becomes the forecast)

I know that my response may contain zeros values, hence I would like to prevent the algorithm from calculating an undefined MAPE rather than letting it go ahead and throw a warning. Similarly, I am not interested in the correlation calculation, so I would like the algorithm to be spared that task and effort too.

from greykite.

sayanpatra avatar sayanpatra commented on July 20, 2024

When you pass cv_selection_metric as None in EvaluationMetricParam, it computes a default set of metrics. I believe you will not get those error messages if you add the RMSE as the evaluation metric as follows:

from linkedin.greykite.common.evaluation import EvaluationMetricEnum

evaluation_metric = EvaluationMetricParam(
    cv_selection_metric=EvaluationMetricEnum.RootMeanSquaredError.name
)

config = ForecastConfig(
metadata_param=metadata,
...,
evaluation_metric_param=evaluation_metric
)

from greykite.

dromare avatar dromare commented on July 20, 2024

I did as you said but I am still getting MAPE and MedAPE messages, whether I use the RMSE or the MAE metric (MAE metric in screenshot below)
Capture5
:

from greykite.

sayanpatra avatar sayanpatra commented on July 20, 2024

I can not respond based on partial code. As I said before if you need help, post your full code.

from greykite.

dromare avatar dromare commented on July 20, 2024

I found out that these warnings come from the error metrics on the forecast results (and the backtest results if test_horizon > 0):
image

result.forecast.train_evaluation
result.forecast.test_evaluation
result.backtest.train_evaluation
result.backtest.test_evaluation

from greykite.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.