hisl_0043: Configuration Parameters > Diagnostics > Solver

R2026b

Set solver diagnostic parameters to detect configuration issues that could impact code generation

Usage: High-Integrity System Modeling

Guideline ID: hisl_0043

Rules

hisl_0043: Configuration Parameters > Diagnostics > Solver

In the Configuration Parameters dialog box, on the Diagnostics pane, set the Solver parameters as follows:

  • Algebraic loop to error.

  • Artificial algebraic loop occurrences not eliminated to error.

  • Block priority violation to error if you are using block priorities.

  • Automatic solver parameter selection to error.

  • State name clash to warning.

Rationale

Support generation of robust and unambiguous code.

Verification

Check safety-related diagnostic settings for solvers (Simulink Check)

Tips

  • Enabling diagnostics pertaining to the solver provides information to detect violations of other guidelines.

  • This table clarifies the result of not specifying the configuration parameter as indicated above.

    Configuration ParameterResult
    Algebraic loop Automatic breakage of algebraic loops can go undetected and might result in unpredictable block order execution.
    Artificial algebraic loop occurrences not eliminatedAutomatic breakage of algebraic loops can go undetected and might result in unpredictable block order execution.
    Block priority violationBlock execution order can include undetected conflicts that might result in unpredictable block order execution.
    Automatic solver parameter selectionAn automatic change to the solver, step size, or simulation stop time can go undetected and might impact the operation of generated code.
    State name clashA name being used for more than one state might go undetected.

Industry Standards

  • DO-331, Section MB.6.3.3.b – Software architecture is consistent.
    DO-331, MB.6.3.3.e 'Software architecture conforms to standards'

  • IEC 61508-3, Table A.3 (3) 'Language subset'

  • IEC 62304, 5.5.3 - Software Unit acceptance criteria

  • ISO 26262-6, Table 1 (1b) 'Use of language subsets'

  • EN 50128, Table A.4 (11) 'Language Subset'

  • EN 50657, Table A.4 (11) 'Language Subset'

Version History

Introduced in R2010a

expand all

See Also

|