Importing a trace file from a file in non-TuningFork format

TuningFork can import trace files from certain non-TuningFork formats. The supported formats and the associated import options are briefly described in subsections of this section of the user's guide. There is reasonably generic coverage of XML and delimited ASCII. There is more specific coverage of the XML and delimited ASCII formats produced by the TuningFork export facility. Import plugins for other specific formats exist and more are being developed.

To use the importing facility, select "Import Trace" from the File menu, or press Ctrl-i.

You are first asked to specify the file to import, and, optionally, a file in which to save the converted contents as a standard TuningFork trace. If you use the "Save converted file" option, you can avoid repeated import steps by using the converted .trace file for subsequent analyses. Otherwise, TuningFork saves the converted trace anyway, in the importedTraces subdirectory of its workspace, using a generated name. Files are not automatically deleted from this directory so you may wish to empty it manually from time to time.

Different TuningFork import plugins may tentatively recognize the file format, based on both the file extension and on a limited inspection of its contents (for example, XML and delimited ASCII are usually recognized regardless of the extension). If more than one import plugin tentatively recognizes the format, you will be asked to select the specific import strategy from a list. The remainder of the import dialog depends on the particular import strategy chosen (some strategies require no further dialog, in which case pressing the Next button immediately enables the Finish button). If only one import plugin recognizes the format, the import strategy selection step is omitted.