Search

Lee D Erman

from Mountain View, CA
Age ~80

Lee Erman Phones & Addresses

  • 433 Calderon Ave, Mountain View, CA 94041 (650) 964-4443
  • 2112 Wyandotte St, Mountain View, CA 94043
  • 3094 Cowper St, Palo Alto, CA 94306 (650) 494-7881 (650) 494-7891
  • San Francisco, CA
  • Los Altos, CA
  • Los Angeles, CA
  • Santa Clara, CA

Resumes

Resumes

Lee Erman Photo 1

Massage Therapist (Primarily With Hospitalized Patients)

View page
Position:
Massage Therapist at Lucile Packard Children's Hospital, Massage Therapist at Veterans Health Administration, Palo Alto, Massage Therapist at Stanford Hospital & Clinics
Location:
San Francisco Bay Area
Industry:
Health, Wellness and Fitness
Work:
Lucile Packard Children's Hospital since 2007
Massage Therapist

Veterans Health Administration, Palo Alto since 2000
Massage Therapist

Stanford Hospital & Clinics since 1994
Massage Therapist

Mills-Peninsula Health Services 1997 - 2006
Massage Therapist
Education:
Stanford University
PhD, Computer Science
University of Michigan
B.S., Math (with Distinction)
Honor & Awards:
Elected Fellow, Association for the Advancement of Artificial Intelligence

Publications

Us Patents

Architecture For Composing Computational Modules Uniformly Across Diverse Developmental Frameworks

View page
US Patent:
49439324, Jul 24, 1990
Filed:
Apr 15, 1987
Appl. No.:
7/038872
Inventors:
Jay S. Lark - Mountain View CA
Lee D. Erman - Palo Alto CA
Michael Fehling - Mountain View CA
Frederick Hayes-Roth - Atherton CA
Assignee:
Cimflex Teknowledge Corporation - Palo Alto CA
International Classification:
G06F 1520
G06F 1518
US Classification:
364513
Abstract:
A Multi-Level Architecture for developing intelligent computer systems composes computational modules uniformly across diverse developmental framework. The modules interact via message passing and are assembled to form application-specific systems. A first level of the Multi-Level Architecture includes a cooperative operating system which provides support for message passing and resource allocation and is preferably based on a module-oriented programming (MOP) model. The first level, for example, defines a virtual machine which is mapped onto an underlying hardware and operating system environment. A second level of the Multi-Level Architecture supports a plurality of application-independent problem-solving frameworks (PSF's) or programming environments for building modules and combining modules of different frameworks into complex systems. A third level of Multi-Level Architecture includes a plurality of knowledge processing modules ranging from specialized modules to skeletal systems which provide nearly complete solutions to application problems. For building an application-specific system, domain-specific knowledge is added on top of the third level and typically a selected skeletal system is customized.

Knowledge Engineering Tool

View page
US Patent:
46583700, Apr 14, 1987
Filed:
Jun 7, 1984
Appl. No.:
6/618038
Inventors:
Lee D. Erman - Palo Alto CA
William J. Clancey - Palo Alto CA
Philip E. London - Cupertino CA
A. Carlisle Scott - Palo Alto CA
James S. Bennett - Palo Alto CA
Jay S. Lark - Palo Alto CA
Assignee:
Teknowledge, Inc. - Palo Alto CA
International Classification:
G06F 1518
US Classification:
364513
Abstract:
A tool is used for knowledge engineers for building and interpreting a knowledge base having separate portions encoding control knowledge, factual knowledge, and judgmental rules. The tool has an inference engine applying the judgmental rules according to a built-in control procedure defining discrete states or control steps during a consultation with a user. The control knowledge is encoded in an applicative and imperative language defining control actions to be executed during interruption of the built-in control procedure at specified control steps. Since the control knowledge is explicit and results in the modification of data only in a precisely defined fashion, the tool can be used to build knowledge systems that can always explain their conclusions and reasoning, and that are intelligible and modifiable. To provide transparent representation of control knowledge as well as factual knowledge, the knowledge base is preferably organized into distinct frames which include the rules; control blocks separately encoding the control knowledge; and classes which become instantiated, attributes which take on values describing the class instances, class types, legal value hierarchies, and user-defined functions, which all encode factual knowledge. The knowledge engineer may provide control blocks to be executed at the start of the consultation, after the instantiation of specified classes, when a value for a specified attribute is to be determined, after a specified attribute is determined, and upon explicit invocation by another control block.
Lee D Erman from Mountain View, CA, age ~80 Get Report