Groups
Groups
Sign in
Groups
Groups
cvxpy
Conversations
About
Send feedback
Help
Changes to cvxpy interface
74 views
Skip to first unread message
Steven Diamond
unread,
Aug 11, 2014, 3:12:35 PM
8/11/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cv...@googlegroups.com
I've been contemplating a few changes to the cvxpy interface.
Change semidefinite to Semidefinite for consistency.
Change expr.size to expr.shape for consistency with NumPy. expr.size would then give rows*cols, like in numpy.
Raise DCP errors as soon as a non-DCP expression is formed.
There are a few more that I can't remember right now. I'll add them in later.
Any comments would be appreciated.
Steven Diamond
unread,
Aug 11, 2014, 5:16:50 PM
8/11/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to cv...@googlegroups.com
Also, change the solver statuses OPTIMAL and OPTIMAL_INACCURATE to SOLVED and SOLVED_INACCURATE because OPTIMAL_INACCURATE is kind of an oxymoron.
Reply all
Reply to author
Forward
0 new messages