in reply to Re: Re(*): Neural Nets and Verbal SQL
in thread Testing Inline::C Modules

Parsing English wasn't my intention. I was just generalizing as an example of how neural nets can take incorrect or incomplete information and still make a guess. Their robustness is one of their best features -- so long as the caveats are understood.

For a clearer (i.e., programmatic) example of what I meant, take a look in the game AI example of the neural net module. There, you tell the NN its health, weapons, and the number of enemies it sees and it will suggest an appropriate course of action. While the number of inputs is relatively few, it would be trivial to extend that example to cover a broader range of inputs and still get good answers if your inputs are not complete. Right now, the number of inputs is probably too few to really demonstrate that.

As for genetic algorithms, they would be useless to apply to this sort of problem, but once I work in exposing the error rate in the network, one could use genetic algorithms to design a neural network that could generate relatively accurate answers (much faster than designing by hand) by using a lower error rate as a measure of fitness.

Cheers,
Ovid

New address of my CGI Course.

  • Comment on Re: Re: Re(*): Neural Nets and Verbal SQL

Replies are listed 'Best First'.
Re: Re: Re: Re(*): Neural Nets and Verbal SQL
by flyingmoose (Priest) on Feb 11, 2004 at 19:39 UTC
    Good stuff. I think I know where my next area of research is going to be for a while. I was screwing around with some game development in my spare time, and I finally realized (as the UNIX type I am) writing GUI's bore me and I want to get back to my math/engineering type origins.

    A fine example too. I still think it's a little scary when the inputs are not neccessarily mathematical (i.e. "octagon edge detectors", as input to the "stop sign detector" problem), but I need to tackle the essential mathematical problems first to get a better understanding of the fundamentals. After all, I know how edge detectors are written, and finding octagons can be a neural net that would feed ANOTHER neural net, used to determine where the octagon was a stop sign.

    Cool on so many levels. Thanks again. Now I have motivation! (Umh, flyingmoose, you need to get back to work...)