logo logo
Home arrow Blog...
Sunday, 04 January 2009
 
 
English English  Español Español  
Upcoming Events
10.Jun. 2009

IWANN 2009
Salamanca, Spain
11.Jun. 2009

Toward a Science of Consciousness
Hong Kong, China
15.Jun. 2009

International Workshop on Machine Consciousness
Hong Kong, China
15.Jun. 2009

The 8th IEEE International Conference on Cognitive Informatics
Hong Kong, China
22.Jun. 2009

IWINAC 2009
Santiago de Compostela, Spain
Tag Cloud
Architectures Associations Books Conferences Conscious Consciousness Developer Documentación Documentation Español Howto Machine Machine Consciousness Machines Neuroscience Publications Research Researchers Reviews Robotics Robots Spanish Studio VPL
Spotlight
A blog of all section with no images
Maze Simulator Service Print E-mail
Written by Raúl Arrabales Moreno   
Thursday, 09 August 2007

This Maze Simulator Service for Microsoft Robotics Studio is 99% based on the MSRS Maze Simulator by Trevor Taylor (find the original version following this link to Trevor's page). I just modified it to use my simulated SONAR service instead of the simulated Laser Range Finder (LRF). I called this branch of MazeSimulator MazeSimulatorRA and also changed the contract identifier, so you can have both versions in the same MSRS environment.

 Background

Please check original documentation available at the link provided above for a complete overview of this service. Basically this service allows you to simulate a maze composed of walls and blocks in the MSRS Visual Environment. I am using it to simulate a Pioneer 3 DX robot in a building-like environment. The service builds the 3D maze from a 2D color bitmap that especifies the position and color of the walls. I am using a bitmap image that resembles to my lab environment so I can test exploration and SLAM algorithms in the MSRS simulator.

As I am currently using SONAR sensors instead of a LRF I commented out the laser part of the original service and included my simulated sonar service.

 

Service Download

- MazeSimulatorRa Source Code Download (for MSRS 1.5).
- Maze Simulator Source Code Download (for Robotics Developer Studio 2008).

 

Installation Instructions (for source code zip archive)

Please see readme.txt file included in the zip file for detailed instructions. The zip file contains the source code, resources, and visual studio solution. Download the ZIP file and unzip it into your MSRS root directory. This should create a directory called: <MSRS>\Apps\UC3M\MazeSimulatorRA

 

Service Details

Service Contract Identifier:
    http://www.conscious-robots.com/2007/8/mazesimulatorra.html

Implements generic contract: 

Service partners:
    Microsoft.Robotics.Simulation.Engine.Proxy
   

Allow Susbscriptions: 
    No.

Service State:
    Cranium.Simulation.Worlds.MazeSimulatorState

 

Service Implementation Description

See http://sky.fit.qut.edu.au/~taylort2/MSRS/MazeSimulator/MazeSimulator.htm for more information about the implementation.

 

Video:

 

Comments (2) | Add as favourites (133) | Quote this article on your site | Views: 5506 | E-mail

Last Updated ( Thursday, 27 November 2008 )
 
Simulated SONAR Service Print E-mail
Written by Raúl Arrabales Moreno   
Thursday, 02 August 2007

The Simulated SONAR Service provides access to a simulated SONAR array. It uses Robotics Studio Simulator raycasting to simulate SONAR transducers. Using this service you are able to test SONAR object detection and distance measurement in the MSRS Visual Environment.

Background:

ARCOS based robots (like the Pioneer P3-DX) can integrate up to four SONAR rings, each with eight transducers. These sensors provide object detection and distance information. The Robotics Studio platform doesn’t include a simulated SONAR service that could be use in the Visual Environment. However, there exists a generic contract for SONAR that I wanted to implement for the specific case of my SIMULATED P3-DX frontal SONAR array.

NOTE: A real (not simulated) ARCOS SONAR service is available at:
http://www.conscious-robots.com/en/robotics-studio/robotics-studio-services/arcos-sonar-service.html

 I asked Microsoft and I got the following answer:

"you can make a reasonable simulated sonar sensor by doing something similar to the simulated laser rangefinder.  Instead of casting hundreds of rays in a scanline pattern like the laser rangefinder does, cast a handful of rays in a  cone that matches the aperture of the sonar sensor you want to simulate.  In  your code, look at the distance results returned by each ray and then set the sonar return value to be the closest intersection."

Trying to follow these instructions I wrote a service called SimulatedSonar – Source code is available in the download section.

NOTE: Current version of SimulatedSonar don't generate a 3D cone using raycasting, instead a 2D pie is generated and used to calculate the closest intersection. Therefore, the robot only sees in a 2D plane (situated at the height of the SONAR device pose). In order to build a more realistic SONAR, this needs to be fixed. Additionally, noise should be added in the simulation in order to get as closest as possible to a real SONAR.

You can subscribe to this SimulatedSonar service from your application and easily get SONAR readings in your MSRS code (I think this code will be valid for any simulated robot, you just need to add the SimulatedSonar entity to your robot).

 

Service Download:

 

Installation instructions (for source code zip archive):

SimulatedSonar is a small Robotics Studio Service (DSS Service) that allows you to access a simulated SONAR array. The zip file contains the source code and Visual Studio project.

Decompress the contents of the file under MSRS home directory. Note that the service source code is located under Apps directory. Build it using Visual Studio.

See the readme.txt file included in the distribution package for detailed instructions and version history. It is important that you install the service in a machine with the same version of MSRS that is indicated in the readme.txt file. I always try to update the distribution file with the latest available version of MSRS, please check regularly for updates.



Service Details:

Service Contract Identifier:
    http://www.conscious-robots.com/2007/07/simulatedsonar.html

Implements generic contract:
    Microsoft.Robotics.Services.Sonar

Service partners:
    Subscription Manager

Allow Susbscriptions:
    Yes.

Service State:
    Microsoft.Robotics.Services.Sonar.Proxy.SonarState

 


Description:

Each Pioneer 3 DX SONAR ring is composed of eight transducers arranged at angles -90, -50, -30, -10, 10, 30, 50, and 90 degrees. They are polled sequentially at a configurable rate (usually 25 Hz – 50 ms per transducer per array).

The SimulatedSonar service aims to simulate a real SONAR by using the raycasting facility of the MSRS simulator. P3DX front ring sonar is 180 degress. But lateral transducers are centered at 90 degrees, so I consider: 196 degrees. I considered the aperture of one transducer is 16 degrees (real hardware transducers have an aperture of 15 degrees). Therefore,

_state.AngularRange = 196;  // 180 plus two halfs of lateral transducers.

Using the raycasting facility, I generate one ray per degree forming a 2D pie of rays. Then I only consider the rays that fall within the angles covered by each SONAR transducer (the measures obtained from the rest are discarded as the fall in the blind spots between transducers), and for each transducer I retrieve the closest intersection (minimum distance). See figure: blue rays represent discarded measurements. Red rays correspond to measures taken for sonar transducers. The yellow spot is the simulates sonar pose (origin of all rays).

Whenever a substantial change occurs in the raycasting readings that correspond to the simulated SONAR transducers the SimulatedSonar service issue a replace message to all its subscribers notifying a state change.

Within the SonarState object, an eight position array of double values is created. This array (called DistanceMeasurements[]) contains the distance readings corresponding to the simulated SONAR transducers.

 

Comments (5) | Add as favourites (130) | Quote this article on your site | Views: 6401 | E-mail

Last Updated ( Thursday, 27 November 2008 )
 
ARCOS SONAR Service Print E-mail
Written by Raúl Arrabales Moreno   
Wednesday, 01 August 2007

ARCOS based robots (like the Pioneer P3-DX) can integrate up to four SONAR rings, each with eight transducers. These sensors provide object detection and distance information. I am currently using the inbuilt frontal SONAR array for navigation with MSRS.

The Robotics Studio platform doesn’t include a specific SONAR service for ARCOS robots. However, there exists a generic contract for SONAR that I wanted to implement for the specific case of my P3-DX frontal SONAR array.

 I asked Microsoft (see forum) and I got the following answer:

If you subscribe to the ArcosCore service you will receive Replace notifications. This contains the complete state of the ArcosCore service everytime that it changes. Included in that state is a member Information which in turn contains a List of sonar readings in the member Sonar.

Alternatively a specific ArcosSonar service could easily be written to simplify access to this data.


 

Following these instructions I wrote a service called ArcosSonar – Source code is available in the download section.
You can subscribe to this ArcosSonar service from your application and easily get SONAR readings in your MSRS code (obviously, this is only valid for Arcos based robots).

 

Service Download:

Installation instructions (for source code zip archive):

ArcosSonar is a small Robotics Studio Service (DSS Service) that allows you to access the Pioneer 3 DX Robot frontal SONAR array readings. The zip file contains the source code and Visual Studio project.

Decompress the contents of the file under MSRS home directory. Note that the service source code is located under Apps directory. Build it using Visual Studio.

See the readme.txt file included in the distribution package for detailed instructions and version history. It is important that you install the service in a machine with the same version of MSRS that is indicated in the readme.txt file. I always try to update the distribution file with the latest available version of MSRS, please check regularly for updates.



Service Details:

Service Contract Identifier:
    http://www.conscious-robots.com/2007/07/sonar.html

Implements generic contract:
    Microsoft.Robotics.Services.Sonar

Service partners:
    Microsoft.Robotics.Services.MobileRobots.Arcos

Allow Susbscriptions:
    Yes.

Service State:
    Microsoft.Robotics.Services.Sonar.Proxy.SonarState

 


Hardware Description:

Pioneer 3 DX frontal SONAR ring is composed of eight transducers arranged at angles -90, -50, -30, -10, 10, 30, 50, and 90 degrees. They are polled sequentially at a configurable rate (usually 25 Hz – 50 ms per transducer per array).

The ArcosSonar service subscribes to ArcosCore service in order to get any replace message indicating a state change. Whenever a substantial change occurs in the SONAR reading members of the ArcosCore, the ArcosSonar service will in turn issue a replace message to all its subscribers notifying a state change.

Within the SonarState object, an eight position array of double values is created. This array (called DistanceMeasurements[]) contains the distance readings corresponding to the SONAR transducers.

 

 

Comments (1) | Add as favourites (104) | Quote this article on your site | Views: 7461 | E-mail

Last Updated ( Thursday, 27 November 2008 )
 
Cognitive Robotics Print E-mail
Written by Raúl Arrabales Moreno   
Thursday, 26 July 2007

In this article I aim to provide a comprehensive introduction to the field of cognitive robotics by providing you with some definitions, examples, links to information resources, courses, and research projects. Also, the research motivations of this field are discussed, as well as main application areas and the inspiration in natural cognitive systems.

The field of Cognitive Robotics is very much related with Machine Consciousness (MC). Indeed, I consider MC as a subfield or a specific focus of the research on Cognitive Robotics. Any implementation of the functionality of consciousness has to be framed within a cognitive architecture. Consciousness per se does not make any sense unless it is integrated in a subject able to develop end to end (embodied) processes like perception and behavior.

The ultimate aim of the development of cognitive architectures is the implementation of machines that are able to “know what they are doing”, thus being more robust, adaptive, and flexible. Social robots are significant example of the kind of applications that cognitive robots (and particularly conscious robots) might perform. Interacting with humans is an extremely complex task where all these cognitive capabilities are required.

Future cognitive robots are expected to be able to interact with humans, acting and learning in unpredictable environments.

Introduction to Cognitive Robotics (excerpt taken from [0])

Research in robotics has traditionally emphasized low-level sensing and control tasks including sensory processing, path planning, and manipulator design and control. In contrast, research in cognitive robotics is concerned with endowing robots and software agents with higher level cognitive functions that enable them to reason, act and perceive in changing, incompletely known, and unpredictable environments in a robust manner. Such robots must, for example, be able to reason about goals, actions, resources (linear and/or non-linear, discrete and/or continuous, replinishable or expendable), when to perceive and what to look for, the cognitive states of other agents, time, collaborative task execution, etc. In short, cognitive robotics is concerned with integrating reasoning, perception and action with a uniform theoretical and implementation framework.

The use of both software robots (softbots) and robotic artifacts in everyday life is on the upswing and we are seeing increasingly more examples of their use in society with commercial products around the corner and some already on the market. As interaction with humans increases, so does the demand for sophisticated robotic capabilities associated with deliberation and high-level cognitive functions. Combining results from the traditional robotics discipline with those from AI and cognitive science has and will continue to be central to research in cognitive robotics.

Be first to comment this article | Add as favourites (239) | Quote this article on your site | Views: 9794 | E-mail

Last Updated ( Tuesday, 21 August 2007 )
Read more...
 
Robotics Studio 1.5 Released Print E-mail
Written by Raúl Arrabales Moreno   
Thursday, 19 July 2007

 

Microsoft Robotics Group has released the second official version (1.5) of Microsoft Robotics Studio. This version can be downloaded from this link.

For those of you who don't know what Robotics Studio is, let me quote Microsoft: The Microsoft Robotics Studio is a Windows-based environment for academic, hobbyist and commercial developers to easily create robotics applications across a wide variety of hardware. Key features and benefits of the Microsoft Robotics Studio environment include: end-to-end Robotics Development Platform , lightweight services-oriented runtime, and a scalable and extensible platform.  

Microsoft Robotics Studio (1.5) is a significant update to Microsoft Robotics Studio (1.0). It includes support for Windows CE, greatly improved documentation, runtime optimizations, and many other new features. Optional packages provide support for robot sumo competition and simulated soccer competition.

For more information, please see Tandy Trowers' welcome letter:

Be first to comment this article | Add as favourites (178) | Quote this article on your site | Views: 5200 | E-mail

Last Updated ( Tuesday, 21 August 2007 )
Read more...
 
Deus ex Machina. Interview with Anne Foerst Print E-mail
Written by Raúl Arrabales Moreno   
Thursday, 05 July 2007

This is a transcript of a Berkeley Groks interview with Anne Foerst entitled Deus ex Machina.
December 22, 2004.

 

Prof. Anne Foerst
Visiting Professor of Theology and Computer Science, St. Bonaventure University
Author, God in the Machine: What Robots Teach Us about Humanity and God
Website

 

Robots have fascinated the public for years, appearing in countless films, books, and television shows.  The increasingly lifelike capability of robots in the real world has many prominent thinkers wondering how humans and their creations will interact in the future.  Will a thinking machine be regarded as a person, differing from humans only in design?  Will even the most human like robots be seen as possessing a soul?

Joining us today to discuss these issues of robots and our humanity is Prof. Anne Foerst.  Prof. Foerst is a theologian and research scientist, and visiting professor of theology and computer science at St. Bonaventure University.  Formerly she was a research scientist at the artificial intelligence laboratory at MIT, where she founded and directed the God and Computers project.  She is the author of the new book, God in the Machine: What Robots Teach Us about Humanity and God.

Prof. Anne Foerst (AF) joins Charles Lee (CL) to discuss robotics and theology.

CL:  It’s a pleasure to have you on the program.  You’ve written an interesting, and I would have to say somewhat controversial new book.

AF:  Thank you.

CL:  Well, this is indeed an issue that some people might find somewhat controversial, the relationship between robot building and god.  Some might find this incompatible.  How can the two be related?

AF:  First of all, what I realized was that when we try to build humanoid robots in our image, we realize the complexity of humans.  When we really try to build something that moves like us, acts like us, and is smart like us, our appreciation for nature grows.  And, I would put that in spiritual terms, our admiration for god’s creation grows.  So, building humanoid robots in our image is in a way a spiritual enterprise.

CL:  So what then is the motivation for building robots?

AF:  In the literature, you find two motivations.  The first is more hubristic and arrogant, playing god, trying to equal god, and so on.  The other is a more modest goal, trying to find out how we work, learning more about who we are, learning more about what makes us human by trying to rebuild us, and seeing the failures and successes, and therefore find some solution for who we are.  And, actually, it’s the second attempt that I mostly appreciate and discuss in my book.  I’m not interested in people who are arrogant.  I’m interested in people who are seriously interested in who we are, and trying to find out that millennia old quest by building robots.

CL:  So, one of the stories you mention in your book is from the Jewish traditions of golem building, and how one can read those two points of view from those stories as well.

AF:  The golem stories are interesting, because they really have the explicit motive of prayer.  Golem building, construction of artificial humans from clay, is actually a prayer.  And, the nice thing about the golem traditions, which go back to the 13th century to the Jewish mysticism called Kabala, is a real connection between current artificial intelligence research and this old eastern European motive.  Several of the early top notch AI researchers come from that tradition, and actually relate themselves to that tradition, and see those ancient golem builders as their ancestors.

CL:  You also talk about humans as storytellers.  How does this relate to our motivation for building robots and understanding ourselves?

AF:  People have always analyzed humans as thinkers.  So, since the early beginnings of artificial intelligence, people have tried to build machines or programs that could think, do chess playing, mathematical theorem proving, etc.  And, I define humans as mainly embodies and interactive.  That is really what makes us human, not the individual that thinks, but the person that is in community with other people trough embodiment.  We share a physical world.  And, we interact in that world through stories.  It’s interesting because you can see it on the very profane level of neurons, where we have pattern recognition and the way neurons interact, that our brain already creates narratives.  And, you can recognize it on the highest level of human societies interacting, where they have narratives about how they came into place, how they came into being, what’s their meaning, what’s their identity, etc.

So, we tell stories on all different levels.  And, I found out that this is actually a very fruitful attempt to bring theology into the realm of science, because science tells a lot of stories.  And, theology obviously tells a lot of stories too.  And, I think instead of playing out, “Oh, that is objective science”, which doesn’t exist in fact, and, “Oh, that is subjective theology”, I think the storytelling approach actually brings us much closer to talking to one another and enriching both sides of the dialogue.

CL:  Indeed.  You do mention in one of your chapters about the sort of conflict that arose when you attempted to bring these two sides together at MIT.

AF:  Yes.  Um, some people didn’t like me there.  It took me probably at least a year before heads would stop turning whenever the term, evolution, was mentioned, because they couldn’t imagine that I as a theologian had no trouble with evolution.  For me as a German academic theologian, the whole concept of evolution being in conflict with creation is utterly ridiculous.  Before I came to this country, I had never encountered it, because it’s very alien.  It really only exists in certain parts of the United States.  It doesn’t exist anywhere else in the world.  And, so when I encountered it, my explanation for it was that people try to reduce Christianity to something that is quite irrational, because it is easier to discard it then.  And, I think people when they encountered me at the beginning were kind of nervous, because I’m not a wacko.

CL:  Harder to discount then….

AF:  Yeah.  I think at least I’m not, perhaps I am.  So, people were a little bit disconcerted and they tried to put me in an irrational category.  They tried to denounce me as psychologically deluded, and that I would destroy MIT’s objectivity.  They had all of these interesting attacks, in order to kind of handle me.  In a way, when it happened, there was a real war out there, and people tried to get rid of me.  And, when it happened, I was quite hurt, but I had tons of supporters.  There were tons of wonderful people who really supported me, so in retrospect it was quite exciting.  You know, it was kind of funny how religious those people were in their rejection of religion.  So, it was quite emotional and interesting.

CL:  Well, one of the parallels you allude to is that science is somewhat of a religion itself.

AF:  Yes.  I think there are scientists who are not.  And, those are usually scientists that I interact with the most.  But, let’s take the project of building humanoid robots in our image.  When you try to build humanoid robots that are like us, you have to assume that humans are some kind of machine.  Right?  Otherwise, we couldn’t rebuild ourselves.  And, that’s perfectly fine, because science always operates from assumption, and then we see how far we get.  And, there is nothing wrong with that assumption. 

The problem is when scientists then say, “Ah, that means we are nothing but machines.”  So, they turn a statement they assume for pragmatic reasons into a statement about the reality of the world.  And, that is when I come into problems with them.  People who do that are usually the ones who do not believe that human are narrators.  When I think about people like Rodney Brooks, who was my boss at MIT and the head of the whole robot project, he was very happy to say, ‘Of course, in my work, I have to assume that humans are nothing but machines, but I don’t want to be treated as a machine, and I don’t treat my kids as machines.’  And, he was perfectly happy to have that contrast within himself.  They were different stories that relate to different parts of who we are.  But, a lot of people are uncomfortable with that kind of discrepancy.  So, they try to prove the correctness of their assumption.  And, they then become religious.

CL:  Almost fanatical, one might day.

AF:  Yes.  Yes.  You know, what is so sad is that the fanaticism happens on both sides.  Of course, there are religious people who try to prove that humans are more than machines, and they can’t do that either, because there is absolutely no evidence of something like a soul or so.  So, you basically have people on both sides yelling at each other. And when we see that humans can have many different kinds of narratives, which are all true but don’t necessarily have to be coherent, only if we admit that can we make peace with it.

CL:  Should we try to reconcile all of these separate stories?

AF:  Reconcile is sort of a difficult word, because I don’t think that they can be reconciled.  I don’t think they can be turned into one single story.  But, I think they all make sense in certain contexts.  I mean, if I want to find out how a drug works, or how to perform certain surgeries, or other medical things, every idea of humans being more than machines gets in the way, right?  I have to look at the functions and mechanisms of the human system. 

On the other hand, when I want to establish something like dignity and personhood, or fight for humanitarian causes against genocide, I have to assume that humans are more than machine, because otherwise I can’t give any reason for protection of humanity, right?  And, both of those stories make sense, but in very different contexts.  So, both of those stories are equally important.

CL:  So, when you were at MIT, you worked on the development of the Cog and Kismet robots.

AF:  When I first came to MIT, the team had just started to build Cog, who was only a year old at the time.  Cog was a humanoid robot, at first with one arm, then two arms, a head, torso, gyroscope, eyes, ears, and all that kind of stuff.  Cog was very cute and learned to coordinate its various body parts.  It was really the first real life attempt to build a humanoid robot, so it was the first time a serious robot team said that it wanted to build a humanoid by basically turning science fiction into reality.  And, I was quite intrigued by that. 

And, what I especially liked about the whole Cog project was that these people did not say that the core of intelligence is chess playing and mathematical theorem proving, but they said that intelligence is the result of the human’s ingenious capability to survive everywhere.  In other words, intelligence is a result of evolution, and the fact that we can play chess and do math is more or less a by-product.  So, these people were interested in social interaction and coordinating the body.  That intrigued me because that is the type of understanding of humans that we can find in the Bible.  In the Bible, what defines humans is their capability for relationships, especially with God of course, and then with one another.  So, I felt very much at home there.

But, the problem with Cog was that they had so much difficulty trying to get Cog to coordinate its body.  Also, Cog was very massive and tall, and created a lot of anxiety and fear.  So, Cynthia Breazeal, who is now a professor at the MIT media lab, after some years started Kismet, because I had always been saying that when you look at human development, humans are only in relation.  We are so fundamentally relational. And, with Cog, there was too much that the robot did on its own, and I always thought that we needed a robot that was purely reactive, just reacts to input from the outside world, and see what such a robot could do. 

So, Cynthia had the same ideas, and came back with the first proto-Kismet.  From then on, Cog was dead to me, and I only interacted with Kismet.  Kismet has a very cute face, and you basically fall in love with it right away.  It mimics your facial expressions and babbles, and it interacts with you in a quite profound way.  And that was very intriguing.  When I presented Kismet to non-technical audiences, they were much more fascinated by it, but also much more afraid.  They were afraid of all the emotions that they had towards that robot, which they didn’t want to have, because it’s just a stupid machine, right?  And so, Kismet was much more powerful for doing what I wanted to do, which was confronting people with their own mechanisms of social interaction, confront people with the fact that they are capable of reacting to just about everything, and making them aware of who they are.

CL:  In the book, you mention that even a very simple computer program written in the sixties was capable of eliciting these types of emotions.

AF:  Yes, ELIZA.  It was actually written by Josef Weizenbaum, who was an AI professor.  And the fact that his students used that program, which was a simple question and answer program to solve their own personal problems turned him into a critique of AI.  And, it was actually Josef Weizenbaum who got me to MIT.  I met him in Germany and he gave a talk there.  That talk actually inspired me to do the research that I am doing.  And, it was him that invited me to MIT.  It was interesting, because I think he hoped that I would become something of a critic of AI, but I never became one.  I think there is too much reason behind it.

CL:  So, what does this mean for our development of robots?  Do you think there will be a community of robots and humans interacting as storytellers?

AF:  Yes, definitely.  I always like to think that robots will be our future partner species.  In a way when you look at humans, we are so desperately lonely.  We look desperately for animal intelligence by trying to communicate with chimps and dolphins.  And, at the same time we look for extraterrestrial intelligence.  So, in a way, we are a very lonely species.  And, for me as a theologian, that is because we lost our relationship with God that was started at the beginning.  So, it makes sense that we would try to build a species that would be our partners and friends. 

And, I think there is a good chance that those robots will become exactly that.  What we have learned from Cog and Kismet is that the best way to build an intelligent machine is to build it in accord with a human newborn, and like a human newborn let it grow in intelligence with its interaction with humans.  And, so those robots can only become smart if they have interaction, and that’s exactly how a human baby eventually becomes a smart grownup.  So, we have to build them communal, which will be the most fascinating thing about them.

I always refer to the Frakenstein story.  People always tell the story with Frankenstein building the monster who then turns against humanity, right?  But, the way I see it is that Frankenstein builds this monster or creature, and then leaves the creature alone.  And, the creature never has a chance to bond, and this is why it becomes evil.  And so, if we build the robots such that we have to interact with them in a good way to make them smart, then it will be a great relationship.

CL:  Is this the direction people are taking in terms of building intelligent robots?

AF:  Yes.  There is still the old camp that thinks you can build intelligent programs in disembodied, unconnected machines.  And, intelligent databases like that certainly serve their purpose.  But, I think when it comes to real interactive technology, then we have to build them embodied and social.

CL:  So, we are running out of time, but I am curious, how did you become interested in this topic?

AF:  Well, it’s kind of funny.  First of all, I was always fascinated by technology.  When I was four years old, I was building my own machines.  But at the same time, I have to admit that I fell early in love with humans, and I’m fascinated to see how we work.  So, I started first to study theology, and realized that I wanted to do something technical too.  It’s really my quest to determine what does it mean to be human?  Who am I?  This kind of drove me to gather as many insights from as many disciplines as possible.  And I guess with AI and religion that I’m gifted for those.

CL:  Well, you’ve certainly made a major effort in a unique academic field here.

AF:  Well, thank you.  I tried to, and I hope it is received well.  It was a really hard product, and just writing the book took I don’t know how many years.

CL:  Congratulations again on your book, God in the Machine, which I believe is in stores today.

AF:  Yes, it is in stores as of today.

CL:  Thank you for joining us today on Berkeley Groks.

AF:  Thank you

 

Berkeley Groks 2004
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

 - Original transcript at Berkeley Groks.

 

 

Be first to comment this article | Add as favourites (89) | Quote this article on your site | Views: 2489 | E-mail

Last Updated ( Thursday, 05 July 2007 )
 
<< Start < Prev 21 22 23 24 25 26 27 28 29 30 Next > End >>

Results 121 - 126 of 221
Syndicate
 Conscious Robots RSS FeedConscious Robots RSS Feed





Lost Password?
No account yet? Register