On 2020-12-28, Jeff Barnett <jbb@notatt.com> wrote:

> An example of the issues that might stem from a single symptom: Patient
> is coughing over a period of time. Things to considered are throat
> infection, flu like, sinus drip, medicine side effect, reflux,
> allergies, asthma, COPD, certain heart problems, and more. (This list of
> potential problems for a very common symptom should give your idea of a
> little script a problem.) Proper "taking of the patient" as the
> interview is called, tries to shortly get to the most common issues and
> try some easy remedy. If that doesn't work referrals various specialists
> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
> cardiologist. Oh yes, you also need to know side effects of 1000's of
> medicines - I'd say that the typical physician knows hundreds by heart
> and of course has access to appropriate databases.
>

You'd think revealing drug contraindications would be one domain for
which computer software might be quite effective.

BTW, it's Harry *Pople* (only one P).

On 5/23/2021 3:18 AM, Curt wrote:
> On 2020-12-28, Jeff Barnett <jbb@notatt.com> wrote:
>
>> An example of the issues that might stem from a single symptom: Patient
>> is coughing over a period of time. Things to considered are throat
>> infection, flu like, sinus drip, medicine side effect, reflux,
>> allergies, asthma, COPD, certain heart problems, and more. (This list of
>> potential problems for a very common symptom should give your idea of a
>> little script a problem.) Proper "taking of the patient" as the
>> interview is called, tries to shortly get to the most common issues and
>> try some easy remedy. If that doesn't work referrals various specialists
>> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
>> cardiologist. Oh yes, you also need to know side effects of 1000's of
>> medicines - I'd say that the typical physician knows hundreds by heart
>> and of course has access to appropriate databases.

If I remember correctly, this was in response to someone who thought
that a good "medic" program could be written in a 100 or so lines of a
script language that included the medical knowledge. This was my "Don't"
be ridiculous!" response.

> You'd think revealing drug contraindications would be one domain for
> which computer software might be quite effective.

You might be correct. However, the amount of work to organize and create
that software might be much more than initially expected. Simple reasons
for avoiding a medicine are simple to list, e.g., don't take drug x and
y at the same time. However, more complicated contraindications might
involve observed reactions and need lab data as part of the decision
process. I will note that the drug prescription component of the MYCIN
system was not coded rule based; rather, it was an ad hoc blob of code.
The stated reason was that the drug selection was too detailed and
finicky (my words). I'm basing my conclusion on the hunch that
determining indication and contraindication are equally hard problems.

> BTW, it's Harry *Pople* (only one P).

I'd be surprised if that was my only typo/mistake.

BTW I'm not a medical professional but have been involved in much AI
work during my career so take what I say with a grain of salt. A long
time ago, INTERNIST and MYCIN appeared and I (and many many other AI
types) read a bunch of medical related papers and books as part of our
"ongoing learning".
--
Jeff Barnett

On Sunday, May 23, 2021 at 2:19:01 AM UTC-7, Curt wrote:

> You'd think revealing drug contraindications would be one domain for
> which computer software might be quite effective.

Stanford University did at one time have a pharmacy system that would
flag potential drug interactions for patients.

One of the takeaways was that it was critical that the system not block
dispensing drugs even if a severe negative interaction was detected.
Blocking was the initial action but that was removed because of physician
complaints that it was interfering with care. That was because the
pharmacy did not necessarily have the full information. Such as a decision
to change drugs, so that the potentially interacting drugs were not, in fact,
both being given. But that information would not be communicated to the
pharmacy, since it wasn't like they would be able to take the drugs back
once dispensed.

But once the system was redesigned to print warnings, it was embraced
as a good backstop / reminder to the physician who would then take
the appropriate action, but without a robot preventing the doc from doing
what was needed.

On 2021-05-24, Tom Russ <taruss@google.com> wrote:
>
> But once the system was redesigned to print warnings, it was embraced
> as a good backstop / reminder to the physician who would then take
> the appropriate action, but without a robot preventing the doc from doing
> what was needed.

It grows pretty complicated pretty quickly, as Jeffrey pointed out, but
the sheer quantity of over-the-counter and prescription drugs, and the
scores of new medicinal products being approved and added to the
pharmacopoeia yearly, makes it impossible for a physician to remember
all of even the most straightforward "don't take A with B" kind of
injunctions. Here, software could be helpful (and already exists,
apparently). But writing a truly "intelligent" program of this sort
would be doubtless arduous at best and is left as an exercise for the
reader.

:-)

On 5/25/2021 2:31 AM, Curt wrote:
> On 2021-05-24, Tom Russ <taruss@google.com> wrote:
>>
>> But once the system was redesigned to print warnings, it was embraced
>> as a good backstop / reminder to the physician who would then take
>> the appropriate action, but without a robot preventing the doc from doing
>> what was needed.
>
> It grows pretty complicated pretty quickly, as Jeffrey pointed out, but
> the sheer quantity of over-the-counter and prescription drugs, and the
> scores of new medicinal products being approved and added to the
> pharmacopoeia yearly, makes it impossible for a physician to remember
> all of even the most straightforward "don't take A with B" kind of
> injunctions. Here, software could be helpful (and already exists,
> apparently). But writing a truly "intelligent" program of this sort
> would be doubtless arduous at best and is left as an exercise for the
> reader.
>
> :-)
BTW, many medical professionals, including, M.D.s are deferring to your
friendly local pharmacist to do the checking now a days. I think that
parts of their education and continuing education requirements include
drug interactions, etc. I know that isn't the whole ball of wax and that
pharmacist don't have access to your lab work or patient history so they
are working partially blind.

Question: I sign by messages "Jeff" so where did the (correct" Jeffery
come from?
--
Jeff Barnett

On 2021-05-25, Jeff Barnett <jbb@notatt.com> wrote:
>
> Question: I sign by messages "Jeff" so where did the (correct" Jeffery
> come from?

Someone posted a link to some of your published papers (where I gleaned
the full name Jeffrey A. Barnett) to establish your credibility in
relation to a person with whom you were in discussion several months
ago (as I've revived a moribund thread).

On 5/25/2021 1:54 PM, Curt wrote:
> On 2021-05-25, Jeff Barnett <jbb@notatt.com> wrote:
>>
>> Question: I sign by messages "Jeff" so where did the (correct" Jeffery
>> come from?
>
> Someone posted a link to some of your published papers (where I gleaned
> the full name Jeffrey A. Barnett) to establish your credibility in
> relation to a person with whom you were in discussion several months
> ago (as I've revived a moribund thread).

And you are still talking to me? I'm flattered!
--
Jeff Barnett

On 2021-05-25, Jeff Barnett <jbb@notatt.com> wrote:
> On 5/25/2021 1:54 PM, Curt wrote:
>> On 2021-05-25, Jeff Barnett <jbb@notatt.com> wrote:
>>>
>>> Question: I sign by messages "Jeff" so where did the (correct" Jeffery
>>> come from?
>>
>> Someone posted a link to some of your published papers (where I gleaned
>> the full name Jeffrey A. Barnett) to establish your credibility in
>> relation to a person with whom you were in discussion several months
>> ago (as I've revived a moribund thread).
>
> And you are still talking to me? I'm flattered!

I'm easily impressed.

;-)

In article <slrnsak7g0.2b0.curty@einstein.electron.org>,
Curt <curty@free.fr> wrote:
>On 2020-12-28, Jeff Barnett <jbb@notatt.com> wrote:
>
>> An example of the issues that might stem from a single symptom: Patient
>> is coughing over a period of time. Things to considered are throat
>> infection, flu like, sinus drip, medicine side effect, reflux,
>> allergies, asthma, COPD, certain heart problems, and more. (This list of
>> potential problems for a very common symptom should give your idea of a
>> little script a problem.) Proper "taking of the patient" as the
>> interview is called, tries to shortly get to the most common issues and
>> try some easy remedy. If that doesn't work referrals various specialists
>> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
>> cardiologist. Oh yes, you also need to know side effects of 1000's of
>> medicines - I'd say that the typical physician knows hundreds by heart
>> and of course has access to appropriate databases.
>>

A homeopath would laugh his arse off about such simplistic treatment
of a sympton. Also no practitioner would forego further questions, and
just pick arbitrarily from pulmonary, ENT, gastroenterologist, allergy
specialist, cardiologist.

Groetjes Albert
--
"in our communism country Viet Nam, people are forced to be
alive and in the western country like US, people are free to
die from Covid 19 lol" duc ha
albert@spe&ar&c.xs4all.nl &=n http://home.hccnet.nl/a.w.m.van.der.horst

On 2021-05-28, albert@cherry.(none) (albert) <albert@cherry> wrote:
> In article <slrnsak7g0.2b0.curty@einstein.electron.org>,
> Curt <curty@free.fr> wrote:
>>> An example of the issues that might stem from a single symptom: Patient
>>> is coughing over a period of time. Things to considered are throat
>>> infection, flu like, sinus drip, medicine side effect, reflux,
....

> A homeopath would laugh his arse off about such simplistic treatment
> of a sympton. Also no practitioner would forego further questions, and
> just pick arbitrarily from pulmonary, ENT, gastroenterologist, allergy
> specialist, cardiologist.

There are also those who attribute the right symptom to the wrong
patient, if you catch my drift.

Some entity, AKA Curt <curty@free.fr>,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)

> On 2021-05-28, albert@cherry.(none) (albert) <albert@cherry> wrote:
>> In article <slrnsak7g0.2b0.curty@einstein.electron.org>,
>> Curt <curty@free.fr> wrote:
>>>> An example of the issues that might stem from a single symptom: Patient
>>>> is coughing over a period of time. Things to considered are throat
>>>> infection, flu like, sinus drip, medicine side effect, reflux,
> ...
>
>> A homeopath would laugh his arse off about such simplistic treatment
>> of a sympton. Also no practitioner would forego further questions, and
>> just pick arbitrarily from pulmonary, ENT, gastroenterologist, allergy
>> specialist, cardiologist.
>
> There are also those who attribute the right symptom to the wrong
> patient, if you catch my drift.
>

To stop smoking or even uying etter quality tobacco might do the tick too

CC
--

Any marginally usable programming language approaches an ill
defined barely usable re-implementation of half of common-lisp

On Monday, May 24, 2021 at 3:26:47 AM UTC+10, Jeff Barnett wrote:
> On 5/23/2021 3:18 AM, Curt wrote:
> > On 2020-12-28, Jeff Barnett <j...@notatt.com> wrote:
> >
> >> An example of the issues that might stem from a single symptom: Patient
> >> is coughing over a period of time. Things to considered are throat
> >> infection, flu like, sinus drip, medicine side effect, reflux,
> >> allergies, asthma, COPD, certain heart problems, and more. (This list of
> >> potential problems for a very common symptom should give your idea of a
> >> little script a problem.) Proper "taking of the patient" as the
> >> interview is called, tries to shortly get to the most common issues and
> >> try some easy remedy. If that doesn't work referrals various specialists
> >> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
> >> cardiologist. Oh yes, you also need to know side effects of 1000's of
> >> medicines - I'd say that the typical physician knows hundreds by heart
> >> and of course has access to appropriate databases.
> If I remember correctly, this was in response to someone who thought
> that a good "medic" program could be written in a 100 or so lines of a
> script language that included the medical knowledge. This was my "Don't"
> be ridiculous!" response.

Lets see:

mechanic
-remove at
-assert at mechanic
-mech

mech
-points P
-echo POINTS
-print P
-echo newline
-echo FAULTS
-echo newline
-showfaults
-echo newline
-echo newline
-at B
-echo you are at
-print B
-echo newline
-echo you can
-printrooms5 B
-echo newline
-echo you can
-printgrab B
-echo newline
-echo you can
-printuse5

faulty O
-echo faulty
-print O
-at B
-remove in B fault
-assert in B fault
-remove faults B O
-assert faults B O
-echo newline
-echo newline
-mech

action inspection O
-echo inspect
-print O
-echo newline
-echo newline
-button check O
-button faulty O

showfaults
-faults C F
-print C
-print F
-clear C
-clear F
-echo newline
-next
-showfaults

con mechanic starter
con starter mechanic
con mechanic engineTemp
con engineTemp mechanic
con east forest
con forest east
con spark fuelLine
con fuelLine spark
con base test
con test base
con battery fuses
con fuses battery
con starter ignition
con ignition starter
con engineTemp radiator
con radiator engineTemp
con north base
con base north
con mechanic base
con base mechanic
con mechanic fuel
con fuel mechanic
con mechanic battery
con battery mechanic
con mechanic engTemp
con engTemp mechanic
con radiator engTemp
con engTemp radiator
con mechanic spark
con spark mechanic
con fuseBox battery
con battery batTerminals
con batTerminals battery
con fuseBox batTerminals
con batTerminals fuseBox

needs about 100 more records for a mechanic expert system (to do a 80 points car service)

On Monday, June 21, 2021 at 12:35:02 PM UTC+10, Graham Cooper wrote:
> On Monday, May 24, 2021 at 3:26:47 AM UTC+10, Jeff Barnett wrote:
> > On 5/23/2021 3:18 AM, Curt wrote:
> > > On 2020-12-28, Jeff Barnett <j...@notatt.com> wrote:
> > >
> > >> An example of the issues that might stem from a single symptom: Patient
> > >> is coughing over a period of time. Things to considered are throat
> > >> infection, flu like, sinus drip, medicine side effect, reflux,
> > >> allergies, asthma, COPD, certain heart problems, and more. (This list of
> > >> potential problems for a very common symptom should give your idea of a
> > >> little script a problem.) Proper "taking of the patient" as the
> > >> interview is called, tries to shortly get to the most common issues and
> > >> try some easy remedy. If that doesn't work referrals various specialists
> > >> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
> > >> cardiologist. Oh yes, you also need to know side effects of 1000's of
> > >> medicines - I'd say that the typical physician knows hundreds by heart
> > >> and of course has access to appropriate databases.
> > If I remember correctly, this was in response to someone who thought
> > that a good "medic" program could be written in a 100 or so lines of a
> > script language that included the medical knowledge. This was my "Don't"
> > be ridiculous!" response.
> Lets see:
>
>
> mechanic
> -remove at
> -assert at mechanic
> -mech
>
> mech
> -points P
> -echo POINTS
> -print P
> -echo newline
> -echo FAULTS
> -echo newline
> -showfaults
> -echo newline
> -echo newline
> -at B
> -echo you are at
> -print B
> -echo newline
> -echo you can
> -printrooms5 B
> -echo newline
> -echo you can
> -printgrab B
> -echo newline
> -echo you can
> -printuse5
>
> faulty O
> -echo faulty
> -print O
> -at B
> -remove in B fault
> -assert in B fault
> -remove faults B O
> -assert faults B O
> -echo newline
> -echo newline
> -mech
>
> action inspection O
> -echo inspect
> -print O
> -echo newline
> -echo newline
> -button check O
> -button faulty O
>
> showfaults
> -faults C F
> -print C
> -print F
> -clear C
> -clear F
> -echo newline
> -next
> -showfaults
>
>
> con mechanic starter
> con starter mechanic
> con mechanic engineTemp
> con engineTemp mechanic
> con east forest
> con forest east
> con spark fuelLine
> con fuelLine spark
> con base test
> con test base
> con battery fuses
> con fuses battery
> con starter ignition
> con ignition starter
> con engineTemp radiator
> con radiator engineTemp
> con north base
> con base north
> con mechanic base
> con base mechanic
> con mechanic fuel
> con fuel mechanic
> con mechanic battery
> con battery mechanic
> con mechanic engTemp
> con engTemp mechanic
> con radiator engTemp
> con engTemp radiator
> con mechanic spark
> con spark mechanic
> con fuseBox battery
> con battery batTerminals
> con batTerminals battery
> con fuseBox batTerminals
> con batTerminals fuseBox
>
>
> needs about 100 more records for a mechanic expert system (to do a 80 points car service)

a few more records for the DIRECTED ACYCLIC GRAPH of faults

in engineTemp tempGage
in spark sparkPlugs

in spark fault
in engineTemp fault
in fuses fuse

in mechanic falcon
in radiator water
in radiator fault
in fuseBox fuse
in fuseBox fuse
in engTemp tempGage
in fuel fuelGage
in batTerminals looseTerminal
in batTerminals fault

in mechanic fault
in mechanic inspection

http://dollgirl.com/EXPERT-SYSTEM.png <<<<<<<<<< PIC

On 6/20/2021 8:39 PM, Graham Cooper wrote:
> On Monday, June 21, 2021 at 12:35:02 PM UTC+10, Graham Cooper wrote:
>> On Monday, May 24, 2021 at 3:26:47 AM UTC+10, Jeff Barnett wrote:
>>> On 5/23/2021 3:18 AM, Curt wrote:
>>>> On 2020-12-28, Jeff Barnett <j...@notatt.com> wrote:
>>>>
>>>>> An example of the issues that might stem from a single symptom: Patient
>>>>> is coughing over a period of time. Things to considered are throat
>>>>> infection, flu like, sinus drip, medicine side effect, reflux,
>>>>> allergies, asthma, COPD, certain heart problems, and more. (This list of
>>>>> potential problems for a very common symptom should give your idea of a
>>>>> little script a problem.) Proper "taking of the patient" as the
>>>>> interview is called, tries to shortly get to the most common issues and
>>>>> try some easy remedy. If that doesn't work referrals various specialists
>>>>> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
>>>>> cardiologist. Oh yes, you also need to know side effects of 1000's of
>>>>> medicines - I'd say that the typical physician knows hundreds by heart
>>>>> and of course has access to appropriate databases.
>>> If I remember correctly, this was in response to someone who thought
>>> that a good "medic" program could be written in a 100 or so lines of a
>>> script language that included the medical knowledge. This was my "Don't"
>>> be ridiculous!" response.
>> Lets see:
>>
>>
>> mechanic
>> -remove at
>> -assert at mechanic
>> -mech
>>
>> mech
>> -points P
>> -echo POINTS
>> -print P
>> -echo newline
>> -echo FAULTS
>> -echo newline
>> -showfaults
>> -echo newline
>> -echo newline
>> -at B
>> -echo you are at
>> -print B
>> -echo newline
>> -echo you can
>> -printrooms5 B
>> -echo newline
>> -echo you can
>> -printgrab B
>> -echo newline
>> -echo you can
>> -printuse5
>>
>> faulty O
>> -echo faulty
>> -print O
>> -at B
>> -remove in B fault
>> -assert in B fault
>> -remove faults B O
>> -assert faults B O
>> -echo newline
>> -echo newline
>> -mech
>>
>> action inspection O
>> -echo inspect
>> -print O
>> -echo newline
>> -echo newline
>> -button check O
>> -button faulty O
>>
>> showfaults
>> -faults C F
>> -print C
>> -print F
>> -clear C
>> -clear F
>> -echo newline
>> -next
>> -showfaults
>>
>>
>> con mechanic starter
>> con starter mechanic
>> con mechanic engineTemp
>> con engineTemp mechanic
>> con east forest
>> con forest east
>> con spark fuelLine
>> con fuelLine spark
>> con base test
>> con test base
>> con battery fuses
>> con fuses battery
>> con starter ignition
>> con ignition starter
>> con engineTemp radiator
>> con radiator engineTemp
>> con north base
>> con base north
>> con mechanic base
>> con base mechanic
>> con mechanic fuel
>> con fuel mechanic
>> con mechanic battery
>> con battery mechanic
>> con mechanic engTemp
>> con engTemp mechanic
>> con radiator engTemp
>> con engTemp radiator
>> con mechanic spark
>> con spark mechanic
>> con fuseBox battery
>> con battery batTerminals
>> con batTerminals battery
>> con fuseBox batTerminals
>> con batTerminals fuseBox
>>
>>
>> needs about 100 more records for a mechanic expert system (to do a 80 points car service)
>
>
> a few more records for the DIRECTED ACYCLIC GRAPH of faults
>
>
>
> in engineTemp tempGage
> in spark sparkPlugs
>
> in spark fault
> in engineTemp fault
> in fuses fuse
>
> in mechanic falcon
> in radiator water
> in radiator fault
> in fuseBox fuse
> in fuseBox fuse
> in engTemp tempGage
> in fuel fuelGage
> in batTerminals looseTerminal
> in batTerminals fault
>
> in mechanic fault
> in mechanic inspection
>
>
>
> http://dollgirl.com/EXPERT-SYSTEM.png <<<<<<<<<< PIC

That took a month? I see it can't even recognize a front end caved in
from a collision, or how to change a spark plug, or what grade oil to
use, or tire pressure for dozens of models and dozens of tire choices.
Have you every changed an engine gasket or lapped its valves? Read a
text book on these things and go to trade school for a while then come
back and we will talk.

Oh, by the way, medicine is one hell of a lot harder.

I'm curious: What do you get out of these futile attempts. If you are
really a smart guy, pick a field that actually interests you and study
it for a while. You are much more likely to actually do something note
worthy or recognized as clever if you base it on some fundamental
insight. Using script languages as you are doing simply takes ignorance
and prints it on paper without any knowledge added.
--
Jeff Barnett

On Monday, June 21, 2021 at 3:27:37 PM UTC+10, Jeff Barnett wrote:
> On 6/20/2021 8:39 PM, Graham Cooper wrote:
> > On Monday, June 21, 2021 at 12:35:02 PM UTC+10, Graham Cooper wrote:
> >> On Monday, May 24, 2021 at 3:26:47 AM UTC+10, Jeff Barnett wrote:
> >>> On 5/23/2021 3:18 AM, Curt wrote:
> >>>> On 2020-12-28, Jeff Barnett <j...@notatt.com> wrote:
> >>>>
> >>>>> An example of the issues that might stem from a single symptom: Patient
> >>>>> is coughing over a period of time. Things to considered are throat
> >>>>> infection, flu like, sinus drip, medicine side effect, reflux,
> >>>>> allergies, asthma, COPD, certain heart problems, and more. (This list of
> >>>>> potential problems for a very common symptom should give your idea of a
> >>>>> little script a problem.) Proper "taking of the patient" as the
> >>>>> interview is called, tries to shortly get to the most common issues and
> >>>>> try some easy remedy. If that doesn't work referrals various specialists
> >>>>> might be next: pulmonary, ENT, gastroenterologist, allergy specialist,
> >>>>> cardiologist. Oh yes, you also need to know side effects of 1000's of
> >>>>> medicines - I'd say that the typical physician knows hundreds by heart
> >>>>> and of course has access to appropriate databases.
> >>> If I remember correctly, this was in response to someone who thought
> >>> that a good "medic" program could be written in a 100 or so lines of a
> >>> script language that included the medical knowledge. This was my "Don't"
> >>> be ridiculous!" response.
> >> Lets see:
> >>
> >>
> >> mechanic
> >> -remove at
> >> -assert at mechanic
> >> -mech
> >>
> >> mech
> >> -points P
> >> -echo POINTS
> >> -print P
> >> -echo newline
> >> -echo FAULTS
> >> -echo newline
> >> -showfaults
> >> -echo newline
> >> -echo newline
> >> -at B
> >> -echo you are at
> >> -print B
> >> -echo newline
> >> -echo you can
> >> -printrooms5 B
> >> -echo newline
> >> -echo you can
> >> -printgrab B
> >> -echo newline
> >> -echo you can
> >> -printuse5
> >>
> >> faulty O
> >> -echo faulty
> >> -print O
> >> -at B
> >> -remove in B fault
> >> -assert in B fault
> >> -remove faults B O
> >> -assert faults B O
> >> -echo newline
> >> -echo newline
> >> -mech
> >>
> >> action inspection O
> >> -echo inspect
> >> -print O
> >> -echo newline
> >> -echo newline
> >> -button check O
> >> -button faulty O
> >>
> >> showfaults
> >> -faults C F
> >> -print C
> >> -print F
> >> -clear C
> >> -clear F
> >> -echo newline
> >> -next
> >> -showfaults
> >>
> >>
> >> con mechanic starter
> >> con starter mechanic
> >> con mechanic engineTemp
> >> con engineTemp mechanic
> >> con east forest
> >> con forest east
> >> con spark fuelLine
> >> con fuelLine spark
> >> con base test
> >> con test base
> >> con battery fuses
> >> con fuses battery
> >> con starter ignition
> >> con ignition starter
> >> con engineTemp radiator
> >> con radiator engineTemp
> >> con north base
> >> con base north
> >> con mechanic base
> >> con base mechanic
> >> con mechanic fuel
> >> con fuel mechanic
> >> con mechanic battery
> >> con battery mechanic
> >> con mechanic engTemp
> >> con engTemp mechanic
> >> con radiator engTemp
> >> con engTemp radiator
> >> con mechanic spark
> >> con spark mechanic
> >> con fuseBox battery
> >> con battery batTerminals
> >> con batTerminals battery
> >> con fuseBox batTerminals
> >> con batTerminals fuseBox
> >>
> >>
> >> needs about 100 more records for a mechanic expert system (to do a 80 points car service)
> >
> >
> > a few more records for the DIRECTED ACYCLIC GRAPH of faults
> >
> >
> >
> > in engineTemp tempGage
> > in spark sparkPlugs
> >
> > in spark fault
> > in engineTemp fault
> > in fuses fuse
> >
> > in mechanic falcon
> > in radiator water
> > in radiator fault
> > in fuseBox fuse
> > in fuseBox fuse
> > in engTemp tempGage
> > in fuel fuelGage
> > in batTerminals looseTerminal
> > in batTerminals fault
> >
> > in mechanic fault
> > in mechanic inspection
> >
> >
> >
> > http://dollgirl.com/EXPERT-SYSTEM.png <<<<<<<<<< PIC
> That took a month? I see it can't even recognize a front end caved in

you could add FRAME_DAMAGE as a main menu goto option

con mechanic starter
con mechanic engineTemp
con mechanic fuel
con mechanic battery
con mechanic frameDamage

in frameDamage bonnet
in frameDamage frontDoor
in frameDamage backDoor
in frameDamage hatch
in frameDamage bumpers

> from a collision, or how to change a spark plug, or what grade oil to
> use, or tire pressure for dozens of models and dozens of tire choices.
> Have you every changed an engine gasket or lapped its valves? Read a
> text book on these things and go to trade school for a while then come
> back and we will talk.
>
> Oh, by the way, medicine is one hell of a lot harder.
>
> I'm curious: What do you get out of these futile attempts. If you are
> really a smart guy, pick a field that actually interests you and study
> it for a while. You are much more likely to actually do something note
> worthy or recognized as clever if you base it on some fundamental
> insight. Using script languages as you are doing simply takes ignorance
> and prints it on paper without any knowledge added.

the objective isnt a productive profit making software solution for end users
but helping a collaborative approach with open source
as big corporation AIs are relatively fruitless

ASIMO just passes a robot test but no lingo or anything