You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People will want to know the 'shape' of X, obsp, varp -- I suspect it will be negative UX if people who are accustomed to getting anndata.X.shape cannot get soma.X.shape()
Effectively the shape of soma.X is (soma.obs.shape()[0], soma.var.shape()[0]) and the shape of soma.raw.X is (soma.obs.shape()[0], soma.raw.var.shape()[0])
What we can do is within the SOMA class:
Pass references to soma.obs and soma.var to the soma.X constructor
.shape()
-- it does not exist (see also.shape
attribute of arrays created withfrom_h5ad
generates error #10)X
,obsp
,varp
-- I suspect it will be negative UX if people who are accustomed to gettinganndata.X.shape
cannot getsoma.X.shape()
soma.X
is(soma.obs.shape()[0], soma.var.shape()[0])
and the shape ofsoma.raw.X
is(soma.obs.shape()[0], soma.raw.var.shape()[0])
soma.obs
andsoma.var
to thesoma.X
constructorX
method called.shape()
which will do what bullet Read API part 1: C++ API query and buffer management libraries #3 above saysNote: On PR #129 we have shape-by-scan which is
O(n)
. For the TileDB core 2.10 timeframe we'll have anO(1)
shape accessor.The text was updated successfully, but these errors were encountered: