Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titlePossible causes and solutions

Possible cause: The objectives/constraints are not precise enough.

Solution: Fine-tune the objectives' precision (acceptable_delta, target…) using the previous results.

Possible cause: Some domain rules are not modeled yet. It can be the case when a client forgets to state some constraints they consider as obvious, such as “price cannot drop” or “margin must increase”.

Solution: Loop with the client to ensure that the domain is fully modeled and that the constraints have the correct type (e.g. target instead of threshold).

Error during

...

Run calculation with keywords: “javaheap” “vmem”, “memory”

Expand
titlePossible causes and solutions

Possible cause: Insufficient resources to run the OE.

Solution: This means that the Optimization Engine didn’t did not complete its run due to a lack of memory. This can be solved by asking the support Support to increase the RAM allocation for the OE, or by updating the job-trigger-config as described here /wiki/spaces/EN/pages/3433037940.