VGS Version 3.6.0 (build 2108) for Windows NT 4.0, 2000, XP
May 2009

This document contains the latest information about the T-VEC Vector Generation System.

© Copyright T-VEC Technologies, Inc., 2000-2009

Windows is a trademark of Microsoft Corporation registered in the U.S. and other countries.

All other trademarks and service marks are the property of their respective owners.

The upgrade can be verified by checking the About Box in the Visual Environment ( Help | About ) for version


or by typing the following command

t_vec -version

from a command shell. If the upgrade has been properly applied, the following version information will be displayed...

T-VEC Console Tool 3.8.0  Copyright 1996-2009 T-VEC Technologies, Inc.
... license information ...
T-VEC Version 3.6.0 (build 2108) for Windows NT4, 2000, XP
  T-VEC Compiler                   8.4.0   (verified)
  T-VEC Vector Generator           10.4.0  (verified)
  T-VEC Coverage Analyzer          4.0.0   (verified)
  T-VEC Inference Engine           10.1.0  (verified)
  T-VEC Mapper Generator           2.0.0   (verified)
  T-VEC Vector Formatter           5.1.0   (verified)
  T-VEC Test Driver Generator      3.1.0   (verified)
  T-VEC Cross Comparator           3.0.1   (verified)
  T-VEC API                        3.2.0   (verified)
    Specification Parser           3.0.0   (verified)
    Knowledgebase Parser           3.0.0   (verified)
    Test Vectors Parser            3.0.0   (verified)
    Mapper Parser                  3.0.0   (verified)

NOTE: The Visual Environment (GUI) included in this release requires the installation of Microsoft Internet Explorer 4.0 or later to function properly. If it is not currently installed, please visit Microsoft's IE site to obtain and install it prior to installing T-VEC.

Release 3.6.0 5/09 

Visual Environment (GUI)

·         Added new VGS work environment feature called Scenario Views. In this new view, users can customize aspects and options for vector generation of specific DCPs and then generate test vectors only for the defined and enabled Scenarios, or process them in conjunction with the standard test vector generation DCP processing. With the Scenario View, users can override the domains of input variables, setting them to smaller sub-domains or single point values. Users can also override the vector generation options for each Scenario. Theis new view provides the user with a way of conducting model analysis on specific DCP’s, experiment with different input values than might be identified by the vector generator’s default rules, and/or experiment with different vector generation options – without the normal overhead of generating vectors for all of the current subsystem. Vector generation processes can also be initiated from within the Scenario View. This eliminates the need to change over to the Project View and thus eliminating mouse movements and/or keystrokes. See the VGS Reference Guide for more information.

·         Corrected issue where some VGS build commands are not being properly activated in certain views.

·         It is now possible to specify a list that includes ranges of DCPs for the purpose of generating or ignoring specific DCPs (for example, “1,4,5-10,17”) [0005963]. This is supported in both the VGS vector generation properties dialog boxes and on the command line invocation syntax.

·         When a file or project needs to be saved, VGS will now display the name of the file that has to be saved instead of bringing up a generic “need to save” dialog.

·         Corrected issue where the navigation mechanism to Simulink fails to highlight the correct operator block being navigated to from within VGS. This was happening when there were newline characters in the name of the Simulink block being accessed/highlighted. The newline characters were being filtered out, which prevented Simulink from identifying the block being requested.

·         Added a feature in the Test Vector Generator Properties for controlling the minimum delta above or below a domain boundary that variables that are related by inequality operators such as > and < are converged to [0005658][0005659].

·         Filtered out Array variable columns from vector display when none of the array elements has a defined value. This is related to the support added in the last release for arrays with sparse contents – i.e. only subsets of the array elements having values for the current test vector. [0005739]

·         Added an option for specifying the number of projects or files to keep in the recently used file list. This option can be accessed through the “Tools->Options->Miscelleanous” setting. [0006090]

·         Corrected issue where deleting a Subsystem from the project view causes VGS to crash.  In addtion, it is no longer possible to remove a subsystem that has a dependant from the project.

·         Corrected issue where the refresh environment function does not always refresh all open documents. [0006154]

·         Added feedback for the refresh environment and save workspace features [0006153]

·         Moved the menu item for accessing project or subsystem properties from the edit menu to the build menu. The properties page can now be accessed through “build->properties”. The project and subsystem properties can still be accessed normally through the context (right click) menu. [0006152]

·         Clean up the edit menu, removed unused menu item “edit->del” and “edit->go to model”. [0006147, 0006148]

Test Vector Generator and Compiler

·         Corrected minor convergence-related bug in the vector generation rules for processing the arctan2() function. [0005669]

·         Added support for using bitwise AND, OR, XOR operators on BOOLEAN variables, in addition to the already supported use for integer/unsigned variables.[0005680]

·         Significantly improved the vector generation performance for T-VEC projects with subsystems having large structure variables as inputs. In some cases, vector generation times were improved by orders of magnitude. These were often higher level Simulink subsystems with very large numbers of signals flowing into them. [0005865]

·         Extended optimization support for Simulink NAND and NOR gates from the previous 4-input gates up to 12-input gates, the same as for AND, OR, and XOR. [0005830]

·         Extended support for Simulink “Sign” blocks with unsigned integer inputs. It is possible in Simulink to create such arrangement, but it was not being account for as it was not expected. [0005852]

·         Fixed a crash that occurs when printing out test vectors for subsystem with 10000+ output elements. A very large print buffer was being overwritten because of the size of the test vector printout information.[0005866]

·         Made improvements in vector generation of DCPs containing variables of mixed types which include string variables in addition to numeric variables. [0005872]

·         Added support for T=0 initialization of state variables of type “enumeration”. T-VEC variables of an enumerated type occur in some types of stateflow translations where there is a need to manage information like active/inactive states of a state machine.

·         Fixed a crash in the vector generator when trying to select a Simulink Selector block signal that does not exist in the model. Vector generator was expecting that the selector signal would never contain a constant value that was outside the scope of the available signals. [0005876]

·         Added DCP number to the XML representation of each test vector.[0005927]

·         Made an improvement to the error diagnostics information that is generated in the case when no FCP path can be found through the subsystem hierarchy that is consistent with the constraints of the parent system. When the constraint inconsistency is found with the parent’s constraint expressions that follow the call/return from a child subsystem, the parent level constraint relation is also included in the error diagnostics, in addition to all of the "Convergence Failure Within Subsystem Reference" information.[0005933]

·         Made an improvement to the the error diagnostics information in cases where the “Exact SS File Location” listed in the error report was identical to the “SS File Constraint Location   for arithmetic error cases. Now, the exact location is being provided in many more cases.[0005995]

·         Corrected a problem with generating vectors for subsystems using the Initial_Condition Simulink block.[0005970]

·         Modified the error diagnostics report mechanism to create separate reports for each DCP # when vectors are being generated on a specific DCP by DCP basis, such as during the use of the Vector Scenarios mechanism. [0005996]

·         Updated the Consult Subordinate Vectors optimization option to be applicable to TTM tables with structure outputs. [0006022]

·         Enhanced the Skip DCP field in subsystem options to allow DCP specifications in terms of comma separated list of both individual DCP numbers and ranges of DCP numbers, eg. “1, 6, 10-15, 18”.

·         Refined the final domain of values field for output scalars in test vector files to reflect constant assignments to the output scalar. In the past, this field simply held the general domain of values associated with the semantic type of the output scalar, regardless of the post-condition relationship providing a value. Now, the domain will reflect any constant values assignments to the output scalar such that the domain of “possible values” will simply be the value of the constant. This is useful both for the user’s understanding of the test vector, but also in support of the Consult Subordinate Vectors optimization heuristic. [0006044]

·         Improved the relevance of the error diagnostics information in the case of array indexing that is outside of the domain of the array size. In the past, the array bound exception handler did not have access to the location in the model where the array exception took place. Addition information was made available in order to improved the error report information content. [0006061]

·         Fixed a data type assignment issue where the use of the sprintf() function in TTM has a character input and a %c pattern was resulting in a CHAR type output from the sprintf() function. It is now always outputting a STRING value. [0006068]

·         Added sections to T-VEC VGS Reference Manual, including a section on the new VGS Scenario View, additional documentation on VGS Menu items, and a section on Basic Syntax in the Test Driver Metatokens Appendix.


Close Window