Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback for the user when using the FORECASTING UDF #1257

Closed
2 tasks done
americast opened this issue Oct 5, 2023 · 0 comments · Fixed by #1258
Closed
2 tasks done

Feedback for the user when using the FORECASTING UDF #1257

americast opened this issue Oct 5, 2023 · 0 comments · Fixed by #1258
Assignees
Labels

Comments

@americast
Copy link
Member

Search before asking

  • I have searched the EvaDB issues and found no similar feature requests.

Description

We provide a whole bunch of options to the user when creating the FORECASTING UDF, however, it might not be trivial to realize which options would work the best. It would be great if feedback could be provided when a UDF is called and performs subpar.

Use case

Users using the FORECASTING UDF and having complicated datasets.

Are you willing to submit a PR?

  • Yes I'd like to help by submitting a PR!
@americast americast self-assigned this Oct 5, 2023
@americast americast added this to the Long Term Goal milestone Oct 5, 2023
xzdandy added a commit that referenced this issue Nov 16, 2023
Provide feedback when `Forecasting` UDF is called in the following ways:

- [x] Reporting confidence intervals
- [x] Returning a metric for the forecasting performance.
- [x] Providing suggestions in simple special cases, such as during Flat
predictions.

Eg:
```sql
SELECT HomeForecast();
```

```
SUGGESTION: Predictions are flat. Consider using LIBRARY 'neuralforecast' for more accrate predictions.
```

Partially fixes #1257 and #1243.

---------

Co-authored-by: Andy Xu <xzdandy@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant