Refactor Spatial Averaging: More Robust Handling of Longitude Spanning Prime Meridian #150
Labels
type: bug
Inconsistencies or issues which will cause an issue or problem for users or implementors.
What versions of software are you using?
What are the steps to reproduce this issue?
But the correct value is: 297.150202135895 (Difference of 0.31 K)
I think this can be traced to this line:
domain_bounds
should bedom_bounds
in this case.This will fix the issue in this case, but I realize there are specific situations that will give an (slightly) incorrect solution when the specified regional bounds are within a grid cell that spans across the prime meridian (e.g., -1 to 1).
Any other comments?
This code should be refactored to more robustly deal with averaging along the longitude axis (it needs to robustly handle domain bounds and regional selections that span the prime meridian). An approach I would like to try is to:
The text was updated successfully, but these errors were encountered: