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

Use of last time step state variables for training #58

Open
dsgoll123 opened this issue Jun 26, 2024 · 1 comment
Open

Use of last time step state variables for training #58

dsgoll123 opened this issue Jun 26, 2024 · 1 comment
Assignees

Comments

@dsgoll123
Copy link
Collaborator

For practical reasons, we use the land surface model state variables from the restart file of ORCHIDEE which records the values for Dec 31st. Such type or restart files are common for land surface models. It would require code modifications to the LSM code to be able to record all state variables in time (e.g. record 365 daily values over a year ). This can easily become a bottleneck for the application of the tool to the various LSM and ORCHIDEE versions.

A shortcoming of this approach is, that the value of Dec 31st might lack information (e.g. state variables with strong seasonality). We believe, the issue might be minor as it is more important for us to predict slowly changing state variables which take long time to spin-up. The other state variables spin-up quickly in the 're-run' land surface model simulation

@ma595 ma595 changed the title use of last time step state variables for training Use of last time step state variables for training Oct 15, 2024
@ma595
Copy link
Collaborator

ma595 commented Oct 16, 2024

@dsgoll123 we need to discuss this in the next developer meeting.

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

3 participants