07.05.2013 Views

TPT User's Guide - PikeTec

TPT User's Guide - PikeTec

TPT User's Guide - PikeTec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Page 86 <strong>TPT</strong> User’s <strong>Guide</strong><br />

15.10.3 General platform configuration variables<br />

In addition to the environment variables stated above, the following environment variables can<br />

be used in the context of platform configurations:<br />

Name Format Description<br />

tpt.stepsize double step size of the test execution as specified in the platform<br />

configuration<br />

tpt.timeout double time out of the test execution as specified in the platform<br />

configuration<br />

15.10.4 MATLAB platform configuration variables<br />

Name Format Description<br />

tpt.matlab.modelname text Name of the test frame model to be executed<br />

tpt.matlab.modelfile file File name of the test frame model file that is responsible<br />

for execution<br />

tpt.matlab.modelfile.dir dir Directory where the model file (test frame model file) is<br />

stored<br />

tpt.matlab.version text Logical name of the MATLAB version<br />

tpt.matlab.rootdir file Directory where MATLAB is installed<br />

tpt.matlab.restartnow int This preference is 1 if MATLAB will be restarted<br />

immediately. Otherwise the value is 0. MATLAB will be<br />

restarted (value is 1) if and only if the parameter “Restart<br />

MATLAB every X tests” is set and if the given number X of<br />

tests has been reached.<br />

tpt.matlab.paramstoworkspace text This variable will be substituted by a sequence of mstatements<br />

that set all the test parameters of type<br />

EXCHANGE defined in the <strong>TPT</strong> test case as MATLAB<br />

workspace variables. In order to use this feature, just add<br />

${tpt.matlab.paramstoworkspace} as a<br />

statement into your run test script.<br />

15.10.5 Backbone platform configuration variables<br />

Note, that the following variables are only available together with the backbone integration<br />

extension of <strong>TPT</strong>, which is not part of the regular <strong>TPT</strong> installation. The backbone platform allows<br />

interaction with the Backbone simulation environment for SIL simulations. This platform has<br />

been developed by DaimlerChrysler. For more information send an email to<br />

tpt@piketec.com.<br />

Name Format Description<br />

tpt.backbone.rootdir dir root directory of the backbone installation (dir that contains<br />

“dllkopp/bin/backbone.exe”)<br />

tpt.backbone.config file the “bbc-file” which is the file that describes the modules to<br />

be loaded by the backbone. See backbone documentation<br />

about details. This file is configured in the backbone config<br />

panel<br />

tpt.backbone.workdir dir directory where the backbone will be started<br />

15.10.6 Scenario specific variables<br />

Name Format Description<br />

tpt.scenario.name text Name of the currently executed scenario<br />

tpt.scenario.groupname text Name of the group of the currently executed scenario<br />

tpt.scenario.id int Unique ID of the currently executed scenario<br />

tpt.scenario.dir dir Directory where data for the currently executed scenario is<br />

been stored<br />

tpt.scenario.islast int This preference is 1 if the current scenario is the last one that<br />

is being executed using the current settings. The preference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!