-
Notifications
You must be signed in to change notification settings - Fork 92
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Geodesic surface_direction scales index offsets by degrees, ignoring meridian convergence
area:surfaceArea: surfaceArea: surfacebugSomething isn't workingSomething isn't workingseverity:mediumSweep finding: MEDIUMSweep finding: MEDIUMsweep-accuracyFound by /sweep-accuracyFound by /sweep-accuracyStatus: Open.#3733 In xarray-contrib/xarray-spatial;- Status: Open.#3726 In xarray-contrib/xarray-spatial;
surface_distance tests never touch dask+cupy and only call surface_direction on numpy
area:surfaceArea: surfaceArea: surfaceseverity:highSweep finding: HIGHSweep finding: HIGHtestsTest coverage and parityTest coverage and parityStatus: Open.#3725 In xarray-contrib/xarray-spatial;surface_distance Dijkstra heap is sized height*width and overflows on dense target rasters, corrupting memory
area:proximityArea: proximityArea: proximitybugSomething isn't workingSomething isn't workingdaskDask backend / chunked arraysDask backend / chunked arraysoomOut-of-memory risk with large datasetsOut-of-memory risk with large datasetsperformancePR touches performance-sensitive codePR touches performance-sensitive codeseverity:criticalSweep finding: CRITICALSweep finding: CRITICALsweep-performanceFound by /sweep-performanceFound by /sweep-performanceStatus: Open.#3723 In xarray-contrib/xarray-spatial;surface_distance(): the Dijkstra heap is sized H*W, so dense source rasters write out of bounds and abort the process
bugSomething isn't workingSomething isn't workingStatus: Open.#3722 In xarray-contrib/xarray-spatial;cupy surface_distance stops relaxing after H+W passes and reports reachable pixels as NaN
area:surfaceArea: surfaceArea: surfacebugSomething isn't workingSomething isn't workinggpuCuPy / CUDA GPU supportCuPy / CUDA GPU supportseverity:highSweep finding: HIGHSweep finding: HIGHsweep-accuracyFound by /sweep-accuracyFound by /sweep-accuracyStatus: Open.#3721 In xarray-contrib/xarray-spatial;surface_distance/allocation/direction docstrings have no examples, no backend statement, and no geodesic caveat
area:surfaceArea: surfaceArea: surfacedocumentationImprovements or additions to documentationImprovements or additions to documentationseverity:mediumSweep finding: MEDIUMSweep finding: MEDIUMStatus: Open.#3714 In xarray-contrib/xarray-spatial;surface_direction() returns wrong bearings on dask rasters: block-local pixel indices subtracted from global source indices
area:surfaceArea: surfaceArea: surfacebugSomething isn't workingSomething isn't workingdaskDask backend / chunked arraysDask backend / chunked arraysseverity:highSweep finding: HIGHSweep finding: HIGHStatus: Open.#3713 In xarray-contrib/xarray-spatial;surface_distance trio rejects target_values=None while proximity, allocation, direction and cost_distance accept it
apiAPI design and consistencyAPI design and consistencyarea:surfaceArea: surfaceArea: surfacebugSomething isn't workingSomething isn't workingseverity:mediumSweep finding: MEDIUMSweep finding: MEDIUMsweep-api-consistencyFound by /sweep-api-consistencyFound by /sweep-api-consistencyStatus: Open.#3712 In xarray-contrib/xarray-spatial;- Status: Open.#3710 In xarray-contrib/xarray-spatial;
benchmarks: cupy branch in get_xr_dataarray never raises NotImplementedError on non-GPU hosts
bugSomething isn't workingSomething isn't workingStatus: Open.#3707 In xarray-contrib/xarray-spatial;Proposal: spatial-transcriptomics adapter + Visium proof-of-concept
proposalIdea that needs design discussionIdea that needs design discussionStatus: Open.#3688 In xarray-contrib/xarray-spatial;