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

Todo before releasing 0.1 #49

Closed
5 tasks done
IainNZ opened this issue Feb 16, 2015 · 5 comments
Closed
5 tasks done

Todo before releasing 0.1 #49

IainNZ opened this issue Feb 16, 2015 · 5 comments

Comments

@IainNZ
Copy link
Owner

IainNZ commented Feb 16, 2015

@vgupta1

Target release for Wednesday, recitation is Friday.

  • Finish off docs (http://iainnz.github.io/JuMPeR.jl/) - just need ellipsoidal constraints, and oracle syntax
  • Re-consider how oracles are attached to constraints, given we use macros everywhere
  • Tag JuMP v0.8 so can use new print/solve hooks to kill printRobust/solveRobust
  • Also address callback deprecation warnings
  • Go through tests again
@vgupta1
Copy link
Collaborator

vgupta1 commented Feb 16, 2015

Awesome. Is there anything I can help with on this list? What do you think needs doing right now on DDUS.jl? I'd think:

  • Clean up the read me.
  • Add more examples. Suggestions on what to add here are welcome/appreciated.

Is there anything you think I'm missing?

@IainNZ
Copy link
Owner Author

IainNZ commented Feb 16, 2015

DDUs is looking pretty good, documentation of the arguments to each oracle is the most important thing, caveats and guides to usage.

@vgupta1
Copy link
Collaborator

vgupta1 commented Feb 16, 2015

Would you stick that documentation in the read me or else in source code?

On Mon Feb 16 2015 at 10:02:18 AM Iain Dunning notifications@github.com
wrote:

DDUs is looking pretty good, documentation of the arguments to each oracle
is the most important thing, caveats and guides to usage.


Reply to this email directly or view it on GitHub
#49 (comment).

@IainNZ
Copy link
Owner Author

IainNZ commented Feb 16, 2015

I think either is fine, as long as its clear from the README where to look.

@IainNZ
Copy link
Owner Author

IainNZ commented Feb 18, 2015

Punting on per-constraint oracle syntax until its needed.

@IainNZ IainNZ closed this as completed Feb 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants