AI Status Update

AI

It’s weird: the artificial intelligence is my biggest project right now, the thing I’m most excited about. I’m putting in lots of work and making lots of progress. Yet I’ve barely mentioned it on the blog for the past few months.

Why?

Partly because my AI work these days is…abstract. The code I’m writing now lays the groundwork for cool, gee-whiz features later, but there isn’t a lot of “real” stuff yet that I can demo, or describe.

I could tell you about the abstract stuff, but I avoid that for two reasons. First, because I don’t want to bore you.

And second, because – crazy as it sounds – I think this thing might actually work. If it does, it could be dangerous in the wrong hands. So I want to keep the details secret for now. (The code snapshot above is real, but – I think – not especially helpful. Yes, I am actually paranoid enough to think about things like that.)

Having said all that, I can tell you a few things.

For starters, I really am working hard. I put in an hour and a half every day (or drop it to a half hour sometimes when my schedule’s tight). I’ve written over 5,000 lines of C++ and over 1,000 lines of C#, and created a database with 13 tables and 43 stored procedures (to say nothing of the XAML, Javascript, and Ruby components). I’ve filled two notebooks with designs and ideas. Not that those numbers are astoundingly high, but the code works, and I’m revising it constantly.

And as much time as I’ve spent on theory, design, and groundwork, the current program does actually do some fairly cool things. For instance…

  • You type to it, and it types back.
  • You can make it recognize arbitrary new commands. No hard-coding required, just click a few buttons in the MindBuilder interface and drop the new agents into the database.
  • It takes as input, not merely a stream of typed characters, but a stream of moments. So it can recognize words, but it can also notice if you pause while typing.
  • Right now, inputs are keyboard and robot sensors, outputs are text and robot action. But the framework is completely flexible. Any new input or output I want to add – a camera, a thermometer, whatever – it’s just a matter of writing the interface. The underlying architecture doesn’t change at all.
  • It can recognize words, phrases, sentences, even parts of speech. It can respond differently to later commands based on something you told it earlier. And likewise, none of this is hardcoded, so the exact same mechanism that recognizes a written phrase could also recognize a tune, or Morse code.

The history of AI is littered with the ashes of hubris. So although I’m still wrapped up in the joy of hubris today, I’m well aware it’s a delusion. I can honestly say that the path to a strong AI seems fairly clear, that I don’t see any major obstacles that will prevent me from creating a thinking machine. Yet I know the obstacles are surely there, and I’ll see them soon enough.

Still, it’s exciting.

Any questions?

Advertisements

5 responses to “AI Status Update

  1. That’s some exciting coding going on.

  2. Impressive.

    I imagine that you’ve covered this before, but I’m curious about what this is, in the sense of where it sits. In other words, is this an application that will run on a standalone computer, or will it be web-based?

    I’m curious because I’ve never encountered JavaScript (for which my keyboard suggested “Java Scripture” as an alternative…) except in relation to a browser. But, of course, there’s a lot I don’t know. 🙂

    • Good question!

      The main program – the AI itself – is C++ and runs on my home PC, the same one I’m typing on right now. It talks to the Lego robot via Bluetooth. There’s a PostgreSQL database behind it, and a C# desktop app (the “MindBuilder”) to manipulate the database. Both of those are on the PC too. Those three components form the bulk of the project.

      The JavaScript and Ruby (on Rails) are the web components, and they’re not as fully-developed yet. I built them because I wanted to try out some GUI stuff using HTML 5, and because I wanted to learn Ruby on Rails and HTML 5. I don’t use them too often yet, but when I do, they currently run on my PC as well – acting as a web server (localhost) – and are accessed via a web browser, also on my PC.

      So, short answer, it’s all on my PC – for now. Long-term, the architecture will definitely grow beyond a single computer.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s