-
Notifications
You must be signed in to change notification settings - Fork 40
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 mean pixel value causes Numba type error #234
Comments
Haha, well, shit. 😂 I'm on a bit of a conference tour for the next 4 weeks so I'm not 100% if I'll be able to fix quickly, but I'd be happy to quickly merge a fix and push a 0.12.1 tag. Looking at the error my guess is that on some systems |
Thanks @jni Gave the Spent a bit more time looking through and understanding the workflow though and think I've found the problem which was that Thanks for the pointer and enjoy the conference season. 👍 |
Thanks for the new release @jni 😄
Unfortunately I've found a problem with a type error being raised from within Numba stemming from initalising the
csr.Skeleton()
class inskan-0.12.0
.Traceback
The traceback is...
git bisect
I don't see this error with
skan-0.11.1
and so to investigate I undertookgit bisect
betweenv0.12.0
andv0.11.1
. To check each bisection I ran the test that is failing from the TopoStatsmain
branch.The error is different from that reported by
v0.12.0
though......and sure enough if I checkout
csr_to_nbgraph()
the only parameters it has arecsr
andnode_props
and ooking at this commit the only change tosrc/skan/csr.py
is...NBGraph()
csr.csr_to_nbgraph()
returnsNBGraph
which is anumba.experimental.jitclass()
withcsr_spec_float
...I thought perhaps the
numba.float64
types were the problem but looking at the numba documentation on types shows thatfloat64
anddouble
are equivalent. Regardless I tried switchingnumba.float64
>numba.double
but still get theTypeError: Can only insert double* at [4] in {i8*, i8*, i64, i64, double*, [1 x i64], [1 x i64]}: got float*
.Current installed packages...
A cleaner environment can be found in a failed GitHub workflow of the tests which failed.
I looked at the versions of
skan
/numba
/llvmlite
/scipy
/numpy
and checked whether they were passing...Not sure how to continue investigating this but please let me know if there is any more information I can provide or try/do.
The text was updated successfully, but these errors were encountered: