7 The Mapping Editor

The mapping editor is used to create mappings between components in the different simulation layers of SESAME. There are two types of mapping which differ slightly. Application layer to architecture layer mappings map nodes and channels in the application layer to architecture templates. This type of mapping is viewable under the Application Mapping tab of the YMLEditor. The second type of mapping maps ports from either the template layer or virtual layer on nodes in the architecture layer. The tabs Virtual Mapping and Template Mapping display and provide the editing features for these layers.

Initially there are no mappings. A screen shot of the mapping editor is shown below:

7.1 Application Mapping

Mapping an application process to an architecture component tells the simulator to run the application process on the target architecture component during simulation. Likewise a channel mapping indicates that communication over the specified application channel should be simulated on the specified architecture communication path. Current version of SESAME map application processes and channels onto architecture templates. These templates are then used to generate the virtual layer which does the actual application to architecture mapping at simulation time.

To create a new mapping right click on the Application Mapping list and select Create New Map from the popup menu. If there are mappable nodes or channels this will open a dialog which displays possible mappings. Select the source and destination from the drop down menus. An application node or channel can only be mapped on to one architecture template. However, more than one application node or channel can be mapped on to the same architecture template.

The mapping editors will only show mappings between the currently displayed networks. In order to map nodes in sub-networks or parent networks you must first open these networks by double clicking or selecting the Up option from the popup menu.

Deleting application mappings will also delete the corresponding virtual layer nodes. This loses any changes made directly to the virtual layer. For this reasons is recommended to make changes to architecture templates when at all possible. Other wise save a copy of the virtual layer before making any mapping changes. This feature, however, makes it much easier to change application mappings and rerun the simulation reflecting these changes because the virtual layer is automatically corrected by the Virtual Layer Generator.

7.2 Virtual Layer and Template Mapping

Virtual and template layer mapping works similarly except rather than nodes and channels being mapped to architecture templates, ports are mapped on to architecture nodes. For virtual and template mappings to be viewable and editable the networks to which they apply must be loaded in their respective graph viewers.

For the most part the YMLEditor keeps mappings synchronized with name changes and deletions in the graph editors. However the current implementation of the YMLEditor does not update virtual and template mappings when they are not active, i.e. loaded into the graph editor. This means that name changes and deletions in the architecture layer may invalidate virtual and template layer mappings. In such case these invalid mappings must be deleted and recreated. This is a known bug in the YMLEditor and will be corrected in a future release.

Note

Virtual and template layer mappings are stored in mapping YML properties. In the virtual layer there is only one mapping property per node. Architecture templates may contain more than one mapping. Mappings are differentiated by a name. This name is stored in the property value attribute. This name is used to identify the matching template property. This is demonstrated in the example below.

  <property name="template" value="A">
    . . .
  </property>
  <property name="template" value="B">
    . . .
  </property>
  <property name="mapping" value="A">
    . . .
  </property>
  <property name="mapping" value="B">
    . . .
  </property>

In the example there are two templates A and B with corresponding mappings.

7.3 Visualizing Mappings

To visualize mappings click on the mapping in one of the mapping editors. If the source and destination components or ports are visible in the application, architecture, virtual or template layer graph editors they will be selected and highlighted red. The example below demonstrates this: