Reactive Systems logo

Automated Testing and Validation with Reactis®

June 26, 2017
Newsletters
Patches
 
Spacer
Back to Patches Archive

To: Subscribers to Reactis Patches Mailing List
From:
Reactive Systems (http://www.reactive-systems.com)
Date:
December 2, 2005

We are pleased to announce the availability of Reactis V2005.1.12 (Beta)

The following features were added since V2005.1.11.

  1. Configuration variables of type array and structure are now supported. To specify such a type for a configuration variable, in the ``Configuration Variables'' tab of the Info File Editor:
    1. Select the row containing the configuration variable to set.
    2. Right-click on the row and select ``Edit Type Text''.
    3. A text entry dialog will come up in which the array or structure type may be specified. The syntax is as follows:
      • One-Dimensional Arrays
        basetype array [ numElts ] { instance1, ..., instancen } where numElts is a positive integer and each instancei has the form [ elt1, ... , eltm ].
      • Two-Dimensional Arrays
        basetype array [ numRows, numCols ] { instance1, ..., instancen } where numRows and numCols are positive integers and each instancei has the form [ row1; ... ;rownumRows ] and each rowi has the form elt1,..., eltnumCols.
      • Structures
        { fieldName1 : fieldType1, ... , fieldNamen : fieldTypen } { instance1, ..., instancem } where each instancei has the form { fieldName1 = value1, ... , fieldNamen = valuen }.

    The following examples demonstrate the notation.

    1. Three instances of a four-element array of doubles:
      double array [4] 
      { 
        [1,2,3,4], 
        [11,12,13,14], 
        [21,22,23,24]
      }
      
      
    2. Two instances of a structure for initializing a 2-d Lookup Table:
      
      % configuration variable type
      
      { table  : double array [3,3], 
        row    : double array [3], 
        column : double array [3]}
      
      {
      
      % first Look-Up-Table configuration
      
        {table  = [4,5,6;16,19,20;10,18,23],
         row    = [1,2,3],
         column = [1,2,3]},
      
      % second Look-Up-Table configuration
      
        {table  = [4,5,6;16,19,20;10,18,23],
         row    = [16,18,20],
         column = [11,12,13]}
      
      }
      
      
  2. When hovering over an item in the hierarchy panel that is a child of the system currently displayed in the main panel, Reactis now highlights the label of the item in the hierarchy panel and the main window. This can help users locate a child subsystem residing in a large parent.
  3. Dragging with left mouse button in the main window will now scroll the model. To select a print region, drag with left button while holding down the CTRL key.
  4. In Simulator, when one or more tests are selected to be run, the ``number of steps'' entry box in the toolbar will be pre-filled with the number of steps selected.
  5. Added a ``Go to Parent'' button to the Reactis toolbar (drawn as an arrow pointing up). When this button is clicked, Reactis will display the parent of the currently displayed system.
  6. When exporting a test suite, use the name of the current test suite as a default base name.
  7. Produce an error or warning for the case where values might get back-propagated into a Stateflow chart through an output port of the chart that is connected to a Merge block. Whether an error or warning is issued can be configured from the Reactis settings dialog.
  8. Produce a warning if a type alias is ignored in Stateflow because it is shadowed by a built-in type. This happens because Stateflow is not case sensitive for built-in types. For example, given an alias ``DOUBLE'' = ``single'' Simulink will always use ``single'' when type ``DOUBLE'' is given. Stateflow will still use ``double''. Reactis will now produce a warning if this happens.
  9. The Reactis License Manager now produces a log file. This file is named ``reactisl_log.csv'' and is located in the Reactis root folder.
  10. In the ``User Info'' tab of the ``Settings'' dialog, an option is now available to automatically set the name field to the Windows username of the person currently logged in.

The following bugs were fixed since V2005.1.11.

  1. Fixed lockup during type inference phase when a circular type alias involving a built-in Simulink type was encountered.
  2. Fixed ``Reactis' backend computation engine died unexpectedly'' bug that could occur for some models using data objects.
  3. Recognize type aliases when retrieving top-level inport types.

You may download the patches or full installers from:

http://www.reactive-systems.com/login.msp

Best Regards,
The Reactis Team

Back to Patches Archive

Spacer