issue_comments: 137478562
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/557#issuecomment-137478562 | https://api.github.com/repos/pydata/xarray/issues/557 | 137478562 | MDEyOklzc3VlQ29tbWVudDEzNzQ3ODU2Mg== | 6883049 | 2015-09-03T15:05:35Z | 2015-09-04T09:49:54Z | CONTRIBUTOR | I agree with your arguments against creating too many datetime specific methods. However, I am not convinced about using .sel with 'time.year', it looks a bit hackish to me. Maybe all "CDO methods" can be integrated in one single "seltimes" method. Please look at the function below. The time_coord arguments lets you choose the time coordinate that you want to filter, and by using numpy.logical_and is it possible to do the whole operation in one single function call. It could be turned into a method. What do you think? ``` python %matplotlib inline import xray import numpy as np from matplotlib import pyplot as plt ifile = "HadCRUT.4.3.0.0.median.nc" ixd = xray.open_dataset(ifile) ``` You can download the example file from here http://www.metoffice.gov.uk/hadobs/hadcrut4/data/4.3.0.0/gridded_fields/HadCRUT.4.3.0.0.median_netcdf.zip Now comes the function. ``` python def seltime(ixd, time_coord, **kwargs): """ Select time steps by groups of years, months, etc.
``` It works, and it looks fast enough.
``` 1000 loops, best of 3: 1.05 ms per loop
``` If we average in time we can see the warm tonge in the pacific.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
104484316 |