Evan Savage

What I'll Look Like In 50 Years

I spent a few weeks in the not-so-frozen Canadian northlands over the winter holidays. While there, I had the chance to visit an old childhood favorite: the Ontario Science Centre, six floors of science-based awesomeness. One of their current exhibits, the Amazing Aging Machine, uses a computer vision software package called APRIL to predict how your face will change over the next 50 years.

In this post, I explore my results from that exhibit alongside a customized aging I performed using the APRIL API.

Present Me #

It's not the most flattering photo, but here I am at 26:

Future Me #

Take One: Amazing Aging Machine #

First, my face balloons out massively:

Next, my cheek bones set downwards:

Finally, my face leans up and wrinkles a tiny bit:

Take Two: APRIL API #

For this run, I had access to the raw aging metadata, so I could see exactly how old APRIL thought I was at each point in the aging sequence.

From 26 to 28, there's not much change:

Then, by age 35, my face elongates slightly:

I while away the next couple of decades in relative facial stasis. The most pronounced change is in my skin, which pales gradually with age:

Finally, age catches up with me, and I wrinkle into a haunted septuagenarian:

A few changes, each very minor, contribute to my forlorn expression over these last three photos.

Note the lack of deep forehead and upper nose creases which normally accompany the furrowed brow expression. The mere suggestion of it on the eyes is enough to trigger our expression recognition! It's amazing how sensitive we are to minute variations in facial muscle position.

Summary #

These images provide two divergent visions for my distant future:

Why Were Those So Different? #

...the machine uses state-of-the-art aging software developed in partnership with Aprilage Development Inc. of Toronto to add decades to the faces of 8-12 year olds.

The Amazing Aging Machine is calibrated for ages 8-12, likely to match the Ontario Science Centre's target demographic. (Sadly, I couldn't find detailed visitor demographic data!) In my case, this creates an awkward puffy look: it's applying changes in facial structure through adolescence, when much of our bone growth occurs.

By contrast, the APRIL API asks for your current age, allowing it to more correctly calibrate its models. As a result, the second set of faces exhibits relatively little change in shape.

What Do I Get Out Of This? #

Although my face is unlikely to match either of these faces at 72, this experiment provides some insight into how our faces change with age. After all, the APRIL face aging models are based on real face data. They represent a sort of statistical average of the aging process.

Also, I get the vaguely warm feeling that comes with having contributed to our collective intelligence. I provided APRIL with a real age-labelled face, which will likely be used to help train future models.

Appendix: How To Use The APRIL API #

For the more technically-minded, I've provided a quick walkthrough of the API aging pipeline. For all the gritty details, consult the API docs.

Before starting, I highly recommend installing a tool like jsonpp; it makes it much easier to read API results.

The first step is manual: you need to register at ageme.com, then click the confirmation link in your email.

The next step is uploading an image, but let's check first that the API works by retrieving our user info:

$ curl http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/userInfo

Oops! We haven't authenticated ourselves. The Authorization header uses a brain-dead and highly insecure base64 encoding:

$ python -c "import base64; print base64.encodestring('username:password')"

(Obviously this isn't my real username/password. Substitute yours above and use the resulting base64-encoded string in the Authorization headers below. I'll use this bogus value to illustrate the flow.)

With the correct header, we can try fetching the user info again:

$ curl -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/userInfo | jsonpp
"uri": "http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com",
"email": "savage.evan@gmail.com",
"tokens": 0,
"numOfAgings": 1,
"role": "user"

Great! Now we can POST an image to the uploading endpoint with curl:

$ curl -F 'filename=aging1.jpg' -F 'image=@/Users/candu/Desktop/aging1.jpg' -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/images

Another manual step: before proceeding, you'll need to purchase a token on the ageme.com site. At time of writing, this cost $3.99; I looked for active promotion codes, but couldn't find any.

With your aging token purchased, you can now create an aging document. This lets APRIL know your age and ethnicity, which helps it to select the appropriate models for your particular aging sequence. It also identifies the starting image of that sequence via the imageId returned during image upload.

$ curl -H 'Content-Type: application/json' -d '{"document": {"gender": "male", "age": 26, "name": "Evan", "ethnicity": "Caucasian"}, "imageId": 2371944}}' -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/documents

We're ready to run the aging process. There's a single method detectMatchAge for performing all three steps, but I'll break it down into the component steps here:

$ curl -X POST -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/pointDetection
$ while true; do curl -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/status; done
$ curl -X POST -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/match
$ while true; do curl -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/status; done
$ curl -H 'Content-Type: application/json' -d '{"sequenceType": "Max72", "sequences": [{"smoking": 0, "sunExposure": 0, "multiplier": 1}]}' -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/aging
$ while true; do curl -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/status; done

Note the while loops, which wait for each step to complete. Once all steps are completed, we retrieve the aging results:

$ curl -H "Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=" http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/results > aging_results.json
$ cat aging_results.json | jsonpp | head -15
"uri": "http://www.ageme.com/AprilAPI/users/savage.evan@gmail.com/documents/2371973/results/76647",
"status": "done",
"sequenceType": "Max72",
"sequences": [
"smoking": 0.0,
"sunExposure": 0.0,
"multiplier": 1.0,
"images": [
"age": 26,
"uri": "http://www.ageme.com/AprilAPI/images/IhLAo8Sp"

Finally, I wrote a bit of Python glue to fetch the URLs and name them by age:

import json
import sys
import urllib2

data = json.loads(sys.stdin.read())
images = data[0]['sequences'][0]['images']
for image in images:
url = urllib2.urlopen(image['uri'])
path = 'age{0}.jpg'.format(image['age'])
with open(path, 'w') as f:

With this, we can fetch the images:

$ python fetch_aging.py < aging_results.json

And that's it! Most of the process uses curl, with minimal leaning on Python for its base64 module.