This section explains how to run Converter from a command line. In particular, it describes:
5.1.1. Starting Converter¶
Converter runs as a separate application. The script to run the
executable is in
<NDDSHOME>/bin. (See Section 1.3 for
the path to NDDSHOME.)
To start Converter with a default configuration, enter:
Converter is pre-loaded with a builtin configuration that has default settings. See Section 5.2.20.
5.1.2. Converter Command-Line Parameters¶
The following table describes all the command-line parameters available in
Converter. To list the available parameters, run
All command-line parameters are optional; if specified, they override the values of any corresponding settings in the loaded XML configuration. See Section 5.2.4 for the XML elements that can be overridden with command-line parameters.
|-cfgFile <string>||Semicolon-separated list of configuration file paths.
This name is used to find a matching
|-D<name>=<value>||Defines a variable that can be used as an alternate replacement for
XML environment variables, specified in the form $(VAR_NAME).
Note that definitions in the environment take precedence over these definitions.
|-help||Shows this help.|
Default: 1 (exceptions)
|-version||Prints the program version and exits.|
5.1.3. Working With Large Data¶
The built-in SQLite plugin implementation available in Converter is prepared to handle any type size and storage format. However, when working with large data types and massive files (or filesets), Converter may take a while to prepare SQL statements to work with the data, resulting in a delay when starting the conversion process.
Because of this delay, it is recommended that you index the user data tables for
those large topics before running Converter on them. Indexing can massively
improve Converter’s startup time for those topics. You can create the indexes
offline, after Recording Service has finished recording all the data. Index the
tables on the
SampleInfo_reception_timestamp field. For example, imagine a
VeryLargeTopic@0, has been created by Recording Service; you can use
the following index creation statement:
CREATE INDEX IF NOT EXISTS [VeryLargeTopic@0_idx_rt] ON [VeryLargeTopic@0] (SampleInfo_reception_timestamp)