issue_comments: 76483784

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/pull/337#issuecomment-76483784 https://api.github.com/repos/pydata/xarray/issues/337 76483784 MDEyOklzc3VlQ29tbWVudDc2NDgzNzg0 1217238 2015-02-27T22:22:47Z 2015-02-27T22:22:47Z MEMBER

Should season be listed in the "virtual variables" here: http://xray.readthedocs.org/en/latest/data-structures.html

Good catch

With the addition of the nan-safe functions, numpy is throwing a lot of warnings for things like "empty slices" (ocean grid cells in my example never have data). Its not a big deal to silence them but it is a bit annoying.

To fix this, you can install bottleneck (which will also make these operations much faster). We could also look into silencing the warnings. I'll add a note to the documentation somewhere.

Since ds.groupby('time.season').mean('time') returns a Dataset with a Coordinates variable named time.season, ds.sel(time.season='JJA') doesn't work for Python syntax reasons. So, I don't know if I would change the syntax used in my example (selecting my position). I'm not keen on this constructor: ds.sel(**{'time.season':'JJA'}). I'm wondering if it would be better to name the coordinates returned from "virtual variable" operations without the "time." portion. Just a thought.

This one is trickier. Let me make a new issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   59032389