Given an array of whether samples violated bounds, searches for a given number of violations per run for a given run length. Can use this to build a set of rule checkers. Searches Boolean input array sample exceeds bounds for # violations per run set to true within run length. Values in the sample exceeds bounds array are set to true if they violate some rule limit. Returns arrays with the index of each violation point and run length associated with that point. This is used as a generic building block in the rule checker VIs. For example, to test the rule 4 out of 5 points above 2 standard errors. Set # violations per run to 4, and run length to 5. Then test whether each element of the control chart points array is greater than 2 standard errors and wire the resulting Boolean array to the points exceeds bounds input.


icon

Inputs/Outputs

  • c1dbool.png point exceeds bound —

    point exceeds bound sets each element to TRUE if point exceeds test bound.

  • ci32.png # violations per run —

    (I32) - the number of violations per run length that indicate that a rule has been violated.

  • ci32.png run length —

    (I32) - the run length for the rule.

  • i1di32.png violation start point —

    violation start point is the start point of each sequence violating the rule.

  • i1di32.png violation run length —

    run length is the run length for the rule.