Well, that's embarrassing . . . . flame somebody and realize that you got part of it wrong yourself . . . . ;-) ______________________________________________________________________________________
Mark> If you can't prevent a program from sucking up 100% of your CPU, you aren't competent to be working at this level. There are *all sorts* of ways to stop evil behavior like this to include: a.. pre-allocating memory to yourself (or your AI) before firing up the offending programming b.. replacing the operating system pointers to the memory allocation routines to your routines which will then lie to the offender about the amount of memory available c.. working on multiple linked boxes Duh. Nothing like proposing memory solutions for a CPU problem . . . . ;-) How about the easily applicable solutions (without any work on your part) of running multiple virtual machines on the same box OR (as proposed before) multiple linked boxes. ----- Original Message ----- From: Mark Waser To: [email protected] Sent: Monday, April 14, 2008 10:48 AM Subject: Re: [agi] Comments from a lurker... Steve > Perhaps you can relate your own experiences in this area. Argument from Authority . . . . but what the heck . . . . :-) Earliest scientific computing papers (one from the science side, one from the computing side) Computer Modeling of Muscle Phosphofructokinase Kinetics Journal of Theoretical Biology, Volume 103, Issue 2, 21 July 1983, Pages 295-312 Mark R. Waser, Lillian Garfinkel, Michael C. Kohn and David Garfinkel A Computer Program for Analyzing Enzyme Kinetic Data Using Graphical Display and Statistical Analysis Computers and Biomedical Research, Volume 17, Issue 3, June 1984, Pages 289-301 Serge D. Schremmer, Mark R. Waser, Michael C. Kohn and David Garfinkel Hardware Integration Project - True Omni-font OCR device (1983-1984) Developed software turning any Apple IIe and any fax machine into a true Omni-font OCR reader pages were solved as cryptograms so even *random* fonts were interpretable used 6502 assembly; unloaded the Apple IIe operating system as necessary (memory problems? what memory problems?) AI Project - Case Method Credit Expert System Shell & Builder (1984-1985) Developed in Pascal for Citicorp's FastFinance Leasing System Used by technophobic executives without any problems AI Project - Expert System for Army Logistics Procurement (1986-1987) Developed for/Deployed at Fort Belvoir, VA; Presented at Army Logistics Conference in Williamsburg Part of the Project Manager's Support System AI Project - Project Impact Advisor (1986-1987) Rewrote boss's prototype system implemented in Lisp on special hardware as a PC-based Prolog system Part of the Project Manager's Support System AI/Hardware Project - Neural Network for Diagnosing Thallium Images of the Heart (1987-1988) Successfully convinced top Air Force brass that Air Force doctors were misdiagnosing test pilot check-up images Used Sigma Neural Network hardware boards Hardware Project - Fax Network Switch (1990-1991) Developed for/Deployed by the Australian Government/Embassy for all traffic between Canberra and Washington Subsequently sold to Sony Created multiple terminate-and-stay-resident programs to provide simultaneous 16-fax and dual T1-modem capability under MS-DOS Used Brooktrout 4-port fax boards Hardware Project - Secure Telephone Unit (1991-1992) Developed initial prototype marrying COTS 80286 motherboard, modem, and TI TMS C32000 FPU with custom hardware and software Enhanced and integrated commercially available TI TMS C32000 software for various voice codecs Developed all control software (80286 assembly) Developed all software for debugging custom integrating hardware developed by other company employees Hmmm . . . that's not even ten years with over fifteen to go . . . and I'm boring *myself* to tears despite skipping a bunch of non-relevant stuff . . . . ;-) Mark>> Good thing that you're smarter than that and know how to trash a machine so your stuff will work. Steve> Given that apparently no one else has been able to make commercial speech-to-text work with real-time AI, I'll accept that as a complement. You shouldn't have. It was pure sarcasm. You need to look harder at what is available out there. Real-time speech-to-text is not the problem (though the accuracy rate is still below what is to be preferred -- a problem which your solution does *NOT* address). Fitting real-time speech-to-text into a small enough, friendly enough footprint to work with real-time AI is not the problem (although *you* do seem to be having problems doing it with a *GOOD* engineering solution). Coming up with a worthwhile AI is the problem BUT I haven't seen any sign of such a thing from you. Steve> It is unclear what happened for you to make your comments in the tone that you used. On first glance it appears that you simply didn't carefully read the article. For example, did you notice that Nuance actually has a patent on how they suck up 100.0% of the CPU, leaving nothing for concurrent AI programs? How about constructively addressing the technical ISSUES instead of sounding like an idiot by making snide comments. If you can't prevent a program from sucking up 100% of your CPU, you aren't competent to be working at this level. There are *all sorts* of ways to stop evil behavior like this to include: a.. pre-allocating memory to yourself (or your AI) before firing up the offending programming b.. replacing the operating system pointers to the memory allocation routines to your routines which will then lie to the offender about the amount of memory available c.. working on multiple linked boxes The kludges that you are resorting to are just plain *BAD* engineering. There are *ALWAYS* clean work-arounds -- if you're competent enough to find them. Steve>>> Then there is the fact that Dr. Eliza operates according to principles that aren't taught in any school and would be unfamiliar without some external education. Mark>> Sounds like voodoo to me -- unless you have all this stuff written up so that you can provide this education (and the education can be validated). Didn't think so. Steve> Perhaps you missed the fact that I already posted that I have several articles that I would gladly send to anyone who requested them. However, there ARE limits to just how much can be packed into a published article. One of them even secured special permission to exceed the maximum length limit, when the WORLDCOMP conference committee couldn't suggest ANY part of it that could be omitted without damaging the rest of it. Perhaps I didn't miss the fact that you didn't send me what I requested. Perhaps I noticed that what you did send me had nothing to do with AI. Perhaps I noticed that what you sent me was not what I would call competent. Steve> I am new here, having only made one posting and answered queries to that posting. However, if this were MY group, I would remove you as a member for making such snide comments rather than simply explaining your issues and asking for anything you see is missing, like explanatory articles. Okay. Is this e-mail clearer? The snide comments were because your arrogant initial presentation and claims were followed up by an off-topic "paper" that was inexcusably bad (also known as -- you wasted my time). Steve> People working in AI/AGI get LOTS of derision from the rest of CS (and you certainly sound like you come from that extraction) and we certainly don't need any more here, on what should be a safe forum to express our ideas. Not all people working in AI/AGI get the derision. Just the crackpots. For the record, my MSE is in Artificial Intelligence and I've done doctoral work in Machine Learning and Human Decision-Making. So I'm definitely an AI/AGI person -- but the source of the derision is my ENGINEERING side (which is necessary for competent AI/AGI). If your ideas are good enough, you shouldn't need a safe forum. If you avoid sounding like an arrogant know-it-all, this *IS* a safe forum. You've merely been a *TROLL* and gotten the appropriate response. Thanks for playing but we have no parting gifts for you. ------------------------------------------------------------------------------ agi | Archives | Modify Your Subscription ------------------------------------------- agi Archives: http://www.listbox.com/member/archive/303/=now RSS Feed: http://www.listbox.com/member/archive/rss/303/ Modify Your Subscription: http://www.listbox.com/member/?member_id=8660244&id_secret=98558129-0bdb63 Powered by Listbox: http://www.listbox.com
