pull_requests: 1673012286
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1673012286 | PR_kwDOAMm_X85juCQ- | 8603 | closed | 0 | Convert 360_day calendars by choosing random dates to drop or add | 20629530 | <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Small PR to add a new "method" to convert to and from 360_day calendars. The current two methods (chosen with the `align_on` keyword) will always remove or add the same day-of-year for all years of the same length. This new option will randomly chose the days, one for each fifth of the year (72-days period). It emulates the method of the LOCA datasets (see [web page](https://loca.ucsd.edu/loca-calendar/) and [article](https://journals.ametsoc.org/view/journals/hydr/15/6/jhm-d-14-0082_1.xml) ). February 29th is always removed/added when the source/target is a leap year. I copied the implementation from xclim (which I wrote), [see code here](https://github.com/Ouranosinc/xclim/blob/fb29b8a8e400c7d8aaf4e1233a6b37a300126257/xclim/core/calendar.py#L112-L134) . | 2024-01-10T19:13:31Z | 2024-04-16T14:53:42Z | 2024-04-16T14:53:42Z | 2024-04-16T14:53:42Z | 239309f881ba0d7e02280147bc443e6e286e6a63 | 0 | b581e1f700382207c3bd0fd03860f44f33b29b79 | b004af5174a4b0e32519df792a4f625d5548a9f0 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/8603 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests