迭代組
當測試組不能再找到一個有效MV進行階躍時，其將標記為迭代完成并增加STGITERC計數(shù)。如果完成迭代次數(shù)大于或等于需求迭代數(shù)（STGITER），則測試組標記為已完成。某測試組完成后STGCOMP標簽將被設(shè)置為1，并且測試組請求標簽將被設(shè)置為SUSPEND(掛起)。當用戶將測試組放回TEST(測試)或TEST NO-PULSE模式時， STGCOMP標簽將復位。其允許工程師使用CCF計算來建立一些基本的測試調(diào)度。例如，當?shù)谝粋€測試組完成需求迭代數(shù)量時，工程師可以建立一個計算將所有測試組納入控制中。
組織測試組進行有效測試
測試組設(shè)計應(yīng)最大限度地同時并行階躍測試。當測試組處于TEST模式時，其在一時間內(nèi)僅可進行一個MV的階躍。如果兩個MVs不相關(guān)（即它們不影響相同的CV），那么它們可以同時做階躍測試而不會產(chǎn)生相關(guān)數(shù)據(jù)。這是將MVs放在單獨測試組的充分理由。
當CV在測試范圍外時，測試應(yīng)用將使用測試組中的所有MVs最優(yōu)化解決這一問題。此外，CV所屬的所有測試組也將用于解決此問題。
如果測試組中某個CV不受MVs的影響，那么該CV不應(yīng)該在該測試組中。
如果你遵循這些一般準則，那么你可以實現(xiàn)以下好處：
?在任一時刻MV可被組織到測試組中實現(xiàn)同時測試數(shù)量最大化。
?CVs可以被分配到這些組中來觸發(fā)相應(yīng)的糾正行為。

也可以看看
智能向?qū)?yīng)用中的修正動作
智能向?qū)?yīng)用中的修正(CORRECTING)模式
智能向?qū)?yīng)用中的重新定位(REPOSITION)模式
測試組配置指南

附原文：
Group iterations
When the group can no longer find a valid MV to step then it will mark the iteration as complete and increment the STGITERC counter. If the number of iterations completed is greater or equal to the number of iterations requested (STGITER) then the group is marked completed. Upon completion of a group the STGCOMP flag is set to one and the group request flag is set to SUSPEND. When the user puts the group back into TEST or TEST NO-PULSE then the STGCOMP flag is reset. This allows the engineer to set up some basic test scheduling using ccf calculations. For example the engineer could set up a calculation that puts all test groups into CONTROL once the first test group finishes its requested number of iterations.

Organizing test groups for effective testing
Test groups should be designed to maximize parallel stepping. A group that is in TEST mode will only have one MV stepping at a time. If two MVs are unrelated (that is, they do not impact the same CVs), then they may be stepped simultaneously without generating correlated data. This is sufficient reason to put the MVs in separate test groups.
When a CV goes outside of test limits, the tester application will react to fix the problem by using all of the MVs from the TEST group in an optimal matter. Moreover, all of the test groups to which the CV belongs will be used to correct the problem.
If a CV is not impacted by the MVs of a test group, then the CV should not be in that test group.
If you follow these general guidelines, then you can realize the following benefits:
?MVs can be organized into groups to maximize the amount of simultaneous testing at any given time.
?CVs can be assigned to these groups to trigger the appropriate corrective behavior.

See Also
Correcting moves in a SmartStep application
CORRECTING mode in a SmartStep application
REPOSITION mode in a SmartStep application
Guidelines for configuring test groups

2015/10/23