5.3. Tutorials

5.3.1. Using Timestamp Tags with Converter

If your recording was originally made with the builtin SQLite storage plugin, and you used the tag_timestamp remote command to tag certain events, then your recording contains timestamp tags: symbolic timestamp names you can use in place of timestamps expressed in units of time. For more information on timestamp tags, see Section 3.6.6.

You can list the timestamp tags that are in your recorded database by using the rtirecordingservice_list_tags script. Use the -d argument to point to the directory that contains your recorded database, as follows:

<NDDSHOME>/bin/rtirecordingservice_list_tags -d /database/directory/

This command will analyze the recording in /database/directory/ and list the details of the timestamp tags in the recording, including the tag names, their descriptions, and associated timestamps.

You can use the tag_name of the tags you find in a recording when you are creating an XML configuration file for Converter by using a <data_selection> tag.

For example, if after running rtirecordingservice_list_tags, you see output such as:

tag_name                    timestamp_ms   tag_description
--------------------------  -------------  ------------------------
/my_example/my_events/tag1  1546484663309  first tag description
/my_example/my_events/tag2  1546484703360  a second tag description

Then you can have a <data_selection> tag in your XML for Converter, after the <output_storage> tag, that looks like the following:


Converter will convert data between those tags. Note that when expressing a <time_range> tag, you can mix and match timestamps and tags. For example, you can use a <begin_tag> (by referring to a tag_name) to express the time when conversion should begin, and use an <end_tag> with an end_time timestamp (expressed in time units) to specify when conversion should end. If you do not provide one of the bounds, the start of recording is the default begin bound, and the end of recording is the default end bound.