From: thunk <gmkoller@...>
Date: 2010-04-11T12:10:07+09:00
Subject: Re: The Ruid Concept, with question

On Apr 10, 8:00 pm, H- 16 <s1ay3...@gmail.com> wrote:
> thunk wrote:
> >http://trevoke.net/ruids/index.php?topic=5.0
>
> > Pretty much says it.   It takes a part in a set of like classes
> > (therefore the swarm).  There are multiple Types but the "standard"
> > type makes a few assertions, messages get attached (by the expert) and
> > a conclusion gets reached (5 sections / 5 DSLs)
>
> > The "big secret" to making some basic sense of the conclusions is that
> > each Ruid has basic "categorization" - done into the Header section of
> > the Ruid.
>
> > THEY are simple - so they can be authored using nothing more than a
> > "picklist" driven "expert session" which would be key part of a DEMO
> > system (and must be Web based).   And was done in WEE and tested and
> > so on.
>
> > The SWARM_READER is in charge of making sense of the "Image" made
> > after the Ruids contact "Screens".   Screens are about presenting
> > information (like a patient record) to the Ruid.   The Ru'id "docks"
> > with a "HelperClass" - the HelperClass is something also used by
> > Ruleby (the author is happy to report).
>
> > The "HelperClasses" is where a "Ru'id Programmer must spend his/her
> > effort.
>
> > =================================
>
> Ok, so what's the entire point of the program? What EXACTLY does it do?
> And can you give us even a LITTLE code. If you can't you can't be
> helped.
>
> P.S. If you haven't noticed I'm just about the only one giving you a
> chance right about now. I wouldn't take that kindness for granted. Nuff
> said...
> --
> Posted viahttp://www.ruby-forum.com/.


There is some general utility for certain problem types.

Just about "any" report / data processing Could be done in a system
like this but that would make very little sense!  However there are
several easy to represent problem types where the system would present
many significant advantages due to the fact that the Ru'id units can
be contributed from "outside" the system (via an expert web session).
The simplest set to recognize, imho, is "the shopping basket" (system)
situation.  Ru'ids could tear apart everything and anything in a
shopping basket and make sense of what there is to make sense of (eg
if it is a single computer they could give you a report on peer
systems, tell you your cables are too small, and that you may be
forgetting the CPU heat sink grease.) That was the ORIGINAL idea - 3
years ago.


http://trevoke.net/ruids/index.php?topic=3.0