-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add test_with_logabsdet_jacobian #2
Conversation
b2bd500
to
08cb10b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO the tests should be simplified and users should just provide a suitable Jacobian function. The implementation seems too complicated to me, and I assume it could still fail for types of x
that are not covered here explicitly.
Codecov Report
@@ Coverage Diff @@
## master #2 +/- ##
============================================
- Coverage 100.00% 84.44% -15.56%
============================================
Files 1 2 +1
Lines 31 45 +14
============================================
+ Hits 31 38 +7
- Misses 0 7 +7
Continue to review full report at Codecov.
|
Yes, simpler and more lightweight now with the optional |
Fine with you like this, @devmotion ? |
I think it's still too confusing, I don't get what exactly one has to do even after reading the code and the docstring multiple times 😄 Can't we just drop the back stuff completely and let users just specify a function that computes the Jacobian returned by (BTW the AD vector + |
All right, you win. :-) How about now?
Oh, right! Yes, it really think it's a fundamental thing, I think (hence JuliaGaussianProcesses/ParameterHandling.jl#43). |
b744a19
to
cabe46d
Compare
Ok, doctests for example are in too now. Good with you, @devmotion ? If so, would release a v0.1.1 based on this and then prepare a PR on LogExpFunctions to support InverseFunctions and ChangesOfVariables. |
No description provided.