Conversation
|
Note: I removed the features and bugs headings because I couldn't determine which bugs to include. That made it look like we hadn't fixed any bugs! Hopefully, with imminent, stricter PR guidelines on updating these files as we go, that should not be a problem with future releases. |
There was a problem hiding this comment.
Why have you removed these entries? They are the result of the few PRs that remembered to add entries.
There was a problem hiding this comment.
It's still in the changelog, but because it relates to the tests, i.e it's a developer issue, it doesn't belong in the what's new list.
There was a problem hiding this comment.
I disagree. It is a change to the configuration that directly affect some of our users. The changelog is not part of our built documentation so you can't expect that to be a sufficient route of communication. Let me be clear - changes such as these need to be easy to find. Sysadmins and developers who have custom site.cfg files need to be informed of this change.
There was a problem hiding this comment.
ah, it is there, further down: https://github.com/SciTools/iris/pull/540/files#L1R33
needs to have the new alternative stated too though. will do that now.
|
I quite like the new format of CHANGES, but the short one-liners need some minor tidying. However, the What's New entries are far too brief in my opinion. Bear in mind the people reading this may not be familiar with the context and it's also our opportunity to highlight our achievements over the last few months. Did we really not deprecate anything? |
|
I agree with @esc24 the What's New page should be more detailed. Check out matplotlib's What's New page: http://matplotlib.org/users/whats_new.html, which I think is a nice example. Not every feature needs a huge amount of detail, but they should at least be clear what the feature is for unfamiliar users. |
Ok, will do.
That's not easy to answer just by trawling through the commit history. |
|
I know for sure that the |
|
@bblay it might be worth while searching the code base on Can't help feeling that we should be more strict with ourselves when we add new functionality so that the appropriate whats new files are updated as part of the PR review exit citerion. It might make life easier when it comes to a release. Thoughts ... |
docs/iris/src/whatsnew/1.4.rst
Outdated
There was a problem hiding this comment.
this requires a more in-depth description
There was a problem hiding this comment.
See the PR description #475 ... that might help clarify.
docs/iris/src/whatsnew/1.4.rst
Outdated
There was a problem hiding this comment.
I'd focus on the positive here. This is a big step forward in functionality. I'd also be tempted to combine the two experimental regridding features under a single section. I'll post some suggested text.
There was a problem hiding this comment.
Experimental regridding enhancements
Bilinear and area weighted regridding functions are now available in :mod:iris.experimental.regrid. The final API is still in development, but in the meantime :func:regrid_bilinear_rectilinear_src_and_grid can be used to regrid a cube onto a horizontal grid defined in a different coordinate system. The data values are calculated using bilinear interpolation. :func:regrid_area_weighted_rectilinear_src_and_grid can be used to regrid a cube such that the data values of the resulting cube are calculated using the area weighted mean. Both of these function support masked data and handle derived coordinates such as hybrid height.
|
Deprecations are missing from the changelog. |
docs/iris/src/whatsnew/1.4.rst
Outdated
There was a problem hiding this comment.
um, it means taking all the poetry out! :D
|
CHANGES has a release date, but what's new doesn't. |
There was a problem hiding this comment.
I do not believe this description covers all changes made
|
Checking stuff I was involved with, items seem missing ? (*) No mention of Grib translation extensions - #482.
(*) No mention of ESMPy conservative regridding - #453
|
|
I also think the regridding extensions should be grouped together.
I reckon the comparison would make it clearer what each one does. |
|
Many thanks for taking a look, peeps. 👀 |
Since users might be familiar with the exception that was raised rather than the reasons behind it, it might be worth mentioning the scenario for this. Just a thought really, I wouldnt hold anything back for it! |
If someone can offer a suggested text I'll add it. That quote is gobbledygook 😃 |
|
I suggest: "Cube merging now favours numerical coordinates over string coordinates |
|
👍 |
|
(Perhaps we should merge this and discuss the changelog link elsewhere) |
See https://github.com/SciTools/iris/blob/v1.3.0/lib/iris/_merge.py#L687 I got the wording slightly wrong. Please copy it from the above link. |
|
|
That's not in the trunk: |
|
That's because the fix fixed it. |
docs/iris/src/whatsnew/1.4.rst
Outdated
|
All review actions complete, except the cube merge text because I still can't find the error it refers to. |
docs/iris/src/whatsnew/1.4.rst
Outdated
There was a problem hiding this comment.
Move this "Both ..." up to the top paragraph.
Hehehe, ok, then we can't really say, "These modifications reduce the likelihood of the error: No functional relationship between separable and inseparable candidate dimensions was determined." May we drop this one? |
docs/iris/src/whatsnew/1.4.rst
Outdated
There was a problem hiding this comment.
This returns a cube list. Either use cubes = ... or use load_cube()
OK by me but @cpelley wanted something so I suggest adding "These modifications prevent the error: No functional relationship between separable and inseparable candidate dimensions." |
|
@bblay - I'm done. Please see comments above. |
|
Thanks, I think everything's been addressed. |
|
I'm happy to let it be, I only though that users who were familiar with this message for their case would identify the changes as being relevant to them, but its not important enough to hold this PR for. |
CHANGES
Outdated
|
@cpelley, it made it in: bblay@fe9b83a#L1R144 |
|
(I think you were both right to push for it) |
CHANGES
Outdated
There was a problem hiding this comment.
Change to:
"Improved error message within cube.aggregated_by()"
or similar
|
Thanks for the high quality review work, looking really good now. |
|
👍 |
No description provided.