Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Created by Guest
Created on Jul 10, 2019

Dynamic stopping criterion - An effective way to interrupt the optimal solution search for MILP

Please, see the attached document-

  • Guest
    Aug 25, 2020

    As stated in my previous comment, the dynamic criterion you describe is way too vague to implement as a general feature in CPLEX. CPLEX would have to provide a way to allow the user to submit an arbitrary function to compute the acceptable gap depending on time and other features.

  • Guest
    Aug 24, 2020

    Thank you for your feedback.

    We have already implemented the dynamic stopping criterion using callbacks.

    Neverthanless, I think that general stopping criterion could be extended supporting also the dynamic stopping criterion.

    Luigi Poderico

  • Guest
    Aug 14, 2020

    Can be done using Generic callback.

  • Guest
    Jan 28, 2020

    This dynamic stopping criterion looks a very flexible thing: over time the acceptable gap rises. But how exactly does it rise over time? Is this a linear function? A quadratic one? An exponential one? How exactly the acceptable gap is computed from the elapsed time may be very user specific. So it may be quite hard to cast this into a single parameter. One can also imagine extensions like "reset the gap for every new incumbent found", i.e., give the engine some more time to find good solutions.

    All this being said, it seems rather hard to come up with a single dynamic stopping criterion.

    On the other hand, the criterion described in the author's note can be easily implemented using callbacks: In a callback you can easily figure out the gap and the elapsed time. From a callback you can also easily abort the solution process. As of version 12.9 we have generic callbacks that guarantee to not have any effect on the optimization process as long as you don't explicitly stop the process. Using the generic callback with the LOCAL_PROGRESS and GLOBAL_PROGRESS contexts it seems rather simple to implement the requested dynamic stopping criterion (and others).