We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The standard configurations need to be updated for compatibility with the current libaccessom2 master due to changes to the forcing.json format, in particular COSIMA/libaccessom2@a451a7f and COSIMA/libaccessom2@467e3e2 which were made to support ERA5.
forcing.json
Until that is done, executables should be built with libaccessom2 commit 0ab72954, which is the latest commit using the old forcing.json format.
Should probably write a script to automate updating forcing.json to the new format, so it can be applied to user configs.
Even better would be to make libaccessom2 compatible with both the old and new formats.
The text was updated successfully, but these errors were encountered:
Closing this issue.
master
242-era5-support
Sorry, something went wrong.
No branches or pull requests
The standard configurations need to be updated for compatibility with the current libaccessom2 master due to changes to the
forcing.json
format, in particular COSIMA/libaccessom2@a451a7f and COSIMA/libaccessom2@467e3e2 which were made to support ERA5.Until that is done, executables should be built with libaccessom2 commit 0ab72954, which is the latest commit using the old
forcing.json
format.Should probably write a script to automate updating
forcing.json
to the new format, so it can be applied to user configs.Even better would be to make libaccessom2 compatible with both the old and new formats.
The text was updated successfully, but these errors were encountered: