Open topic with navigation

# Package Templates

You can use a set of individual speaker template files during identification by supplying a list file that specifies the templates to use. However, it might be convenient to package these templates into a single speaker set file.

Using a speaker set file has several advantages:

- A single file simplifies the usage and distribution of the template set.
- The background model that is used during speaker training is packaged with the speaker templates, removing any chance of model mismatches if the base background model is subsequently updated.

You can use standard IDOL Speech Server tasks to add templates to an audio template set file (`.ats`), remove templates from a set file, or to return information on the contents of a set file.

To add templates to an audio template set file

The `SpkIdSetAdd` task takes one or more audio template files, and adds them to an audio template set file. If the set file already exists prior to running the task, IDOL Speech Server adds the templates to the existing set.

- - Send an `AddTask` action to IDOL Speech Server, and set the following parameters:

  `Type` | The task name. Set to `SpkIdSetAdd`.
  `TemplateList` | A list file that specifies the templates to use, along with the name associated with each template.
  `TemplateSet` | The name of the template set file.

For example:

`http://localhost:15000/action=AddTask&Type=SpkIdSetAdd&TemplateList=ListManager/speakers&TemplateSet=speakers.ats`

This action uses port `15000` to instruct IDOL Speech Server, which is located on the local machine, to create the `speakers.ats` template set file containing the templates listed by the `Listmanager/speakers` list file.

You can set additional parameters. For details of the optional parameters, see the IDOL Speech Server Reference.

This action returns a token. You can use the token to:

- Check the task status. See Check the Status of a Task.
- Retrieve the speaker template set file.

To remove a template from an audio template set file

This task removes the named template from the audio template set. If the template named is not found within the set, a task error is given.

- - Send an `AddTask` action to IDOL Speech Server, and set the following parameters:

  `Type` | The task name. Set to `SpkIdSetDelete`.
  `TemplateName` | The name associated with the template to remove.
  `TemplateSet` | The template set file from which to remove the template.

  For example:

  `http://localhost:15000/action=AddTask&Type=SpkIdSetDelete&TemplateName=Brown&TemplateSet=speakers.ats`

  This action uses port `15000` to instruct IDOL Speech Server, which is located on the local machine, to remove the template associated with the name `Brown` from the `speakers.ats` template set.

  You can set additional parameters. For details of the optional parameters, see the IDOL Speech Server Reference.

  This action returns a token. You can use the token to:

  - Check the task status. See Check the Status of a Task.
  - Retrieve the speaker template set file.

To retrieve information on an audio template set file

This task produces a log file that lists the contents of the specified audio template set file.

- - Send an `AddTask` action to IDOL Speech Server, and set the following parameters:

  `Type` | The task name. Set to `SpkIdSetInfo`.
  `TemplateSet` | The template set file to retrieve information for.
  `Log` | The log file to write the information to.

  For example:

  `http://localhost:15000/action=AddTask&Type=SpkIdSetInfo&TemplateSet=speakers.ats&Log=speakers.log`

  This action uses port `15000` to instruct IDOL Speech Server, which is located on the local machine, to write information on the `speakers.ats` template set file to the log file `Speakers.log`.

  You can set additional parameters. For details of the optional parameters, see the IDOL Speech Server Reference.

  This action returns a token. You can use the token to:

  - Check the task status. See Check the Status of a Task.
  - Retrieve the log file.

  ## Log File Example

      <UBM> Yes
      <COMPSELECT> 8 </COMPSELECT>
      <FRAMENORM> UBM </FRAMENORM>
      <NTEMPLATES> 1 </NTEMPLATES>
      <TEMPLATES>
        <TEMPLATE_0>
          <NAME> Brown </NAME>
          <THRESH_ENABLED> Yes </THRESH_ENABLED>
          <THRESH_VALUE> -0.0845253 </THRESH_VALUE>
          <NCOMPS> 1023 </NCOMPS>
          <SHARE_ICOV> Yes </SHARE_ICOV>
          <SHARE_MEANS> Yes </SHARE_MEANS>
          <SHARE_MEANS_PERCENT> 71.9453 </SHARE_MEANS_PERCENT>
        </TEMPLATE>
      </TEMPLATES>

  This file shows some information about how the templates were trained and optimized, along with information about each template stored in the set. The log file includes the following fields:

  `<UBM>` | Whether a Universal Base Model is included in the set.
  `<COMPSELECT>` | How many components are used for each template when scoring.
  `<FRAMENORM>` | The method of frame score normalization used when optimizing the set.
  `<NTEMPLATES>` | The number of templates in the set.
  `<TEMPLATE_0>` | The start of information on template 0, and so on.
  `<NAME>` | The name associated with the template.
  `<THRESH_ENABLED>` | Whether a score threshold is enabled for this template.
  `<THRESH_VALUE>` | The score threshold that has been estimated for this template.
  `<NCOMPS>` | The number of components used in this template.
  `<SHARE_ICOV>` | Whether this template shares variance statistics with a base template.
  `<SHARE_MEANS>` | Whether this template shares mean parameters with a base template.
  `<SHARE_MEANS_PERCENT>` | The percentage of mean parameter components shared with the base template.

© 2013-2016 Hewlett Packard Enterprise Development LP | Send documentation feedback to HPE Close We welcome your comments! To open the configured email client on this computer, open an email window. Otherwise, copy the information below to a web mail client, and send this email to AutonomyTPFeedback@hpe.com. Product: Topic Title: Help Topic: Feedback:

_HP_HTML5_bannerTitle.htm