You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! I'm trying to add an action selection criterion. I would like to have a set of available actions for each node defined by: actions(pomdp, belief) or actions(pomdp, s). With the belief computed via the history of actions and observations (h in "Monte-Carlo Planning in Large POMDPs") and s a state that is a particle in the set B(h).
I implemented POMDPs.actions(pomdp, s). However when I run the BasicPOMCP solver actions are selected in the set defined by POMDPs.actions(pomdp). Is there a way to force the solver to use actions(pomdp, s) or a function like actions(pomdp, belief) instead of actions(pomdp).
We should allow the user to specify a custom action selection criterion like in POMCPOW
The text was updated successfully, but these errors were encountered: