issues

Table actions

3 rows where state = "closed" and user = 15167171 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: author_association, created_at (date), updated_at (date), closed_at (date)

type 2

state 1

  • closed · 3 ✖

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
129919128 MDU6SXNzdWUxMjk5MTkxMjg= 735 Implement vnorm for xarray with dask support deanpospisil 15167171 closed 0     4 2016-01-30T00:29:40Z 2019-02-28T16:01:39Z 2019-02-28T16:01:39Z NONE      

Similarly to #723 I'd like to see if I can port vnorm from Dask into xarray. This a useful quick operation to have handy for linear models. Previously as I work around I tried: n = da.reduce(np.linalg.norm, ['shapes', 'x'] ) but it quickly explodes (eats up all ram) for large DaskArrays

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/735/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
128687346 MDU6SXNzdWUxMjg2ODczNDY= 723 Implement tensordot for xarray with dask support deanpospisil 15167171 closed 0     8 2016-01-26T00:57:23Z 2016-03-05T00:47:49Z 2016-03-05T00:47:49Z NONE      

I've started using X-ray to store responses from convolutional neural nets over different transformations of images (translation(x,y), rotation (radians), etc). So far its been very intuitive storing and transforming results, unfortunately much of my analysis requires the use of tensor dot products, where I can choose arbitrary dimensions over which to make a projection, or perform a correlation. While dask implements np.tensordot, xray does not.

One can implement a dot product manually by multiplying data arrays then summing over dimensions.

fitm = (da_response*da_model).sum('imageID').sum('x_translation').max('models')

but this ends up being very slow, as I imagine when dot products are implemented by numpy or dask, there is a fair amount of optimization going on.

I am relatively new to GitHub, and this project, would you have any advice on the best way to contribute this functionality? tensordot where in you can put in a list of dimension names in two dataarray over which to compute a sum product, using dasks implementation.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/723/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue
129286220 MDExOlB1bGxSZXF1ZXN0NTc0MzExMjA= 731 Add tensordot to dataarray class also add its test to test_dataarray deanpospisil 15167171 closed 0     19 2016-01-27T22:10:15Z 2016-03-04T06:39:11Z 2016-03-04T05:22:58Z FIRST_TIMER   0 pydata/xarray/pulls/731

Resolving issue #723 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/731/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);