Skip to content

Conversation

@hpages
Copy link
Contributor

@hpages hpages commented Jun 18, 2025

nzvals/nzwhich work on any SparseArray derivative (i.e. COO_SparseArray and SVT_SparseArray objects). They even work on dgCMatrix objects and other sparse representations from the Matrix package.

Furthermore, nzdata() and nzcoo() are just accessors for the nzdata and nzcoo slots of a COO_SparseArray object, but these slots are not guaranteed to contain the nonzero values and their index in an order that is consistent with the "first dimension is the fastest moving dimension" convention. OTOH nzvals() and nzwhich() are guaranteed to return the nonzero values and their index in an order that follows this convention. Just a FYI as I don't know if this is relevant in the context of the write_block() method for TileDBRealizationSink objects.

hpages and others added 3 commits June 17, 2025 22:34
nzvals/nzwhich work on any SparseArray derivative (i.e. COO_SparseArray
and SVT_SparseArray objects). They even work on dgCMatrix objects and
other sparse representations from the Matrix package.

Furthermore, nzdata() and nzcoo() are just accessors for the 'nzdata'
and 'nzcoo' slots of a COO_SparseArray object, but these slots are not
guaranteed to contain the nonzero values and their index in an order
that is consistent with the "first dimension is the fastest moving
dimension" convention. OTOH nzvals/nzwhich are guaranteed to return the
nonzero values and their index in an order that follows this convention.
Just a FYI as I don't know if this is relevant in the context of the
write_block() method for TileDBRealizationSink objects.
@LTLA
Copy link
Owner

LTLA commented Jun 19, 2025

LGTM thanks

@LTLA LTLA merged commit 5a6552a into LTLA:master Jun 19, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants