U Cv f5@sddlmZddlZddlZddlmZmZddl m Z ddl m Z m Z ddlmZmZz ddlZWnek r|dZYnXddd d gZdd d ZdddZddZddZdddZdddZdS)) annotationsN)date_range_like get_date_type) CFTimeIndex)_should_cftime_be_used convert_times)_contains_datetime_like_objectsis_np_datetime_likeZ gregorianZproleptic_gregorianZjulianstandardTcCs\t||d}|dkr:|tkr:||ddd||dd}n||ddd||dd}|jS)zLReturn the number of days in the input year according to the input calendar. use_cftime)r_CALENDARS_WITHOUT_YEAR_ZEROdays)yearcalendarr Z date_type differencer>/tmp/pip-unpacked-wheel-h316xyqg/xarray/coding/calendar_ops.py _days_in_years  rtimec sddlm}||}t|s,td|dt||jj}|krZt|jArZ|S|jj dk rt krtdd|dksdkr|dkrtd |dkrdkrd }| } |d kr6| |d jtd } |fddt|jjj| D|f|d| |<| |tj| |dddi} n@|d krvt|jtddd} | | |<| j| |dd} |dk rt|d} | j|| i|d} | |j|j| |j dd| S)a&Transform a time-indexed Dataset or DataArray to one that uses another calendar. This function only converts the individual timestamps; it does not modify any data except in dropping invalid/surplus dates, or inserting values for missing dates. If the source and target calendars are both from a standard type, only the type of the time array is modified. When converting to a calendar with a leap year from to a calendar without a leap year, the 29th of February will be removed from the array. In the other direction the 29th of February will be missing in the output, unless `missing` is specified, in which case that value is inserted. For conversions involving the `360_day` calendar, see Notes. This method is safe to use with sub-daily data as it doesn't touch the time part of the timestamps. Parameters ---------- obj : DataArray or Dataset Input DataArray or Dataset with a time coordinate of a valid dtype (:py:class:`numpy.datetime64` or :py:class:`cftime.datetime`). calendar : str The target calendar name. dim : str Name of the time coordinate in the input DataArray or Dataset. align_on : {None, 'date', 'year'} Must be specified when either the source or target is a `"360_day"` calendar; ignored otherwise. See Notes. missing : any, optional By default, i.e. if the value is None, this method will simply attempt to convert the dates in the source calendar to the same dates in the target calendar, and drop any of those that are not possible to represent. If a value is provided, a new time coordinate will be created in the target calendar with the same frequency as the original time coordinate; for any dates that are not present in the source, the data will be filled with this value. Note that using this mode requires that the source data have an inferable frequency; for more information see :py:func:`xarray.infer_freq`. For certain frequency, source, and target calendar combinations, this could result in many missing values, see notes. use_cftime : bool, optional Whether to use cftime objects in the output, only used if `calendar` is one of {"proleptic_gregorian", "gregorian" or "standard"}. If True, the new time axis uses cftime objects. If None (default), it uses :py:class:`numpy.datetime64` values if the date range permits it, and :py:class:`cftime.datetime` objects if not. If False, it uses :py:class:`numpy.datetime64` or fails. Returns ------- Copy of source with the time coordinate converted to the target calendar. If `missing` was None (default), invalid dates in the new calendar are dropped, but missing dates are not inserted. If `missing` was given, the new data is reindexed to have a time axis with the same frequency as the source, but in the new calendar; any missing datapoints are filled with `missing`. Notes ----- Passing a value to `missing` is only usable if the source's time coordinate as an inferable frequencies (see :py:func:`~xarray.infer_freq`) and is only appropriate if the target coordinate, generated from this frequency, has dates equivalent to the source. It is usually **not** appropriate to use this mode with: - Period-end frequencies: 'A', 'Y', 'Q' or 'M', in opposition to 'AS' 'YS', 'QS' and 'MS' - Sub-monthly frequencies that do not divide a day evenly: 'W', 'nD' where `n != 1` or 'mH' where 24 % m != 0). If one of the source or target calendars is `"360_day"`, `align_on` must be specified and two options are offered. "year" The dates are translated according to their relative position in the year, ignoring their original month and day information, meaning that the missing/surplus days are added/removed at regular intervals. From a `360_day` to a standard calendar, the output will be missing the following dates (day of year in parentheses): To a leap year: January 31st (31), March 31st (91), June 1st (153), July 31st (213), September 31st (275) and November 30th (335). To a non-leap year: February 6th (36), April 19th (109), July 2nd (183), September 12th (255), November 25th (329). From a standard calendar to a `"360_day"`, the following dates in the source array will be dropped: From a leap year: January 31st (31), April 1st (92), June 1st (153), August 1st (214), September 31st (275), December 1st (336) From a non-leap year: February 6th (37), April 20th (110), July 2nd (183), September 13th (256), November 25th (329) This option is best used on daily and subdaily data. "date" The month/day information is conserved and invalid dates are dropped from the output. This means that when converting from a `"360_day"` to a standard calendar, all 31sts (Jan, March, May, July, August, October and December) will be missing as there is no equivalent dates in the `"360_day"` calendar and the 29th (on non-leap years) and 30th of February will be dropped as there are no equivalent dates in a standard calendar. This option is best used with data on a frequency coarser than daily. r DataArrayz Coordinate z must contain datetime objects.]Source time coordinate contains dates with year 0, which is not supported by target calendar .Z360_dayNzsArgument `align_on` must be specified with either 'date' or 'year' when converting to or from a '360_day' calendar.dater.year)target_calendarr csg|]\}}t||qSr)-_convert_to_new_calendar_with_new_day_of_year).0rZnewdoyrr rr sz$convert_calendar..dimsnameT)Z return_indexrr F)Zraise_on_invalid)Zdropr")Z fill_valuer)!xarray.core.dataarrayrr ValueErrorrdtrr dtyperanyrcopygroupbymap_interpolate_day_of_yearzipvariable_dataarrayZiselnpuniquerdatarwhereZnotnullrZreindexattrsupdatepop) objrdimZalign_onmissingr rrsource_calendaroutZnew_doyZ new_timesZ time_targetrr"rconvert_calendar#s^p      "   r@cCsDt|jjd}|jj}tt||||jjt|||tS)zsReturns the nearest day in the target calendar of the corresponding "decimal year" in the source calendar. r) intr)rrr4roundrZ dayofyearZastype)rrr rr>rrrr/s  r/cCsptj|dd|jd|r|ndd}z*t|||j|j|j|j|j|j|j WSt k rjt j YSXdS)aConvert a datetime object to another calendar with a new day of year. Redefines the day of year (and thus ignores the month and day information from the source datetime). Nanosecond information is lost as cftime.datetime doesn't support it. r days since -01-01r rN) cftimeZnum2daterrmonthdayhourminutesecond microsecondr(r4nan)rZ day_of_yearrr Znew_daterrrr s"    r cs`ddlmp|jjt|jr:|jt|jt dd}fdd}| d |S)aSConvert a datetime DataArray to decimal years according to its calendar or the given one. The decimal year of a timestamp is its year plus its sub-year component converted to the fraction of its year. Ex: '2000-03-01 12:00' is 2000.1653 in a standard calendar, 2000.16301 in a "noleap" or 2000.16806 in a "360_day". rrr )r6csLt|jjd}tj|d|ddd}||t|f|jdS)NrrCZ04drDrE)r%coordsr&)rAr)rrFZdate2numrrN)rrZdoysrrr<rr _make_indexsz._datetime_to_decimal_year.._make_indexr) r'rr)rr r*r,rvaluesrr-r.)timesr<rrPrrOr_datetime_to_decimal_years     rScCsddlm}t|tjtfr,|||f|d}t||r@t|sPtd|d||jj }|jj }||j jj dk r|t krtd|d|}t||||d||<t|||d}|jf||i}|||<|S) awInterpolates a DataArray or Dataset indexed by a time coordinate to another calendar based on decimal year measure. Each timestamp in `source` and `target` are first converted to their decimal year equivalent then `source` is interpolated on the target coordinate. The decimal year of a timestamp is its year plus its sub-year component converted to the fraction of its year. For example "2000-03-01 12:00" is 2000.1653 in a standard calendar or 2000.16301 in a `"noleap"` calendar. This method should only be used when the time (HH:MM:SS) information of time coordinate is not important. Parameters ---------- source: DataArray or Dataset The source data to interpolate; must have a time coordinate of a valid dtype (:py:class:`numpy.datetime64` or :py:class:`cftime.datetime` objects) target: DataArray, DatetimeIndex, or CFTimeIndex The target time coordinate of a valid dtype (np.datetime64 or cftime objects) dim : str The time coordinate name. Return ------ DataArray or Dataset The source interpolated on the decimal years of target, rrr$z Both 'source.z-' and 'target' must contain datetime objects.rr)r<r)r'r isinstancepdZ DatetimeIndexrrr(r)rrrr+rr,rSZinterp)sourcetargetr<rr>rr?Z target_idxrrrinterp_calendar s4    rX)T)rNNN)rN)r) __future__rZnumpyr4ZpandasrUZxarray.coding.cftime_offsetsrrZxarray.coding.cftimeindexrZxarray.coding.timesrrZxarray.core.commonrr rF ImportErrorrrr@r/r rSrXrrrrs4      9