-
Notifications
You must be signed in to change notification settings - Fork 26
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
weighted norm minimization #19
Comments
Yes this has been tested here: pyunlocbox/pyunlocbox/tests/test_functions.py Line 116 in d0bd39b
I have added some test in the norm_l1 and did not found any bugs... See this PR: #21 |
Thanks for your response but the error still persists. Suppose A is M*N (where M>N) and consequently x dim would be Nx1 and w&y are Mx1. In this case: from the first line sol is Nx1 and in the second line, sol is going to be divide by w which is Mx1. And that is why I get dimension error. |
Could you simply make a simple example with an error? |
https://user-images.githubusercontent.com/61758751/75893435-cbc64100-5e00-11ea-93f4-f3ffdb82c405.JPG This is an error for norm_l2 and tight=True. |
Please copy the code here so I can try it. It is more efficient thant recopying everything from your image.
|
|
Sorry for my late reply. I was able to reproduce the problem. One thing that see is that you are using tight=True, which is not correct in your example. Indeed A is not a tight operator. If ignore this, the proximal solution for a tight operator requires a constant weight to be valid. Hence, if tight=True, then w should be a scalar. To solve this problem, you can simply set tight=False in your code. i will add a check for this in the code such that one cannot define a function with multiple weights and a tight operator. |
I have a problem with using weighted-l2. In fact, according to the docs, the dimension of w should be the same as the dimension of y while I get a dimension error. I need to know whether you have tried the weighted ones. The error is exactly in the same part as it is mentioned:
Nati: I've checked this code the use of 'y' seems correct
The text was updated successfully, but these errors were encountered: