Steve, about *** So, is anyone here interested in writing AI/AGI support software, or:
1. do you intend to use subsystems that other people write? 2. do you intend to write EVERYTHING needed to support AGI operation? 3. have you even thought about such issues? *** Any modern OSS project uses all sorts of code written by other people... As two recent examples in OpenCog -- our new "surprising pattern miner" was tested using DBPedia ... see tutorial linked from here, http://opencog.org/2015/11/pattern-miner/ -- my new proposal for putting deep learning perception in OpenCog http://blog.opencog.org/2015/11/01/putting-deep-perceptual-learning-in-opencog/ would rely heavily on the Theano library http://deeplearning.net/software/theano/ made by Yoshua Bengio's machine vision group at U. Montreal Our NLP system has long relied on the link parser from Carnegie Mellon, http://www.link.cs.cmu.edu/link/ We would like to get rid of it, http://arxiv.org/abs/1401.3372 but in this proposal, we will still keep the general idea/format of the link parser, just learn the rule content instead of loading hand-coded rules For our applications of OpenCog to genomics, we use all sorts of existing OSS R scripts for data preprocessing, and resources like Gene Ontology, MSigDB, etc. To make a tool for authoring basic robot behaviors to be run in OpenCog, we're customizing an existing Javascript behavior tree authoring library, http://behavior3js.guineashots.com/ To make a type system for OpenCog's internal procedures, we may borrow code from Haskell's type system To communicate w/ robots and also w/ Minecraft, we use ROS (OSS from Willow Garage, now standard in academic robots and penetrating industry...) And many many other examples... In short, sharing components and resources is how OSS tends to work, it's already happening.... Doing this kind of sharing in a proprietary-software context is complicated and seems to basically not work well. But by going OSS, this becomes easy and natural (well, easy except for endless annoying dependency and build problems, lol ...) -- Ben G On Fri, Oct 30, 2015 at 5:00 PM, Steve Richfield <[email protected]> wrote: > I noticed a different viewpoint to my discussion regarding my startup: > > ANY major AI/AGI project is going to need pretty much the SAME support > software, regardless of whether it is weak AI or AGI. Many of the > subsystems I was intending on building are the SAME subsystems anyone else > developing other AI/AGI systems will need. For example: > > 1. A web crawler that scans the Internet and presents postings along > with metadata (name, contact information, etc.) > 2. An idiom dictionary, since natural language includes SO many > idioms. You won't even be able to talk much with your AI/AGI without this. > > The early BIG money in computers was made in operating systems rather than > in applications software. I suspect the same will be the case with AI/AGI. > > So, is anyone here interested in writing AI/AGI support software, or: > > 1. do you intend to use subsystems that other people write? > 2. do you intend to write EVERYTHING needed to support AGI operation? > 3. have you even thought about such issues? > > Steve > > > > *AGI* | Archives <https://www.listbox.com/member/archive/303/=now> > <https://www.listbox.com/member/archive/rss/303/212726-deec6279> | Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > -- Ben Goertzel, PhD http://goertzel.org "The reasonable man adapts himself to the world: the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw ------------------------------------------- AGI Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-f452e424 Modify Your Subscription: https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-58d57657 Powered by Listbox: http://www.listbox.com
