-
Notifications
You must be signed in to change notification settings - Fork 49
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
Three minor bugfixes for data_config.yaml workflow #40
Conversation
While you are doing this I thought of something else with the config: Shouldn't |
Hmm, the dataset.var_names are of the state not of the forcings though.
Note, that currently the forcings are calculate in parts in the dataset and in otherparts loaded from .npy files. |
Ah yes, of course you're right! But but isn't Also, I really like your suggestion about introducing a |
the forcings should be =16
|
neural-lam/neural_lam/config.py Line 51 in 5b71be3
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good fixes, just a small thing about the dict argument.
The coords_projection problem was fixed by merging #17, so merged main in here so we don't see that change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good now, tested and it works!
Did not add explicitly to changelog as these are only fixes to #23 |
Summary
#31 introduced three minor bugs that are fixed with this PR:
()
)data_config.yaml
var_leads_metrics_watch