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

Update MEPS npy example #75

Open
leifdenby opened this issue Sep 12, 2024 · 1 comment
Open

Update MEPS npy example #75

leifdenby opened this issue Sep 12, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@leifdenby
Copy link
Member

I am just writing some notes here with suggestions for what could be done to update the MEPS Npy example:

@sadamov
Copy link
Collaborator

sadamov commented Dec 10, 2024

Since we already have this issue here, I am adding the point that we wanted to make sure that the timesteps covered by this test-datastore match the danra test-datastore.
currently the time-coverage is:

  • danra: 1990-09-03T00:00 - 1990-09-09T00:00
  • meps: 2022-04-01 - 2022-09-15 (with gaps)

It would be fantastic to have both datasets cover roughly the same time-period (can be identical for train/val/test). For danra you could keep the same time-steps.
For meps very few analysis-time steps are required, because the slicing happens along elapsed_forecast_period . So I would say 10 analysis_times, maybe.

@sadamov sadamov added this to the v 0.4.0 (proposed) milestone Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants