Appendix C Revision History
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 V2018. Each label for an intra-year
release includes a suffix consisting of a decimal point followed by a
major release number; for example V2018.1, V2018.2, etc. will
label the releases during 2018 that follow V2018.
- Beta Releases.
Reactive Systems sometimes 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, V2018.1,
and V2018.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:
| V2018.0.1||denotes||the first patch release for V2018 |
| V2017.2.3||denotes||the third patch release for V2017.2 |
C.1 Patches Mailing List Archive
Patches to Reactis are posted to the Reactive Systems website between
major releases. To view a summary of recent changes, please view the
archives of the Reactis Patches mailing list available at:
C.2 V2018.2 (20 December 2018)
The V2018.2 release of Reactis includes the bug fixes that were included
in patch releases through V2018.0.2 plus the new features listed below.
C.2.1 Newly Supported Simulink Features
The following Simulink features are supported in Reactis V2018.2:
- Signals with dimensions greater than 2 in Simulink and Stateflow.
- “Input port” setting for initial condition in Delay block.
- Matrices as initial conditions in Delay block.
C.2.2 Version Information in .rsi Files
The .rsi file which stores the input port constraints and model-specific
settings for a model now tracks the following version information:
A revision number for the .rsi file that is increased
automatically every time the .rsi file is modified and saved.
- The user name under which the last modification was made.
- The date of the last modification.
This information can be seen by selecting Edit -> General in
the Reactis GUI and can be queried using the rsRsiGetParameterValue()
function in the API. The revision number is also included in test execution
and coverage reports (next to the .rsi file name).
C.2.3 Cumulative Coverage Tracking for Referenced Subsystems and Models
It is now possible to track coverage for referenced subsystems and models
cumulatively. To select a system or model for cumulative coverage, navigate
to an instance of the system in the hierarchy tree, right-click on the name
and select Coverage Tracking -> Cumulative.
Coverage for cumulatively tracked systems is shown in a special section
in the hierarchy tree. Interactions such as breakpoints and data observation
continue to be handled in the specific instances.
The following functions have been added to the Reactis API:
- rsRsiSetCumulativeCoverage: Enable/Disable cumulative coverage tracking for a
referenced model or library subsystem.
- rsRsiIsCumulativeCoverage: Check cumulative coverage tracking status for a
referenced model or library subsystem.
- rsRsiGetCumulativeCoverage: Query all systems/models for which cumulative
coverage tracking is enabled.
C.2.5 Reactis for EML Plugin
Support type arguments to
- Support scalar expansion in
C.3 Previous Major Release Dates
Major releases of Reactis prior to V2018.2 have occurred on the
| Version||Release Date |