-
Notifications
You must be signed in to change notification settings - Fork 113
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
Improve testing #55
Labels
Comments
tomasaschan
referenced
this issue
Sep 23, 2015
cc @timholy I don't know if this is the best possible solution to the problem, but it does allow us to do things like gradient(itp, dual(2,1)) and get an Array{DualNumbers{Float64},1} back. Before, that incantation would throw an InexactError because it was trying to fit a dual number with nonzero epsilon into an Array{Float64}.
Referencing #24 here too; it should be closed when we fix this. |
@timholy I took the liberty of fleshing out the body of this issue a little :) |
Very good, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(With contributions from @tlycken) There is lots of room for improvement in our test suite. Here are some areas that are in need of improvement:
Colon
indexing withNoInterp
dimensions.Flat
boundary condition really has a gradient tending to 0 toward the boundary.The text was updated successfully, but these errors were encountered: