The Simulink documentation recommends a setting of "error" for the vector/matrix block input conversion diagnostic in "safety precaution" applications. Several modeling standards for high-integrity systems similarly recommend a warning or error output for that diagnostic. Is there a published white paper or other rationale that describes the types of errors or non-deterministic behavior that can result from automatic vector/matrix conversions?
My application includes numerous matrix multiplication applications that are performed on arrays or 1-D vectors that lead to numerous nuisance warnings of this type, and I would like to understand the implications of disabling the diagnostic or adding signal definition or reshape blocks to resolve it, as no adverse behavior has been observed.
0 Comments
Sign in to comment.