-
Notifications
You must be signed in to change notification settings - Fork 21
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
error in set_forecast_unit #427
Comments
Thanks for raising this! I solved the issue in #437 which will be live hopefully soon. A quick fix for now is to make sure the input is a data.table (i.e. call (This really stresses the point raised by @seabbs yesterday that we should test everything for compatibility between data.frame and data.table...) |
Thanks for reporting @elray1! @nikosbosse we should PR the fix into main not the Dev version so it's available to users now (as I am aware of at least one other person hitting this) and because it's unrelated to the Dev work. |
…unit Issue #427: Fix error in `set_forecast_unit()` that occurs when input is not a data.table
We fixed this on |
When attempting to call
set_forecast_unit
, I get an error. Here's an illustration with a small subset of the data that I'm working with:I'm working with the version of scoringutils that you get by installing from github.
The text was updated successfully, but these errors were encountered: