# Solve standard continuous relaxation of model in v0.19-alpha

**URL:** <https://discourse.julialang.org/t/solve-standard-continuous-relaxation-of-model-in-v0-19-alpha/17416>\
**Category:** Optimization (Mathematical)\
**Created:** [November 12, 2018, 1:18am UTC](https://discourse.julialang.org/t/solve-standard-continuous-relaxation-of-model-in-v0-19-alpha/17416 "2018-11-12T01:18:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vtjeng](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vtjeng/32/3787_2.png) [@vtjeng](https://discourse.julialang.org/u/vtjeng)\
**Post date:** [November 12, 2018, 1:18am UTC](https://discourse.julialang.org/t/solve-standard-continuous-relaxation-of-model-in-v0-19-alpha/17416/1 "2018-11-12T01:18:07Z")

</div>

JuMP (up to `0.18.4`) allowed you to pass the keyword `relaxation=True` to solve the standard relaxation of a model (for example, onw with integer constraints). [JuMP.jl/NEWS.md at 4b04d34fac5af2494611d972c24095d3ecbc20e8 · jump-dev/JuMP.jl · GitHub](https://github.com/JuliaOpt/JuMP.jl/blob/4b04d34fac5af2494611d972c24095d3ecbc20e8/NEWS.md#version-0110-november-30-2015).

Is it possible to do this in `0.19-alpha` using the `optimize!` function? (Will this be supported some time in the final `0.19` release if it isn’t currently?)

---

<div class="post-metadata">

**Author:** ![miles.lubin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/miles.lubin/32/279_2.png) [@miles.lubin](https://discourse.julialang.org/u/miles.lubin)\
**Post date:** [November 12, 2018, 3:33am UTC](https://discourse.julialang.org/t/solve-standard-continuous-relaxation-of-model-in-v0-19-alpha/17416/2 "2018-11-12T03:33:42Z")

</div>

There’s no one-liner for this anymore. I opened an issue to track the feature request: [Feature request: solve relaxation · Issue #1611 · jump-dev/JuMP.jl · GitHub](https://github.com/JuliaOpt/JuMP.jl/issues/1611). However, I don’t consider it blocking for the 0.19 release.

You can achieve the same result in a generic way by querying all variables from the model ([https://github.com/JuliaOpt/JuMP.jl/issues/1612](https://github.com/JuliaOpt/JuMP.jl/issues/1612)) and manually setting and unsetting integrality constraints (i.e., `is_integer`, `set_integer`, `unset_integer`, `is_binary`, `set_binary`, `unset_binary` around [https://github.com/JuliaOpt/JuMP.jl/blob/10878c9fd513036510c0402e9f01402ca5dc12b1/src/variables.jl#L461](https://github.com/JuliaOpt/JuMP.jl/blob/10878c9fd513036510c0402e9f01402ca5dc12b1/src/variables.jl#L461)).