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

Root Management #4

Open
zsunberg opened this issue Jun 27, 2018 · 1 comment
Open

Root Management #4

zsunberg opened this issue Jun 27, 2018 · 1 comment

Comments

@zsunberg
Copy link
Member

Hey @dressel ,

I was perusing through our solvers today and noticed the long section in the README about root management. Not sure if we have talked about this before, but one solution to the root_manager=:user conundrum that you describe is to make a AEMSTreeUpdater that uses the tree itself as part of the belief. This updater's update function would simply set the new root to be the child of the current root corresponding to the true observation that it received. updater(::AEMSPlanner) would return an AEMSUpdater. No worries if you don't have time to do it, just a thought.

@dressel
Copy link
Collaborator

dressel commented Sep 26, 2018

That's actually a pretty good idea. I probably won't work on it in the near-term (it's a low priority), but it's worth looking into at some point.

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