Skip to content
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

Test tight #25

Merged
merged 2 commits into from Mar 25, 2020
Merged

Test tight #25

merged 2 commits into from Mar 25, 2020

Conversation

nperraud
Copy link
Collaborator

Raise an error if a user define a weighed tight L2 norm function

@nperraud
Copy link
Collaborator Author

closes: #19

add test

updates

fix bug

fix bug

fix lint
@coveralls
Copy link

coveralls commented Mar 25, 2020

Coverage Status

Coverage increased (+0.005%) to 98.597% when pulling 4fa008c on test-tight into 07745c8 on master.

@mdeff
Copy link
Collaborator

mdeff commented Mar 25, 2020

Thanks! Is that applicable to other functions than the l2 norm?

@mdeff mdeff linked an issue Mar 25, 2020 that may be closed by this pull request
@mdeff mdeff self-requested a review March 25, 2020 11:22
@nperraud
Copy link
Collaborator Author

I thought for the l1 norm as well... But eventually I think not. I am not entirely sure. It would take me quite a lot of math and testing to be sure. So I suggest to stop here.

@mdeff
Copy link
Collaborator

mdeff commented Mar 25, 2020

Sure. I'm not even convinced we should try to catch user errors. After all this library is made for users that want control. It is not a black-box optimization tool.

@mdeff mdeff merged commit f69b5db into master Mar 25, 2020
@mdeff mdeff deleted the test-tight branch March 25, 2020 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

weighted norm minimization
3 participants