-
Notifications
You must be signed in to change notification settings - Fork 25
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
calculate diamond norm using dual problem #54
Conversation
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.
Test for diamond distance symmetry should be added to the test/convex.jl
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.
Shouldn't it be simply Z in :SDP
instead of Z+Z' in :SDP
? Except fixing a bug, which I cannot reproduce, does the dual problem have advantages over the primal one? Better numerical performance?
I took inspiration from qetlab where they have the similar line
I also did notice some instability with just I was just playing with primal & dual formulation, and found that the dual one didn't have the buggy behaviour of #53 . Not sure if it has other advantages. |
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.
I think we should keep both versions, norm_diamond
should take an optional parameter likedual=false
setting which approach is used.
I agree that we should keep both versions. We should also force the correct |
After some tests on this problem anything higher causes to hit |
Ok. Does it make sense then do add |
Yes, the user should be able to set |
In the new commit I added a test from #53 and implemented both the primal and dual problem with optional argument |
We should have |
I have implemented the 'julianeque' notation with |
This implements the same algorithm of QETLAB, first discussed in this paper, section 3
Fix #53