Different versions of Reactis are labeled as shown in
Figure C.1 and described below.
|Figure C.1: Version labels begin with a “V” and
include three parts: a year, a major release number, and a patch
release number. The parts are numbers separated by decimal points.
By convention, trailing zeros are omitted.|
- A new version of Reactis is released
at the start of each year and labeled by a “V” followed by the
four-digit year, for example V2016. Each label for an intra-year
release includes a suffix consisting of a decimal point followed by a
major release number; for example V2016.1, V2016.2, etc. will
label the releases during 2016 that follow V2016.
- Beta Releases.
RSI often makes beta releases available to customers interested in
evaluating the newest features of Reactis. Beta releases do not
undergo as much testing as major releases do. By convention, beta
releases have odd numbered major release numbers. For example,
V2016.1, and V2016.3 denote beta releases.
- Patch Releases.
Both stable and beta releases may be “patched.” The label for a
patch release is constructed by extending the label for the major
release to be patched with a suffix that includes a second decimal
point and a patch release number. For example:
| V2016.0.1||denotes||the first patch release for V2016|
| V2015.2.3||denotes||the third patch release for V2015.2|
C.1 Patches Mailing List Archive
Patches to Reactis are posted to the Reactive Systems website every two to
four weeks on average. To view a summary recent changes, please view the
archives of the Reactis Patches mailing list available at:
C.2 V2017 (7 July 2017)
The V2017 release of Reactis includes the bug fixes that were included
in releases V2016.2.1 through V2016.2.4 plus the new features listed below.
C.2.1 Newly Supported Simulink Features
The following Simulink features are supported in Reactis V2017:
Support MATLAB R2017a.
- Support Variant Source and Variant Sink blocks.
- Support Lookup and Prelookup blocks in which the input data type is
different from the breakpoint data type.
- Support outputting Stateflow leaf-state and child-state activity to Simulink.
C.2.2 API improvements
Added API functions to add/modify/remove test points.
- Added options to include/exclude plots in test execution report.
C.2.3 Reactis for EML Plugin
Support ’struct’ function.
- Support empty ’otherwise’ branches in ’switch’ statement.
C.2.4 Enhanced Test Points
Previously, test points in Reactis could only be used to capture model data
and compare it to data in a test suite. In Reactis V2017, test points can
also be used to check a value in a model against boundary constraints defined
for the test point. Reactis can track whether the boundaries have been met
and/or exceeded. Test points exceeding their boundaries can be recorded as
either warnings, errors or assertion failures.
- Captured test point data can be constrained to the given boundaries.
- All test point operations such as adding, modifying or removing
are now available via the Reactis API.
C.2.5 Enhanced Scopes
When zooming into scopes, instead of zooming a fixed amount, the user
can draw a rectangle of interest and the scope will zoom to that rectangle.
- When zoomed into a scope, the scope window can be moved along the
signal by holding the CTRL key while dragging.
- Improved the choice of major and minor tick marks.
- A screen shot of the scope can be exported to a file or copied to
C.2.6 Test Execution Report Enhancements
- Show input/output/testpoint signals in test execution report.
- Show model version in test execution report.
- User-defined default values can now be specified for the test execution report.
- Tolerance for each input and test point is included in the report.
C.3 Previous Major Release Dates
Major releases of Reactis prior to V2017 have occurred on the
| Version||Release Date|