-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix bugs with evaluating models that accept no inputs. #3772
Conversation
95c95e9
to
8e1af77
Compare
I now get a problem with
and output is an array. I wonder if these are related. |
… model sets) with array-like output.
Ah, I thought I had that case covered, but it turns out I didn't. I've extended the test to check more possibilities, and fixed the issue. |
that did it! thanks @embray |
it's quite a bit slower than my solution - I'll checkout what is going on. |
Could you quantify that? What exactly is slower and by how much? There's nothing about this change that is at all computationally expensive unless you have some enormous number of outputs. |
@embray nevermind, must have been something on my side! Anyways, thanks a lot this is great and from my side definitely ready to be merged. |
Fix bugs with evaluating models that accept no inputs.
Fix bugs with evaluating models that accept no inputs.
Fixes an issue pointed out by @wkerzendorf, where models with zero inputs did not work. Incidentally the fix is almost exactly the one he put in temporarily. Just fixed it in another case as well.