-
Notifications
You must be signed in to change notification settings - Fork 56
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
How could we add precipitation forecast in your neural-lam? #12
Comments
Hi, Some adaptation would also be needed to run for your specific region, but that is not related to modeling precipitation specifically (see #4). |
Hi, we are using hourly precip sums for 2.2km precipitation forecast in our fork: https://github.com/MeteoSwiss/neural-lam. Maybe the zarr-based dataloader for model level data is useful on a technical level. We have a bug in the data-prep (hourly sums are wrongly calculated), so the predictions are off. Still, if you think about adding Precip to your input channels maybe this helps. |
@weatherforecasterwhai Does this answer your question? Can I close the issue? |
Yes, Thank you!
At 2024-03-13 16:05:15, "Joel Oskarsson" ***@***.***> wrote:
@weatherforecasterwhai Does this answer your question? Can I close the issue?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
* Fix mdp datastore to allow for forecast data * Start adapting testing and dataset length checking for boundary forecasts * Work out cropping for forecast boundary * Make test work up to boundary checking * Rework forecast boundary forcing slicing and test * Fix boundary valid time computation and add assert * Fix slicing if da1 ends first * Adjust time stepping when interior and boundary have different time step * Fix bug in step length computation for forecast datastore * Implement loading stats from other datastore * Update neural_lam/weather_dataset.py * Use explicit arguments in init_datastore --------- Co-authored-by: sadamov <45732287+sadamov@users.noreply.github.com>
I've send email to you asking about removing precipitation from GraphCast origional codes,sir.
Thank you for your quick reply. In the email you explained the precipitation part is difficult due to ERA5
precipitation is not accurate enough. So, as in a specific region like China, we got high quelity precipitation
reanalysis data. Maybe, we could use these precipitation data instead of ERA5 precipitation to make the forecast better.
Now, how could we add the precipitation part in your neural-lam codes?
Thank you.
The text was updated successfully, but these errors were encountered: