-
Notifications
You must be signed in to change notification settings - Fork 105
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
Bug in prox of l1 norm #1181
Comments
What would be the expected result and why? Edit: I'm stupid, ofc it should be zero. |
BUG: Fix bug with aliased input to l1_cconj proximal, closes #1181
As mentioned above already, replacing f by |
Darn it, you are right. I'll look into it. |
Any news here? Is there a way to write a test that gets run on all functionals (without us writing a new one every time)? |
No update sadly, havn't had time. With that said there is a rather enormous large-scale test here:
it should catch stuff like this, but apparently does not. |
Does it test with aligned input & output? |
Very much looks like it does not. |
BUG: fix in-out aliasing issue in OperatorSum, closes #1181
Well done! This indeed fixed the bug I was observing. |
I just did a similar test with the l1-norm itself and not its conjugate. While the latter is indeed fixed, the former still has the same problem:
|
This example shows a bug in the prox operator of the l1 norm:
results in 0.9. Similar effects can be observed in
KullbackLeibler
but not inL2Norm
.The text was updated successfully, but these errors were encountered: