Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow custom action selection criteria #1

Open
zsunberg opened this issue Sep 11, 2017 · 3 comments
Open

allow custom action selection criteria #1

zsunberg opened this issue Sep 11, 2017 · 3 comments

Comments

@zsunberg
Copy link
Member

We should allow the user to specify a custom action selection criterion like in POMCPOW

@simon-lc
Copy link

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).

@MaximeBouton
Copy link
Contributor

This is related to JuliaPOMDP/POMDPs.jl#226.

Note that the function insert_obs_node! that is calling actions does not have access to a state nor the belief.

@simon-lc
Copy link

Thanks for the redirection!
You're right insert_obs_node! only has access to the observation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants