# \[JuMP + Gurobi Bug?\] value of variable in solved model changes after deleting another variable

**URL:** <https://discourse.julialang.org/t/jump-gurobi-bug-value-of-variable-in-solved-model-changes-after-deleting-another-variable/29619>\
**Category:** Optimization (Mathematical)\
**Tags:** jump, bug\
**Created:** [October 7, 2019, 8:31pm UTC](https://discourse.julialang.org/t/jump-gurobi-bug-value-of-variable-in-solved-model-changes-after-deleting-another-variable/29619 "2019-10-07T20:31:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Henrique\_Becker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/henrique_becker/32/15443_2.png) [@Henrique\_Becker](https://discourse.julialang.org/u/Henrique_Becker)\
**Post date:** [October 8, 2019, 10:42pm UTC](https://discourse.julialang.org/t/jump-gurobi-bug-value-of-variable-in-solved-model-changes-after-deleting-another-variable/29619/7 "2019-10-08T22:42:17Z")

</div>

Oh, no, I can work around it. I am thinking of people that will end up  
with the same problem in the future. If there is no plan to support  
deepcopy why do not specialize deepcopy to show an error message and  
abort?

As it is just a stub, I can write it and make a pull request for it  
too. I suppose that the better is to specialize it for the concrete  
class and not the AbstractModel, as someone may want to implement a  
model that supports deepcopy.

I will submit a change to the documentation soon. I just don’t know if  
it is not kinda long considering the size of the issue. Feel free to  
say to me rewrite it.

---

_[View the full topic](https://discourse.julialang.org/t/jump-gurobi-bug-value-of-variable-in-solved-model-changes-after-deleting-another-variable/29619)._