This page details what to do when the results of the OE are not what we “were expecting”.
| Table of Contents |
|---|
I do not see the impact on the change of scope/constraints on the results
Possible cause: All the needed calculation steps are not executed.
Solution: When the scope, the business rules or the objectives are changed, the run step will have to be executed again to compute the new results. After that, executing the results step is needed to update the visualizations.
Some results are really strange (massive negative margins etc.)
Check: Check the source data; often we are missing a filtering step removing bogus inputs or data that do not fit the scope of the problem. Ensure that you are working on the correct subset of data and if the behavior persists, look into the tables to find the explanation with the ID of the involved points.
The target objectives are not reached
Check: Look at the information tooltip next to the finished OE job. If it says that “Some value finders are still moving fast with unsatisfied neighbor” it means that the OE needs more steps to find the solution. This is especially true if a large portion of the value finders is moving fast.
...
Solution: With feedback from the domain, decide if you have to modify some constraints or to add an exception for specific agents (e.g. not optimizing for some specific product).
The constraints are satisfied but the solution is not “good enough”
Possible cause: The objectives/constraints are not precise enough.
...