An uncoupled interface to soar using sml
This presentation is the property of its rightful owner.
Sponsored Links
1 / 6

An Uncoupled Interface to Soar using SML PowerPoint PPT Presentation


  • 139 Views
  • Uploaded on
  • Presentation posted in: General

An Uncoupled Interface to Soar using SML. Pearson, Marinier, Stokes Dunham, Voigt. System Architecture. Soar Kernel. Soar 8.6 Kernel (C). gSKI. Higher-level Interface (C++). Encodes/Decodes function calls and responses in XML (C++). ElementXML. SML. Soar Markup Language.

Download Presentation

An Uncoupled Interface to Soar using SML

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


An uncoupled interface to soar using sml

An Uncoupled Interface to Soar using SML

Pearson, Marinier, Stokes Dunham, Voigt


System architecture

System Architecture

Soar Kernel

Soar 8.6 Kernel (C)

gSKI

Higher-level Interface (C++)

Encodes/Decodes function calls and responses in XML (C++)

ElementXML

SML

Soar Markup Language

Encodes/Decodes function calls and responses in XML (C++)

ElementXML

Client-side gSKI interface (C++, with wrapper for Java, etc)

Client gSKI

Application

Application (any language)


Features

Features

  • All the advantages of gSKI

  • Embedded or socket connection

  • Multiple language support for applications

  • Tools should “just work” with new versions

    • No need to recompile or relink

    • Graceful degradation of functionality


Why sml gski

Why SML + gSKI?

  • Why not SGIO?

    • SGIO is not gSKI

  • Why not C API

    • Not robust, poor encapsulation

    • Doesn’t hide enough details from user

    • Not much easier than directly working with raw kernel calls


Status

Status

  • Identified 26 common gSKI functions for environments (Tic-Tac-Toe, Eaters, TankSoar, and even UT)

  • Kernel-side ElementXML support mostly finished

  • Client-side gSKI layer in progress

  • Socket implementation in progress


Future

Future

  • Java wrapper for Client-side gSKI

  • Expand gSKI support to include functions necessary for debugger

  • Applications

    • Java Eaters

    • Java TankSoar

    • Java debugger


  • Login