Here's a fascinating essay by Mike Kaplan, who oversaw marketing for the movies 2001 and A Clockwork Orange, which explains how Stanley Kubrick became one of the first commercial data scientists. In 1971, as Kaplan and Kubrick were trying to determine which theaters should show the new movie, they realized that Variety published box office totals for individual cinemas in every city. The data would potentially reveal people's preferences for different theaters, if only the two men could come up with a way to access it. In the days of manual databases, that meant spending six weeks collecting volumes of carefully curated notebooks to tally 18 months of back data. The payoff, however, was enormous: the studio was able to show the new film exclusively in theaters with the perfect mix of margins and demographics.

Rumors even presaged today's computer-driven industry:

Word quickly spread that Stanley had a computerized system to track theaters and grosses based on technical information he had acquired while developing HAL 9000, the all-knowing computer in 2001. For months these stories persisted in the trades as the roster of Clockwork cinemas was refined. They were neither confirmed nor denied.

(via Daring Fireball)

{ 0 comments }

Have your math and eat it, too

January 11, 2012 in Math

Here are two of my favorite things, unexpectedly combined:

This is from the slideshow accompanying a brief NYT article on an unusual book called Pasta by Design. The book is about, yes, modeling pasta in Mathematica.

(via FlowingData)

{ 0 comments }

Call 'em like you see 'em

January 5, 2012 in Data

Anderson Cooper, on air, referring to CNN's nonsensical "Social Media Screen":

The social media screen, again with the social media screen. My Lord. This is the third hit, I still don't understand what the hell this thing shows!

It's a shame that it takes a 3am broadcast for someone to let the emperor know his clothes are missing.

(via The Huffington Post)

{ 0 comments }

...and not a drop of value

January 5, 2012 in Data

Bryce Roberts gets it:

Here’s the thing. Data, big, medium or small, has no value in and of itself. The value of data is unlocked through context and presentation.

{ 0 comments }

Fun with servers

December 5, 2011 in General

I apologize to all my readers for the outage we experienced this weekend. I had to do some server surgery including a very frightening "erase everything" operation that I hoped -- but couldn't be entirely sure -- would be reversed with a TGR backup. This was all compounded by a bit of travelling that left me unable to address the issues until this morning.

The good news is, we seem to be up and running again. I'm sorry again for the inconvenience.

{ 0 comments }

Brilliant

November 27, 2011 in Math

Six famous thought experiments, each presented in 60 seconds:

YouTube Preview Image

Reminds me a bit of the Peabody and Sherman sketches from the old Rocky and Bullwinkle show...

{ 0 comments }

A few weeks ago, I complained that Google Maps' new WebGL version was being artificially -- and unnecessarily -- restricted to high-end machines, creating a sort of "minimum system requirements" for the web. Therefore, I was very interested to see that Nokia's competing maps product, Maps 3D, has just released its own WebGL product.

Unlike Google Maps, it doesn't have a hardware lockout (that I'm aware of). It does have a software requirement, however. Currently, and somewhat ironically, it only runs in Google's Chrome browser.

Nokia's product provides a full 3D map, not unlike Google's Earth plugin. I can rapidly call up a full reconstruction of Manhattan in which even the individual trees in Central Park have been modeled with some fidelity. By contrast, Google's current WebGL product only provides vectorized (non-3D) maps, with realtime vector shadows as the "crown jewel." I stand firmly by my claim that Google's hardware throttling is completely arbitrary.

Nokia could use a win -- maybe this will help. Try it out here (and let me know if you see any hardware restrictions).

{ 0 comments }

I remember when the concept of "minimum system requirements" became important. It was during the late 90's, as 3dfx and Nvidia battled to own the nascent market for hardware-accelerated graphics. For the first time, you had software which simply wouldn't run on a computer unless it met certain criteria, namely the ability to perform certain types of linear algebra (though that wasn't part of the marketing, for some reason).

Over the next near-decade, the GPU would become a near-standard piece of equipment, 3dfx would disappear (bought, in fact, by Nvidia), and ATI (now AMD) and later Intel would arrive as new competitors. But the concept of "minimum system requirements" quietly disappeared. The binary outcome (will or won't your system run this software?) was replaced with a spectrum (how well will your system run this software?) as manufacturers found ways to gracefully degrade their products. It's been a while since I came across a product that simply wouldn't run, in one form or another, on a modern computer.

And that's why I was so surprised to discover this evening that "minimum system requirements" are not only back, but they're on the web! I'm not talking about some shadowy site that only a handful of people will stumble upon. I'm talking about one of the most widely-visited properties in the world: Google Maps.

Google announced that its more daring customers may enable an experimental WebGL mode in Google Maps, which allows smooth vector rendering and other visual niceties like 3D buildings with shadows that actually track the local sun. It also appears that Street View fully integrates the 3D data collected along with the imagery, to enhance the illusion of motion.

But this all comes with a catch -- unless your system is packing a modern browser AND a recent GPU, the experimental renderer will refuse to load. I have no problem with the browser requirement. Browsers are free; it astounds me that someone wouldn't run the latest available version of their preferred browser. But the GPU requirement bugs me. First of all, this technology is currently available on mobile phones; let's not pretend it requires significant hardware capabilities. Secondly... it runs on mobile phones. I constantly wonder at the fact that my iPhone is orders of magnitude more powerful than my first computer, but I've never considered for one second that it was more capable than my current machine.

I'm going to choose to believe that the "minimum system requirements" is an artificial gate akin to Google's infamous "beta" tags: a simple way to disclaim any bugs or errors without having to provide full support. What better way to test an experimental rendering engine than having your testers self-select based on a preference for high-end graphics work? I really can't argue with the logic.

In the meantime, I'll sit here and dream about exploring WebGL maps on my MBA. While I wait, maybe I'll play around with the Google Earth browser plugin. It's really kind of incredible: I can fly over a faithfully rendered 3D globe, filled with textured buildings and trees, without ever leaving my browser*, but if I want to see building shadows that update in realtime, I need to buy a new GPU. Something doesn't add up.

*I know, I know, it's a plugin. It doesn't count.

{ 0 comments }

Stat is magic

October 13, 2011 in Data,Math

I really love the latest post on Lessons from my Twenties, called Stat Is Magic.

Sometimes, things are better left as magic.

{ 0 comments }

We have a new car and it has an American radio. That wouldn't be a problem except that in Israel, FM stations broadcast on even-numbered spectrum intervals (like 97.8), but American radios can only pick up odd-numbered intervals. And even that wouldn't be a problem if I hadn't grown to really like Israeli radio stations (especially the aforementioned 97.8, "Radio Gimel").

So, the new car has prohibited me from listening to the radio. It's not the end of the world -- after all, I'm a tech geek with an iPhone. If anything, the radio was a digression from my usual habits. The only trouble is -- brace yourself -- the car doesn't have an aux port. There's no way to get sound from the iPhone to the car.

This is bad. Driving a car without music is like writing an analogy without .

The car does have a CD player -- but when was the last time you used a CD to play music? My computer doesn't even know what a CD is, except in the abstract virtual sense that it can access remote drives on the same wireless network that identify themselves as such.

And so we come to the cassette player. Yes, there's a cassette player. And, at wit's end, I acquired a cassette adaptor for my iPhone. I plugged it in, inserted the tape, and was rewarded with a clicking, grinding noise that was almost, but not quite, utterly unlike music. Something was wrong. I took the tape out, looked at it, tried turning the little wheels. I noticed they would only go one way with any ease; rotating them the other direction resulted in the clicking noise. I decided that the tape was jammed, damaged, or both and gave up on the whole project. I was resigned to spending the rest of my car rides in silence.

That all happened one week ago.

One good thing about silent driving: you get an awful lot of thinking done. And so it was that this morning I suddenly remembered that cassette tapes -- those antiquated relics of an analog era -- had two sides. And when you reached the end of one side, you turned it over and listened to the other. Or, if you had a really fancy tape player, you just told the machine to switch sides and it handled the complexities. In The Future, one hoped, the machine would even figure that out on its own! Most importantly, you could tell if you were at the end of a side when the tape refused to advance any further.

I immediately knew: I was at the end of the tape.

I can't easily describe what this revelation felt like. It was such a little, stupid thing, but it provided massive relief. It was exactly the same feeling as solving a difficult data analytics problem -- you turn the issue over and over in your mind, trying to understand how it works and the various causalities it represents, until finally you intuit the system. In this case, the experience was almost archaeological: I had conquered the antique. I had unlocked its mysteries.

I went back to the car. I found the "switch sides" button. And there was much rejoicing.

{ 1 comment }