issues
2 rows where type = "issue" and user = 14925067 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2162954553 | I_kwDOAMm_X86A7BE5 | 8800 | unload python object from memory | agrouaze 14925067 | closed | 0 | 5 | 2024-03-01T09:14:30Z | 2024-03-11T14:38:16Z | 2024-03-11T14:38:15Z | NONE | Is your feature request related to a problem?The problem related to the feature I am looking for is the fact that Describe the solution you'd likeI would like that such snippet gives constant memory footprint: ```python import xarray as xr import numpy as np import psutil import os n_iteration = 20 x = np.arange(6000) y = np.arange(3000) ds = xr.Dataset() def get_memory(): pid = os.getpid() python_process = psutil.Process(pid) memoryUse = ( python_process.memory_info()[0] / 2.0 ** 30 ) # memory use in GB...I think print("memory use:", memoryUse) for n in range(n_iteration): matrix_numpy = np.random.rand(y.size,x.size) ds['var'+str(n)] = xr.DataArray(matrix_numpy,dims=['y','x'],coords={'x':x,'y':y}) # here I don't need this matrix anymore, I just want it to be stored in the xr.Dataset del matrix_numpy # I suppose that the memory should be free, but obviously not... get_memory() print(ds) ``` currently the memory footprint is growing at each iteration:
Describe alternatives you've consideredNo response Additional contextcontext:xarray==2023.11.0 ubuntu 22.04 execution in python (not ipython not notebook) |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/8800/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue | ||||||
924722006 | MDU6SXNzdWU5MjQ3MjIwMDY= | 5491 | rasterio backend not supporting complex_int16 type | agrouaze 14925067 | closed | 0 | 3 | 2021-06-18T09:29:27Z | 2023-02-28T21:48:22Z | 2023-02-28T21:48:21Z | NONE | Dear xarray team,
problem : /home1/datawork/agrouaze/conda_envs2/envs/xsar_gdal3.3_v2/lib/python3.8/site-packages/xarray/backends/rasterio_.py in open_rasterio(filename, parse_coordinates, chunks, cache, lock) 371 attrs[k] = v 372 --> 373 data = indexing.LazilyIndexedArray(RasterioArrayWrapper(manager, lock, vrt_params)) 374 375 # this lets you write arrays loaded with rasterio /home1/datawork/agrouaze/conda_envs2/envs/xsar_gdal3.3_v2/lib/python3.8/site-packages/xarray/backends/rasterio_.py in init(self, manager, lock, vrt_params) 40 if not np.all(np.asarray(dtypes) == dtypes[0]): 41 raise ValueError("All bands should have the same dtype") ---> 42 self._dtype = np.dtype(dtypes[0]) 43 44 @property TypeError: data type 'complex_int16' not understood ``` versions : rasterio == 1.2.4 gdal == 3.3.0 numpy == 1.20.4 xarray == 0.18.2 system : Linux Ubuntu 16.04.7 Python 3.8.10 possible patch in |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5491/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);