Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Forecast skill #431

ecomodeller started this conversation in Ideas
Mar 21, 2024 · 2 comments · 4 replies
Discussion options

ModelSkill already supports forecast skill thanks to flexible grouping on aux variables.

image

Is there anyting else we need to streamline forecast skill?

  • Data handling, what is the best format to preserve necessary metadata, e.g. time of forecast
You must be logged in to vote

Replies: 2 comments 4 replies

Comment options

  • Forecast data file structure: It would be good if it was possible to extract forecast times series directly from the BlueCast dfsu forecast files named H12, B1 and B2. (And also use dfs0 files with the same naming convention.)
  • Hitrate with a given "deviation" is an accepted accuracy measure by forecast clients. As it is already a part of ModelSkill I guess that it will automatically be a part of ForecastSkill.
You must be logged in to vote
3 replies
Comment options

ecomodeller Apr 3, 2024
Maintainer Author

To be able to calculate lead time, we need the time of forecast in addition to the valid time (available in dfs{u,0}) files).

Since dfs files lacks support for arbitrary metadata, we can not encode time of forecast into the file, so this information has to be supplied to modelskill in some other way, csv?

time_of_forecast filename
2024年04月01日 18:12:12 foo_B1.dfsu
2024年04月01日 18:12:12 foo_B2.dfsu
Comment options

The "basetime" of the forecast (when the forecast cycle starts, not when the content of the file starts) is already a part of the file name, so should be available.

Comment options

attrs?

Comment options

Is the skill() method able to handle multiple models and aux_items?

I was trying to write a simple example and I noticed this:

image

Notice that I could either compute the skill by model or by aux (lead_time), but not both. Am I doing something wrong?

You must be logged in to vote
1 reply
Comment options

jpalm3r Jun 14, 2024
Collaborator

I have talked with @jsmariegaard and we have figured out how to do it: it was just a matter of writing cmp.skill(by = ["model", "lead_time"]).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /