Closed IainNZ closed 5 years ago
Hi @yeesian and @jackdunnnz. Great to meet you.
As far as priorities go, you can get an idea of what we've been working on by looking at the 0.0.1 milestone. The way SCIP.jl works right now is:
I've mostly been working on the Python bits. @joehuchette put together an MPB interface on top of the raw SCIP function wrappers.
Next, I was going to start adding docs to the Julia code based on the SCIP doc strings. I could really use help with any of the Julia components of the system.
OK, thats very helpful! We probably shouldn't have the XML files checked into the repository though, right?
I've added notes to that effect to the README as well: https://github.com/ryanjoneil/SCIP.jl/blob/master/README.md
Regarding the XML files, no we shouldn't. At the moment they are there for convenience only. You have to generate them from the SCIP source using doxygen, so it's not something we can just download. Long term, they should be taken out.
Excellent. Can you add me as a contributor?
Done
Hey, nice work. If I can do anything, I'd be glad to contribute. I've actually used more of the C++ interface for SCIP, but still.
Hey @sbebo, returning back to this issue, it'll be great if you can contribute! Is there anything we can help you with to get started?
I just saw your blogpost -- we actually have support for MINLP in JuMP right now, but haven't yet gotten round to wrapping some of the other solvers you work with.
So lets get this package wrapped (hah!) up.
I wanted to introduce a new doctoral student in the ORC, @yeesian, who just wrapped KNITRO. We also have @jackdunnnz joining us, he is getting started and is currently the local expert on the NL file format.
I've been out of the loop on this package, so I'm gonna review the situation now. Whats your take on first priorities @ryanjoneil ?