# About JuMP.is\_solved\_and\_feasible

**URL:** <https://discourse.julialang.org/t/about-jump-is-solved-and-feasible/126868>\
**Category:** Optimization (Mathematical)\
**Tags:** jump\
**Created:** [March 12, 2025, 12:36pm UTC](https://discourse.julialang.org/t/about-jump-is-solved-and-feasible/126868 "2025-03-12T12:36:15Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![WalterMadelim](https://avatars.discourse-cdn.com/v4/letter/w/3e96dc/32.png) [@WalterMadelim](https://discourse.julialang.org/u/WalterMadelim)\
**Post date:** [March 13, 2025, 4:43am UTC](https://discourse.julialang.org/t/about-jump-is-solved-and-feasible/126868/9 "2025-03-13T04:43:30Z")

</div>

I find that JuMP already has part of this nice warning Error message integrated in quering functions, just as the following.

```julia
import JuMP, Ipopt
model = JuMP.Model(Ipopt.Optimizer)
JuMP.@variable(model, x >= 1)
JuMP.@objective(model, Min, x)
JuMP.optimize!(model)
JuMP.objective_bound(model) # The following ERROR is approving 👍
# ERROR: MathOptInterface.GetAttributeNotAllowed

```

Which embodies the idea mentioned by my post above

```julia
function improved_value(model) # in place of the existing `JuMP.value`
    if normality
        return JuMP.value(model) # returns the existing API 
    else
        error("Sorry, this info is unavailable or invalid!")
    end
end

```

In view of this, the `JuMP.objective_bound(CR) # 1.0e100` is weird here ([Gurobi12 reports obj\_value \< obj\_bound in a Min-Program?](https://discourse.julialang.org/t/gurobi12-reports-obj-value-obj-bound-in-a-min-program/126849)), which doesn’t make any sense.  
The expected behavior is also an ERROR message. Do you agree? @odow

---

_[View the full topic](https://discourse.julialang.org/t/about-jump-is-solved-and-feasible/126868)._