-
Notifications
You must be signed in to change notification settings - Fork 11
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
Incompatibility with Array{Bool} #59
Comments
The main issue with Array{Bool} is they are much slower in our use cases of computing flows, etc (about 4x or sometimes more). I guess one solution is to do the conversion behind the scene for the users. |
Currently these are the assumptions about the data representation: 1/ Complete data
2/ Incomplete data:
It would make sense to take other data formats and convert them to these standards automatically, so that we don't need to support too many cases. |
In v0.4 will be using Matrix{Union{....}} instead of dataframes, will update the docs when that is out. |
Hi,
Juice only accepts
DataFrame
s constructed fromBitArray
s. As far as I know, this is not documented anywhere. Here's a minimal reproducible example:This is because of how Juice optimizes code. Here's the backtrace:
Since
Array{Bool}
does not deal with chunks, Juice crashes. Instead, Juice should either acceptArray{Bool}
or at least convert the offending data into aBitArray
. If we implement #58, we might also want to extend data toArray{Int}
as well.The text was updated successfully, but these errors were encountered: