1 / 11

The Perceptual Components API & Applications

The Perceptual Components API & Applications. Gerhard Sutschet Fraunhofer IITB http://www.iitb.fraunhofer.de/servlet/is/9237/. Nikolaos Dimakis Athens Information Technology http://www.ait.gr/research/RG1/overview.asp. Towards Standardization. Problem definition

kawena
Download Presentation

The Perceptual Components API & Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Perceptual Components API& Applications Gerhard Sutschet Fraunhofer IITB http://www.iitb.fraunhofer.de/servlet/is/9237/ Nikolaos Dimakis Athens Information Technology http://www.ait.gr/research/RG1/overview.asp

  2. Towards Standardization • Problem definition • Numerous Perceptual Components • Different Vendors, Technologies, Platforms, etc. • Should work together (CHIL Vision) • Proposed Solution • Introduce a “compliant” prototype (define APIs) • Answer all basic needs of the PCs • Flexibility, adaptability, expansion

  3. Perceptual Components APIs • initialize() • Initializes the Perceptual Component • register() • Register to the IPD Knowledge Base • query() • Query KB for room specific parameters • start() • Start Perceptual Component • stop() • Stop Perceptual Component • set/getParameter() • Send/Get parameters by the consumer component

  4. Building …The CHIL Compliant Perceptual Component Scattered Parts (Ontology, Sensors, Processing, Service) Connective Interfaces Bundled Components The CHIL Compliant Perceptual Component

  5. CHIL Compliance. Does it work? • Evaluation during EC Review, May 2006 • 3 PCs (INRIA, UKA, AIT) • CHIL Ontology (IPD) • SitCom (IBM) • SmartFlow (NIST) • Components collaborated as expected

  6. Applications using the architecture • Main applications (demonstration follows) • SitCom • Memory Jog • Additional applications • The Travel Service • The Connector Service • The Recording Service

  7. Videos • Application Videos

  8. More on the APIs • PCs boot-up sequence • Load XML file with PC configuration (initialize) • Name, Vendor, Technology, type of required sensor, etc • Query the Ontology for the environment and sensors (query) • Request the ID of the required sensor (as a flow)

  9. APIs continued • PC remains in an idle state • … until awakened by the application (start) • Connect to SmartFlow • Distributes context at a given rate • Configurable by XML file • Fine-tunes performance (set/getParameter) • Frame rate, etc. • … until stopped by the application (stop)

  10. Context XML • Following a simple XML DTD Schema <!ELEMENT ChilixMessage (BodyTracker)> <!ELEMENT BodyTracker (Target)> <!ATTLIST BodyTracker tsImage CDATA #REQUIRED> <!ELEMENT Target EMPTY> <!ATTLIST Target id CDATA #REQUIRED unit CDATA #FIXED "mm" x CDATA #REQUIRED y CDATA #REQUIRED z CDATA #REQUIRED>

  11. DTD explained • The tsImage is the timestamp at which the frame was captured. • The parameters x,y,z are in millimetres and are related to the specific room configuration. • For those who wish to send additional parameters for SitCom (kind, cause, explanations, volume, confidence level), separate XML messages have to be sent. • It has been decided that only one composite message will be transmitted instead of more the one for each individual person tracked. • Finally the timestamps will be UNIX timestamps, which are commonly used and have already been used in the evaluation data.

More Related