-
-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow uint32 dtype for coords #249
Comments
Hey!
Thanks!
Unfortunately, we'd love to. In the past, we converted After going through the "whack-a-mole" process of squashing bugs left and right, I just decided to make it If there was a coordinated effort to examine each line of code that assigns to |
However, if we work on #125 or something along those lines, that'd solve your issues, to my understanding, as it has better compression efficiency in the majority of cases. |
I've found myself wanting
Could you link to the commit where you removed this, and to some of the issues? |
Hey awesome library! I'm really having a blast with it.
One question / comment:
For my purposes, I need the COO array with the largest dtype for
coords
ofuint32
.When I create an array, the COO constructor seems to convert all coord arrays to
intp
orint64
in my case.https://github.com/pydata/sparse/blob/master/sparse/coo/core.py#L234
Any thoughts on skipping that
astype
if coords is already an array?The text was updated successfully, but these errors were encountered: