On midterm #1:
<p>
What to expect: Here are the sorts of questions I tend to ask:

<ul>
<li> Define terms in your own words.

<li> Sketch the execution of an algorithm. For example, show the queue for
A* on a particular problem.

<li> Give pseudocode describing an algorithm.

<li> Give the setup for a problem. for example, what would the state,
successor function, etc look like for the Towers of Hanoi?

<li> Compare different algorithms and their strengths/weaknesses.

<li> Explain why an algorithm has the characteristics it does. For
example, what does the h function do in A*?  

</ul>
<p>
Here are the sorts of questions I will not ask.
<p>
<ul>
<li> Write syntactically correct Python code. (I may ask you to write
pseudoode, but I'll be interested in program correctness, not whether
every bracket and colon is in the right place)
<li> Multiple choice questions. 
<li> "Trick" questions - the point of this exam is to test your
knowledge of the topics we've covered. I may ask you hard questions,
but I won't ask things that are deliberately misleading or deceptive.
</ul>
<p>

Potential exam topics:
<p>
<ul>
<li> Agents:
<ul>
<li> Parts of an agent: Percepts, sensors, actuators, actions.
(be able to define these concepts and identify them in a 
particular application)

<li> Definitions
<ul>
<li> Autonomy
<li> The "intentional stance"
<li>Rationality
</ul>


<li> Environments:
<ul>
<li> Observability
<li> Deterministic/stochastic
<li> Episodic vs sequential
<li> Static vs Dynamic 
<li> Discrete vs continuous
<li> Single-agent vs multi-agent
<li> (you should be able to explain these terms and use them to
characterize a particular environment.)
</ul> 
</ul>


<li> Uninformed Search:

<ul>
<li> Basic algorithms: BFS, Uniform cost search, DFS, DLS, IDS
<li> Be able to: 
<ul>
<li> describe the algorithm in pseudocode
<li> trace their execution.
<li> Characterize their time and space requirements.
<li> Describe whether they are complete and/or optimal (and
define those terms)
</ul>

<li> Problem setup: be able to take a description of a problem and set it
up accordingly. Describe what the state will be, what the initial
state is, what the goal test is, and how the successor function works
with enough precision that someone could write code to implement this.


<li> Definitions:
<ul>
<li> Complete
<li> Optimal
<li> State space
<li> Path cost
<li> Weak method
</ul>
</ul>

<li> Heuristic Search:
<ul> 
<li> Basic Algorithms: Best-first search, Greedy Search, A*.
Be able to: 
<ul>
<li> describe the algorithm in pseudocode
<li> trace their execution.
<li> Describe whether they are complete and/or optimal (and
define those terms)
</ul>

<li> Definitions:
<ul>
<li> Admissibility
<li> Monotonicity
<li> Optimally efficient
</ul>

<li> Be able to: 
<ul>
<li> propose heuristics for a problem
<li> show that a heuristic is or is not admissible. 
</ul>
</ul>
<li> Information Retrieval 
<ul>
<li> definitions: 
<ul> 
<li> Types of Queries
<li> Information Need
<li> "bag of words" 
<li> Corpus, lexicon
<li> Boolean and probabilistic queries
</ul>
<li> Know how to compute TFIDF
<li> Know how to compute cosine similarity
</ul>
<li> Natural Language Processing 
<ul>
<li> Definitions: 
<ul>
<li> syntax and semantics
<li> parse tree
</ul>
<li> Be able to tell what strings are produced by a grammar
<li> Be able to describe the difference between top-down and bottom-up
parsers.
<li> Be able to explain why a chart parser is more efficient than a
top-down or bottom-up parser.
</ul>
</ul>