align-toparrow-leftarrow-rightbackbellblockcalendarcamerachatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditemptyheartfacebookfullheartglobegoogleimagesinstagramlocation-pinmagnifying-glassmailmoremuplabelShape 3 + Rectangle 1outlookpersonplusImported LayersImported LayersImported Layersshieldstartwitteryahoo

Let's do statistical models for non-deterministic online navigation (AIMA ch. 4)

4.11c asks you to develop an error-correction strategy for online search agents which can recover from multiple, sequential failures; this brings up some interesting issues: it turns out that it might be necessary to collect statistics on transitions to determine what the most likely result of an action might be.

In order to assess one's next move, furthermore, it may be necessary to calculate the expected utility as a sum of cost-probabilities.

Let's develop a planning agent that keeps track of state-transition probabilities, even during error correction; and that can take advantage of accidental loops during error-recovery. This may also involve a novel data-structure that behaves like a stack but with constant-time random access.

Join or login to comment.

  • Peter D.

    Prasan showed off some good Kalah stuff, and I finally presented some non-determinism.

    March 19, 2013

  • Glenn B.

    Folks, I am wiped out tonight and can't make it. Sorry.

    March 18, 2013

    • Peter D.

      Hey, Glenn; do you have a Monday left or was that the last one?

      March 18, 2013

  • Dale B.

    Sorry I can't attend this one. I'll be there again soon. The topics are grear and I'm re

    March 13, 2013

    • Peter D.

      Hey, Dale; hope to see you soon.

      March 18, 2013

  • Patrick N

    Can't make this one, but I'm wondering what the activity breakdown is like for reading/planning/coding. Could've sworn I've seen pictures with whiteboard/dry-erase at some point :V

    March 18, 2013

    • Peter D.

      Hey, Patrick; someone typically codes up a solution to a problem they're interested in, which may or may not work. If it doesn't, we whiteboard together; even if it does, we still whiteboard. When we're starting a new chapter, we'll usually spend a little time talking about the techniques and concepts before we delve into problem-solving.

      March 18, 2013

  • Dale B.

    Sorry I can't attend this one. I'll be there again soon. The topics are grear and I'm re

    March 13, 2013

4 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy