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
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.
The text was updated successfully, but these errors were encountered:
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'supdate
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 anAEMSUpdater
. No worries if you don't have time to do it, just a thought.The text was updated successfully, but these errors were encountered: