Hello,
I’ve been experimenting with the planner module in Picat, and I’m running into an issue where my planning problem doesn’t seem to branch as I expect.
In my model, the state is [Timers, Phases, Occs, Time], and I want phase transitions to branch nondeterministically when a timer expires. I wrote update_phase/5 like this:
My next/2 facts return lists of possible successors, e.g.:
And duration/2 is defined as:
When I run plan or best_plan
from the initial state:
I only ever see plans going through red_1_long. I expected the planner to also explore the red_1_short branch (and produce a different plan with a lower cost).
It looks like the member/2 nondeterminism is not being explored, or perhaps the planner’s search strategy prunes it too aggressively. Am I misunderstanding how branching in the planner works when member/2 is used inside action/4?
Thanks a lot for your help!
--
You received this message because you are subscribed to the Google Groups "Picat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to picat-lang+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/picat-lang/895f8445-8796-4b77-8dc8-f31433f6ae31n%40googlegroups.com.