Skip to main content

Matthew - Capstone Blog Post 2

In Towards Integrated Imitation of Strategic Planning and Motion Modeling in Interactive Computer Games, Dublin City University researchers Bernard Gorman and Mark Humphrys detail their experiments in using imitation learning techniques to teach an artificial agent to play a first person shooter—in this case, Quake—in a way that would convince onlookers and other players that it is human. They describe a superior agent, which imitates "the observed goal-oriented behaviors of a human player," (p. 2) in order to play with competence, exhibit strategic thinking, and employ "believably human-like motion" (p. 1). In other words, they want to create a bot that can pass a kind of Turing deathmatch.

Gorman and Humphrys describe the behavior model which serves as the basis for their work. The model specifies several levels of control, where each level corresponds with roughly how much time the agent has to form a plan. These range from immediate ("scrambled control") to long-term ("strategic control"). Furthermore, their model relates these levels of control to three kinds of behavior—strategic, tactical, and reactive—which together are supposed to form the building blocks for an agent's motion modeling capabilities (p. 3).

In their experiments, Gorman and Humphrys emphasize the "human-like motion" mentioned above. Specifically, they limit their agent's problems to those of environmental navigation and item acquisition. Their methods involve topology learning (p. 3), Markov decision processes or MPDs (p. 4), and motion modeling based on "action primitives." The action primitives, the recorded gameplay, and relevant state space information comprise the training data (p. 6-7). They applied their agent in two types of tests: "pickup sequence" tests, in which the agent must pick up a series of items, and "continuous gameplay" tests, which were of a more free-roam nature (p. 8-9). The researchers noted that the agent performed "showed impressive performance and adaptability" during the pickup sequence tests (p. 8). Otherwise, they noted one issue in the continuous gameplay tests: the agent would sometimes struggle to choose among competing utilities (p. 10-11).

Gorman and Humphrys note in their conclusion that their work relates closely to that of Christian Thureau of Bielefeld University. They mention several works from this author throughout the paper. Please consider joining me next time as I explore this researcher's work.


Popular posts from this blog

Matthew - Blog Post 9

After our last meeting, Professor Auerbach asked us to shift our focus towards building and training our model. So that's what we've been working on lately. The results so far have been interesting and problematic.

The first step was to define a minimal working model and a loading system to feed it our labelled data-set. I wrote a Sequence subclass, which is essentially a kind of generator designed for use with the fit_generator method. With fit_generator and a sequence, we're able to train and test the model with just a couple of one-liners:


The sequence subclass also has a few other tricks up its proverbial sleeve. For one, it reduces the dimensionality of the frame buffer data from 135×240×3 to 135×240×1 by converting it to gray-scale. This reduces the number of features from 97,200 to 32,400. For two, it does the same with the labels, combining and dropping 26 action types into just 9 atomic classes. This a…

Matthew - Blog Post 7

Since January, we've been working hard to not only finish writing the Replay Parser and Frame Collector but also totally synchronize them. I'm pleased to report our success. This is an amazing milestone for us because it means that we've surmounted one of our most troubling obstacles.

I have also made sure to keep our documentation up to date. So, if you like, you can follow along with this blog post by replicating its results.
The Frame Collector uses timed input sequences to start each replay associated with the currently running game version. Then, after waiting a set amount of time for playback to begin, it starts grabbing 1/4-scale frames at a rate of 10 frames per second. The Frame Collector takes these down-scaled frames, which are NumPy arrays, and rapidly pickles and dumps them into the file system. Here's a screenshot of the Frame Collector in action:

If you look at the image above, you'll see that each pickle (the .np files) is simply assigned …

Matthew - Blog Post 8 is only 339 lines long but it feels at least three times that when I'm working on it. The module is definitely due for a refactor. For one, the term subdataset should be renamed to version_set and extracted into a class. version_set more accurately and describes what it is, and the class extraction would clean up the namespace in ReplayManager. There is probably some kind of class extraction possible for replays, so that their names, paths, file streams, and Twitter profiles can all be neatly encapsulated, thereby cleaning up the namespace even more. However, I do not want to worry about having two kinds of replays: the one used by ReplayManager and the one used by ReplayParser. Even though ReplayManager does not use ReplayParser, the prospect of making things more muddier deters me.

There's probably a right way to refactor this code, but, to put it simply, now is not the time. Speaking of time, I came up with a great way to get work done, even when I am sleep…