Changes between Version 6 and Version 7 of VirtualHumanLoader


Ignore:
Timestamp:
08/07/12 23:49:38 (7 years ago)
Author:
dennisr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VirtualHumanLoader

    v6 v7  
    44We have made an XML format to specify in detail what should and should not be initialized for your virtual human.  
    55 
    6 main idea: you can specify Embodiments and Engines. Each Embodiment offers an interface to display expressions and behaviors: skeleton control for animation, MPEG4 control for a face embodiment,motor control for a robot embodiment, etcetera. An Engine specializes in displaying specific behavior types (e.g., head and hand gestures) on one or more of the Embodiments. In a !VirtualHumanSpec file you specify the various embodiments and engines, and connect the embodiments to the right engines. 
     6main idea: you can specify Embodiments and Engines. Each Embodiment offers an interface to display expressions and behaviors: skeleton control for animation, MPEG4 control for a face embodiment,motor control for a robot embodiment, etcetera. An Engine specializes in displaying specific behavior types (e.g., head and hand gestures) on one or more of the Embodiments. In an Asap Virtual Human Loader file you specify the various embodiments and engines, and connect the embodiments to the right engines. 
    77 
    8 A somewhat self-explaining example VHSpec file can be found in `HmiResource/HmiHumanoidLoaderDefaults/resource/Humanoids/armandia/testvhloader.xml`. 
    9 An example of how to load such a file is in `HmiDemo/EnvironmentDemos/src/hmi/environment/examples/MinimalBMLRealizationDemo.java`. 
     8== Start of documentation == 
     9 
     10General structure: the file consists of 3 sections, that must appear in that order. 
     11 
     12{{{ 
     13<AsapVirtualHuman> 
     14 
     15   Subsection: Specification of parsing, scheduling, pipes, ports, and adapters 
     16 
     17   Subsection: Specification of Embodiments, Engines, and other loaders 
     18 
     19   Subsection: Re-routing of BML to Engines (overriding defaults) 
     20 
     21</AsapVirtualHuman> 
     22}}} 
     23 
     24== parsing, scheduling, pipes, ports, and adapters == 
     25 
     26__Log pipe__ 
     27Module: in Asap core  
     28Allows you to log all incoming requests and outgoing feedback messages to an Slf4j channel. Configurable: the logger name for requests and for feedback. 
     29{{{ 
     30<PipeLoader id="..." loader="asap.realizerembodiments.LogPipeLoader"> 
     31        <Log requestlog="..."  feedbacklog="..."/>  
     32</PipeLoader> 
     33}}} 
     34 
     35__ActiveMQPipe __ 
     36Module: org=HMI   name=HMIActiveMQPipe  
     37Connects your realizer seamlessly to the ActiveMQ network, through the {{{asap.bml.request}}} and {{{asap.bml.feedback}}} channels. 
     38No configuration settings; connects to ActiveMQ on localhost, default port. 
     39{{{ 
     40<PipeLoader id="..." loader="hmi.activemq.bmlpipe.ActiveMQPipeLoader"/> 
     41}}} 
    1042 
    1143== User contributions ==