24. Revision History#

Different versions of Reactis are labeled as shown in Figure 24.1 and described below.

_images/versionLabel.png

Fig. 24.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.#

Major Releases.

There are two major Reactis releases each year, for example V2023 and V2023.2.

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, V2023.1, and V2023.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:

V2023.0.1

denotes the first patch release for V2023

V2023.2.3

denotes the third patch release for V2023.2

24.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:

https://reactive-systems.com/mlists.msp?lid=2

24.2. V2025 (3 June 2025)#

The V2025 release of Reactis includes the bug fixes that were included in patch releases through V2024.2.2, plus the new features listed below.

24.2.2. Generalized Mechanism for Linking to Requirements#

Reactis Validator lets you formulate a requirement that your model should satisfy and then search for violations of the requirement. Prior to V2025, Reactis offered a mechanism to link from a Validator objective to a natural language version of the requirement maintained in a Microsoft Word or Excel document. V2025 offers a generalized version of this mechanism which can be configured to link to other types of requirements repositories, e.g. a web-based system.

24.2.3. Automatically Generate Assertions for Checking Run-Time Errors in Stateflow Charts#

Extending the automatic Run-Time Error (RTE) assertions introduced in Reactis V2023, Reactis now automatically generates RTE assertions within Stateflow charts. Just like in Simulink, these assertions track the following types of errors:

  • Integer Overflow: The result of an integer arithmetic operation is not in the range of the integer type for the result.

  • Integer Division by Zero: The divisor of an integer division operation is zero.

  • Inf/NaN: The result of a floating-point operation is +-Inf or NaN.

  • Indexing: The index used to identify the position of an element in an array is out of range.

24.2.4. Improvements to SMT Solver#

The Reactis solver interface constructs and solves constraints for two purposes:

  1. to flag targets as unreachable

  2. to guide Reactis Tester in the selection of inputs to exercise targets during test-generation.

Improvements to the solver interface in V2025 enable Reactis to flag more targets as unreachable and to exercise more targets with generated tests.

The solver interface has been extended to support the following Simulink blocks: Discrete Integrator, Rate Limiter and Weighted Sample Time Math.

The solver interface has improved support for integer division in models where Reactis is configured to produce an error on integer division by zero.

24.2.5. Embedded MATLAB (EML) Support Improvements#

V2025 adds support for the circshift function in all places where Reactis supports the use of EML (e.g., MATLAB Function blocks, MATLAB Action language in Stateflow).

24.2.6. Other Improvements#

  • A new option for CSV export lets you include the current Reactis version the exported file.

  • A new menu item (File > Launch MATLAB with Reactis API) starts a MATLAB window with the Reactis API pre-configured for use.

  • A new setting in the Edit > Error Checking pane lets you configure a model to continue test generation after detecting an indexing error in Stateflow.

24.2.8. Additional Bug Fixes#

The following bugs fixes are included in V2025 but not in previous releases:

  • If the Prepend Reactis search path to MATLAB search path option is checked for a model and a Pre-Load Function is defined for the model in Reactis then previously, the pre-load function was executed before updating the search path. This could lead to situations where scripts in the pre-load function would not be found. In V2025, the pre-load function is executed after updating the search path (#5605).

  • In previous versions, a warning about unsaved changes could appear when starting Reactis Simulator or Tester after canceling a Tools > Synchronize Inports, Outports and Test Points operation. This has been fixed in V2025.

24.3. Previous Major Release Dates#

Major releases of Reactis for Simulink prior to V2024.2 occurred on the following dates:

V2024.2

November 21, 2024

V2024

June 5, 2024

V2023.2

December 22, 2023

V2023

June 30, 2023

V2022.2

December 23, 2022

V2022

June 22, 2022

V2021.2

December 23, 2021

V2021

July 9, 2021

V2020.2

December 18, 2020

V2020

July 17, 2020

V2019.2

December 20, 2019

V2019

June 28, 2019

V2018.2

December 20, 2018

V2018

June 27, 2018

V2017.2

December 22, 2017

V2017

July 7, 2017

V2016.2

December 22, 2016

V2016

June 20, 2016

V2015.2

December 18, 2015

V2015

June 30, 2015

V2014.2

December 19, 2014

V2014

June 25, 2014

V2013.2

December 17, 2013

V2013

August 14, 2013

V2012.2

December 19, 2012

V2012

June 14, 2012

V2011.2

December 20, 2011

V2011

June 22, 2011

V2010.2

November 19, 2010

V2010

February 8, 2010

V2009.2

July 22, 2009

V2009

January 16, 2009

V2008

June 10, 2008

V2007

October 31, 2007

V2006.2

November 6, 2006

V2006

January 25, 2006

V2005

May 18, 2005

V2004.2

December 17, 2004

V2004

March 3, 2004

V2003.2

October 16, 2003

V2003

February 4, 2003

V2002

June 3, 2002