Closed MaximilianHoffmann closed 3 years ago
This looks like a relatively easy to fix bug. Did you close the issue on purpose ?
Yeah, since I just fixed the input in my code, but it took me some time to find the culprit. I thought this might save someone time.
I imagine very well... I'll reopen the issue and make a fix. Ordering is dealt with by numba so we shouldn't add contraints to it.
Le mar. 30 mars 2021 à 10:25, Maximilian Hoffmann @.***> a écrit :
Yeah, since I just fixed the input in my code, but it took me some time to find the culprit. I thought this might save someone time.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/EconForge/interpolation.py/issues/84#issuecomment-810023414, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACDSKP7JXFJKEMPVF2FF6DTGGDGFANCNFSM4Z6DHEZA .
My old code was broken from this version on since it didn't check that eval_linear needs C-order and dtype FLOAT64 in all its arguments: