CODEWITHSUNDEEP
optaplanner
axellerdp
axellerdp

Reputation: 31

Optaplanner - Why switching from mode full_assert to another gives totally different results?

I am developing a solver using drools to find the most likely date (start date = planningVariable) for which a medical analysis (planningEntity) will start. Then i calculate other dates from it whose calculation does not depend on the optaplanner mechanism (end date and other intermediate dates). For my problem, I need each rule to fire whenever the planningVariable value change.

When using FULL_ASSERT mode everything works but when i change to another mode, results are a mess. Almost no rule is respected or the solution gives null values and i don't understand why.

Is it because the full_assert mode is the only one that guarantees to fire all rules each time the planningVariable value changes?

Upvotes: 0

Views: 88

Answers (1)

Geoffrey De Smet
Geoffrey De Smet

Reputation: 27312

Try running NON_INTRUSIVE_FULL_ASSERT, that doesn't trigger more fireAllRules().

Either way, switching on FULL_ASSERT etc, shouldn't change the behavior (unless you're explicitly using simulated annealing with walk clock time because it is time gradient sensitive). If it does change behavior, it's probably due to some sort of corruption. All the more reasons to run NON_INTRUSIVE_FULL_ASSERT and figure out where.

Upvotes: 1

Related Questions