# Odd behavior from ControlSystemIdentification and JuMP on version 1.6

**URL:** <https://discourse.julialang.org/t/odd-behavior-from-controlsystemidentification-and-jump-on-version-1-6/58714>\
**Category:** Optimization (Mathematical)\
**Tags:** control, potential-bug\
**Created:** [April 6, 2021, 8:15pm UTC](https://discourse.julialang.org/t/odd-behavior-from-controlsystemidentification-and-jump-on-version-1-6/58714 "2021-04-06T20:15:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![odow](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/odow/32/28685_2.png) [@odow](https://discourse.julialang.org/u/odow)\
**Post date:** [April 6, 2021, 8:49pm UTC](https://discourse.julialang.org/t/odd-behavior-from-controlsystemidentification-and-jump-on-version-1-6/58714/2 "2021-04-06T20:49:24Z")

</div>

Does the optimize call finish at all? Does it work if you use less packages? (e.g., what about just JuMP, GLPK, and ControlSystemIdentification?)

I’m guessing this is a bad case of method invalidation: [Analyzing sources of compiler latency in Julia: method invalidations](https://julialang.org/blog/2020/08/invalidations/)

---

_[View the full topic](https://discourse.julialang.org/t/odd-behavior-from-controlsystemidentification-and-jump-on-version-1-6/58714)._
