modelPrintViolations

Print violated, untested and satisfied requirements at end of simulation (drag in top level of your model)

Information

Block PrintViolations has to be dragged in the top-level of the model, where components of library Modelica_Requirements are used. This block provides the file name, to which the Requirement blocks write their status at the end of the simulation (whether a Requirement is Violated or Untested). Furthermore, the PrintViolations block reads this log-file at the end of the simulation and prints a summary to the output window.

Parameters

Type	Name	Default	Description
String	logFile	Internal.getFirstName(getInstanceName()) + "_log.txt"	Name of log file (default = <root name>_log.txt)
String	htmlFile	Internal.getFirstName(getInstanceName()) + "_log.html"	Name of html log file (default = <root name>_log.html)
Boolean	printViolated	true	= true, if violated requirements shall be printed
Boolean	printUntested	true	= true, if untested requirements shall be printed
Boolean	printSatisfied	true	= true, if satisfied requirements shall be printed

Connectors

Type	Name	Default	Description
Modelica_Requirements.Internal.SortingPort	sortingPort		Dummy connector to enforce that printing to and reading from log file is performed in the correct order; do not connect to it)

Components

Type	Name	Default	Description
Real	satisfaction	noEvent(if abs(sortingPort.one) < 0.5 then 100.0 else 100abs(sortingPort.status/(2sortingPort.one)))	Satisfaction of all requirements in % (0% ... 100%)