# JuMP solver callback arguments

**URL:** <https://discourse.julialang.org/t/jump-solver-callback-arguments/13936>\
**Category:** Optimization (Mathematical)\
**Tags:** jump\
**Created:** [August 23, 2018, 12:49pm UTC](https://discourse.julialang.org/t/jump-solver-callback-arguments/13936 "2018-08-23T12:49:39Z")\
**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:** [August 23, 2018, 10:13pm UTC](https://discourse.julialang.org/t/jump-solver-callback-arguments/13936/2 "2018-08-23T22:13:44Z")

</div>

Hi @Zacharie_ALES,

Can you provide a small working example of your code and what you are trying to achieve? It is much easier to offer specific advice than answer general questions.

You should also note that solver independent callbacks are going away in JuMP 0.19. Instead, JuMP will enable solver-specific callbacks that allow a much lower-level of control over the callback process. See:

> [@Cutting plane algorithm performance varies with Gurobi and CPLEX](https://discourse.julialang.org/t/cutting-plane-algorithm-performance-varies-with-gurobi-and-cplex/8597/2):
>
> Callbacks are tied in very deeply to how a MIP solver works, and they’re just not the same across solvers. (This took some experience to discover.) In JuMP 0.19 we will no longer be providing solver-independent callbacks for this reason; they create a false expectation that you can abstract away the solver when you implement the callbacks. The replacement will be solver-specific callbacks that expose the same interface as the low-level API.

You can also search old discourse posts for callback related questions. [Search results for 'jump callback' - Julia Programming Language](https://discourse.julialang.org/search?q=jump%20callback)

---

_[View the full topic](https://discourse.julialang.org/t/jump-solver-callback-arguments/13936)._