quadratic objective support about jump.jl HOT 9 CLOSED

On the 2nd point, do you mean we should just having a m.quadObj and m.affObj, and m.quadObj can be nothing?

from jump.jl.

m.quadObj should always be a QuadExpr (but it can have zero terms), and m.affObj should always be an AffExpr.

from jump.jl.

Operator overloads are done, I think. Needs testing to ensure that though.
See notes in QuadExpr test with regards to the issue of Q being symmetric or lower triangular. I guess this can really just be done at the end, but maybe we should cram it into pretty printers. Very low priority.

from jump.jl.

I also renamed some of the fields of QuadExpr to make it less verbose and camel-casey

from jump.jl.

About to tackle point 2

from jump.jl.

Ok, done, I think. Tests pass, but we don't have a quadratic objective test yet!
ba0ba53
Basically, removed objective and quadObj and isObjQuad and just have a single objective field that is a QuadExpr (and thus has an AffExpr in it). From then on was just a matter of replacing isQuadObjs with length checks on quadratic part of objective.

from jump.jl.

Do you want to do point 3? I see you've started on it. If not, I'll do it.

from jump.jl.

Done. All that's left is macro support, but I'm not sure if I'll get to that in the short term.

from jump.jl.

Future work then - I don't think its a priority

from jump.jl.