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

Should wis() warn about missing values? #731

Open
nikosbosse opened this issue Mar 23, 2024 · 3 comments
Open

Should wis() warn about missing values? #731

nikosbosse opened this issue Mar 23, 2024 · 3 comments
Labels
question Further information is requested

Comments

@nikosbosse
Copy link
Contributor

Consider the following example:

df <- copy(example_quantile)
df[quantile_level == 0.75, predicted := NA]
df <- df[target_end_date == "2021-05-08" & location == "DE"]

df |>
  as_forecast() |>
  score(metrics = metrics_quantile(select = "wis"))

This just produces a normal output. wis() does have an argument na.rm = TRUE, so in theory all works as expected. But users might not be aware of what happens.

Should wis() (and maybe other functions) warn you if they encounter missing values?

@nikosbosse nikosbosse added the question Further information is requested label Mar 23, 2024
@nikosbosse nikosbosse added this to the scoringutils-2.x milestone Mar 23, 2024
@seabbs
Copy link
Contributor

seabbs commented Mar 23, 2024

Isn't as_forecast handling this?

@nikosbosse
Copy link
Contributor Author

Hmm. Maybe a big part of the answer is just to make the message in as_forecast() not be terrible. I kind of started ignoring the "some NA values get removed" message because the example data always has NA values - so distinguishing one type of NA value from another is maybe helpful.

But since it is the weighted interval score, I think it could also be fine if that function warns if something is unexpected. People might also use it directly and independently of as_forecast()

@seabbs
Copy link
Contributor

seabbs commented Mar 26, 2024

We don't want to set up a situation where score is throwing the same warnings as as_forecast but agree if can be made useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: No status
Development

No branches or pull requests

2 participants