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

Why was the 'sparse_actions' function from POMCP.jl removed in BasicPOMCP.jl? #29

Open
richa-varma opened this issue Jul 14, 2022 · 1 comment

Comments

@richa-varma
Copy link

richa-varma commented Jul 14, 2022

@zsunberg While looking at ways to reduce the size of the action space in my model during computation, I came across the POMCP.sparse_actions function in the documentation of POMDPs.jl, which I understand has been deprecated.
I was wondering if there was some rationale behind not providing this function in BasicPOMCP.jl, and if there is another way to sample a subset of actions to be considered at the current node during planning.

@zsunberg
Copy link
Member

You should just specify the smaller action space as the action space for the POMDP that POMCP is solving.

Note that this action space can be belief-dependent, since BasicPOMCP always uses actions(m::YourPOMDP, b) to get the list of actions that it will consider at each node.

Note that the POMDP that you are simulating does not have to be the same as the one you are using with the POMCP solver, so you can create one version of your POMDP with a full action space, and one version with a limited action space to give to POMCP.

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

2 participants