-
Notifications
You must be signed in to change notification settings - Fork 56
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 Test style and coverage #319
Conversation
…rims tests via @info.
…incareBallTVectors
Codecov Report
@@ Coverage Diff @@
## master #319 +/- ##
==========================================
+ Coverage 95.97% 96.86% +0.88%
==========================================
Files 69 69
Lines 4646 4655 +9
==========================================
+ Hits 4459 4509 +50
+ Misses 187 146 -41
Continue to review full report at Codecov.
|
Wow, thanks for working on it. That's a nice cleanup. I will try to find some time to give you some feedback here. |
I wouldn't exclude them but covering them seems like a low priority task.
Sure, we have a good coverage but of course it can be improved 🙂 .
Which default warning?
Sure, we just need a metric group manifold with a non-bi-invariant metric.
I think the whole metric stuff needs a larger rework aimed at addressing #6. IIRC this quantity depends on the selection of a chart so this is somewhat broken now. I think this is perhaps supposed to return this for normal coordinates which is I think well defined but I don't like it anyway.
That looks doable, I'll take a look at it later.
I don't know,
Probably yes but it looks like a very special case.
Sure, I can add that. |
Thanks for the long response. I think we do not have to solve all of my points, for example if the det local metric is not yet finished, there is surely no need to do a test.
Sorry, that I forgot to link something, this one
I did mean, to we have a case where we expect the rethrow so we can check that line? Or can we do that in a one-line instead of with an if? |
No problem, I'll go through other points too 🙂 .
I'd leave it for now.
It can be either tested by providing a custom method for |
There seems to be an actual major problem with projected point distributions (they seem to not work at all). |
These are just some fallbacks that aren't used. Riemannian gradients should work, let me know if there are any problems. You should be able to use them in Manopt.jl. |
Cool, I hopefully find time to check it or write an example about that then. |
I've updated formatting and hopefully fixed the projected distributions. I don't know why they had the decorator dispatch but it seems to only break things. Maybe it would be nice to fix it but |
Thanks for working on that. I hopefully find some time this week to also add a test or two. You can also mark things that we discussed. Are there tests available for the fallbacks of the Riemannian Gradient or do we leave those untested? |
Thanks, I've marked a few things but some are only partially resolved.
I'd vote for merging this PR before any other new work since it touches quite a few files, and any remaining points could be put in an issue. Actually, this PR may be worth splitting into a few PRs with a smaller scope instead of solving here every issue you've listed in the first comment. |
Ok, sure, we can just mark them atop that we will do them later and finish this PR. I just came across making that list since I had rewritten our tests a little bit and an hour left to go through uncovered lines. |
such that the Array variant was never used and never checked/compared.
I think I just did 4 more lines. Can we mark the ones we move in the initial comment (maybe with an X after the box or an -> new PR at the end?) and check the box upfront? |
Maybe let's merge this PR and copy all points that are not checked as done? |
Ok. Would you mind copying those and whereto? An Issue or multiple issues? edit: I just lost track which ones we would resolve where, that's why I am asking. |
Sure, I'll open a new issue. |
…op before the loop)" This reverts commit 6e71c6c.
OK, so can we merge this now? |
In my opinion, yes. |
This PR resolves #259 and
@testset
s are missed and a few nonmutating else-cases,The following is a list of lines where I am not sure how to cover those, but it would be great to have these covered, too.
Sure with our current coverage this is maybe not that necessary, I just would like to have some feedback in them :)
det_local_metric
? For examplePowerdistribution
? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/manifolds/PowerManifold.jl#L191ProductFVectorDistribution
? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/manifolds/ProductManifold.jl#799ProductManifold
s_rand
? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/manifolds/ProductManifold.jl#861Rotations
? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/manifolds/Rotations.jl#L438Rotations
log!
? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/manifolds/Rotations.jl#L504mean_and_var
and how can we get that better? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/statistics.jl#L860ziptuples
,eiogvals
(for static arrays) andeigen_safe
for aStaticMatrix
still needed or are they now part of `StaticArrays in some form? https://codecov.io/gh/JuliaManifolds/Manifolds.jl/src/master/src/utils.jl#L54