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

Forcing NeuralGCM with monthly mean data #137

Open
smhenry2 opened this issue Oct 30, 2024 · 2 comments
Open

Forcing NeuralGCM with monthly mean data #137

smhenry2 opened this issue Oct 30, 2024 · 2 comments

Comments

@smhenry2
Copy link

From the NeuralGCM documentation, "all_forcings" uses the function "forcings_from_xarray" for all ERA5 data to create the forcings. It is stated that “ERA5’s sea surface temperature and sea ice concentration variables exclude the diurnal cycle and are updated only about once daily, so passing in hourly forcings is unnecessary”. I am interested to know 1) how the SST and sea ice data are updated by NeuralGCM when using a theoretical monthly forcing data, and 2) how to pass monthly mean data as forcings given that the number of days varies between months. Could the authors provide more information? Thanks.

@yaniyuval
Copy link
Contributor

Hi @smhenry2 ,
I am not sure I fully understand your questions.

@smhenry2
Copy link
Author

smhenry2 commented Nov 8, 2024

Hi @smhenry2 , I am not sure I fully understand your questions.

Hello @yaniyuval,
To clarify, I would like to know how to best force NeuralGCM with forcing data of a different time resolution than model output time resolution for a dynamic forcing. For instance, in the demo Jupyter Notebook, both the ERA5 forcing data and the prediction output are of time resolution 24h. How could dynamic forcing be used to force NeuralGCM with weekly or monthly data while maintaining 24 hourly output data, and how might that impact the predictions? Sorry if my initial question was not clear enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants