Smart Stop vs MP Limit

Smart Stop is not meant to replace the MP Limit. Both conditions are relevant and it is important to understand the differences.

If your aim is the following:

"I don't care much about aesthetics, I care about time. I want to accept the first legible result and move on."

The MP Limit should be used, not Smart Stop. The more you care about time and not about aesthetics, the greater the MP Limit value should be. For example:

27/08/2019 18:57:38 optimization started.

27/08/2019 18:57:38 Result improved: T=0.6s AC=12 KFV=0 MP=10.00 (1) (…)

27/08/2019 18:57:38 Result improved: T=0.9s AC=12 KFV=0 MP=1.60 (1) (…)

27/08/2019 18:57:38 Result improved: T=1.2s AC=12 KFV=0 MP=1.60 (1) (…)

27/08/2019 18:57:38 Result improved: T=1.5s AC=12 KFV=0 MP=1.60 (1) (…)

27/08/2019 18:57:38 Result improved: T=4.8s AC=12 KFV=0 MP=1.60 (1) (…)

27/08/2019 18:57:38 Result improved: T=5.4s AC=12 KFV=0 MP=1.60 (1) (…)

27/08/2019 18:57:38 optimization stopped: timeout 150s.

In this case, if the MP Limit = 2 (or a greater value) the session is stopped at T=0.9s. This is when the first result is achieved with KFV=0 and MP < 2. Smart Stop does not need to be enabled.

If your aim is the following:

"I expect the computation to stop when the result cannot be improved. If the result can be improved, I expect AVEVA E3D Whitespace Optimizer to continue to work further. I don't know whether the result can be improved, but I expect AVEVA E3D Whitespace Optimizer to know."

Smart Stop should be used and the MP Limit set to a small value. For example, one or zero.

If you would prefer the session to stop earlier with less regard for aesthetics, then consider increasing the MP Limit value.