-
Couldn't load subscription status.
- Fork 297
Fix conflicts in netcdf var_name #3634
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
base: main
Are you sure you want to change the base?
Conversation
|
?Maybe see also: #3643 |
|
In order to maintain a backlog of relevant PRs, we automatically label them as stale after 500 days of inactivity. If this PR is still important to you, then please comment on this PR and the stale label will be removed. Otherwise this PR will be automatically closed in 28 days time. |
|
I believe this is still worth adding. |
|
In order to maintain a backlog of relevant PRs, we automatically label them as stale after 500 days of inactivity. If this PR is still important to you, then please comment on this PR and the stale label will be removed. Otherwise this PR will be automatically closed in 28 days time. |
|
@stephenworsley fancy updating the branch and we can restart the review process? |
There was a bug when two cubes were being saved where the first cube shared a var_name with a the var_name of a coordinate on the second cube. In such a case, Iris was failing to save. This can be solved by appropriately incrementing the var_name to avoid conflicts in such cases.