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.

Sign up for GitHub

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

Jump to bottom

Decide on default functionality and engines that are part of "core" tulip #39

Closed
murrayrm opened this issue Oct 2, 2014 · 0 comments
Closed

Decide on default functionality and engines that are part of "core" tulip #39

murrayrm opened this issue Oct 2, 2014 · 0 comments
Labels
invalid

Comments

@murrayrm
Copy link
Member

murrayrm commented Oct 2, 2014

We need to sort out what tulip should do "out of the box". Things like whether we use jtlv and gr1c, how to deal with cvxopt, etc. There are a couple of issues related to this; please add some comments on this here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@murrayrm @slivingston