1 / 25

Scenario elicitation

Scenario elicitation modules. Scenario elicitation. Sample elicitation scripts . Execution of the elicitation scripts. Script editor. Scenario elicitation: hands-on experience. Scenario Elicitation. Sample elicitation scripts. <object>. subconcept_of.

tucker
Télécharger la présentation

Scenario elicitation

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. Scenario elicitation modules Scenario elicitation Sample elicitation scripts Execution of the elicitation scripts Script editor

  2. Scenario elicitation: hands-on experience ScenarioElicitation

  3. Sample elicitation scripts <object> subconcept_of Script type: Elicit instances of Scenario Controls: Question: “Provide a name for the scenario to be analyzed:” Answer variable: <scenario-name> Default value: “new-scenario” Control type: single-line Ontology actions: <scenario-name> instance-of Scenario Script calls: Elicit the properties of the instance <scenario-name> elicitation_script Scenario elicitation_script Script type: Elicit properties of an instance <scenario-name> of Scenario: Script calls: Elicit the feature brief_description for <scenario-name> Elicit the feature description for <scenario-name> Elicit the feature has_as_opposing_force for <scenario-name>

  4. Sample elicitation scripts (cont.) <feature> subfeature_of Script type: Elicit the feature Has_as_opposing_force for an instance <scenario-name> Controls: Question: Name the opposing forces in <scenario-name> Answer variable: <opposing-force> Control type: multiple-line, height 4 Ontology actions: <opposing-force> instance-of Opposing_force <scenario-name> Has_as_opposing_force <opposing-force> Script calls: Elicit properties of the instance <opposing-force> in new window Has_as_opposing_force elicitation_script

  5. Execution of the elicitation scripts <object> Script type: Elicit the feature Has_as_opposing_force for an instance <scenario-name> Controls: Question: Name the opposing forces in <scenario-name> Answer variable: <opposing-force> Control type: multiple-line, height 4 Ontology actions: <opposing-force> instance-of Opposing_force <scenario-name> Has_as_opposing_force <opposing-force> Script calls: Elicit properties of the instance <opposing-force> in new window subconcept-of subconcept-of Force subconcept-of Scenario Opposing_force instance-of instance-of Has_as_opposing_force instance-of Anglo_allies_1943 Sicily_1943 Has_as_opposing_force European_Axis_1943 …

  6. Script editor: hands-on experience ScriptEditor

  7. Recommended reading License, Learning Agents Laboratory, George Mason University, October 2001. (required) Disciple-RKF/COG: Demo Guide, Learning Agents Laboratory, George Mason University, October 2001. Installation, General Functions, Scenario Elicitation, Script Editor, Learning Agents Laboratory, George Mason University, October 2001. Michael Bowman, Sicily COG Report, US Army War College, Spring 2001.

More Related