1、我们感兴趣的第一个时间戳是当控制器被切换到控制模式（第5步）至干扰信号开始从其原点移走（第20步）。图6的左侧显示了所有3个CV在相同优先级时的行为。有趣的是在这段时间戳里所有3个控制目标都得到实现。这是由于在起始时CV_2就处在其设定点的缘故。实际上只有两个CV需要被带到设定值，为此，可以通过操作 MV_1将CV_1带到60 ，通过操作MV_2将CV_3带到40。图的右侧显示了不同优先级情况的类似行为。
2、接下来，有效干扰序列的时期是20步至400步。图的左侧显示了SMOCPro不能将任何的CVs控制到各自的设定点。这是由于所有3个CVs都具有相同优先级，都拥有相同的权重，但只有两个MVs是可用于控制的。图的右侧显示了期望的行为，因为用户已经指定了优先级，SMOCPro放弃了最低优先级的CV，控制剩下的两个CVs到它们相应的设定点。
3、如前面的情况一样，在400步后 SMOCPro开始有能力再次操作所有3个MVs，因此不管是否选择CV优先级，其都可以使用所有3个手段将3个CVs带回到各自的设定点。
带回家的消息
当提到斜坡CVs时，CV优先级的概念和它的正确实施是非常重要的。用户以这种方式指定斜坡CV优先级时必须小心谨慎，如果遇到任何竞争性控制目标和/或残缺模式的话，对每个应用程序其控制行为将是所期望的行为。如果可能的话实际上，如果斜坡CVs分享所有的MVs且可能遇到残缺模式时，斜坡CVs不应该设置成相同的优先级。这里要考虑的一个重要事情是，当优先级设置不正确时，可能导致斜坡CV“上下摇摆”而失控。
原文：
1、The first timeframe of interest is the one from when the controller is switched to control (step 5) to when the disturbance signal first moves away from its origin (step 20). The left side of figure 6 shows the behavior with all three CVs at the same priority. The interesting thing is that for this timeframe all three control objectives are met. This is due to the fact that from the start CV_2 is already at its setpoint. In reality only 2 CVs need to be brought to their setpoints and to this end, MV_1 can be manipulated to bring CV_1 to 60 and MV_2 can be used to bring CV_3 to 40. The right side of the figure shows similar behavior for the case with different priorities.
2、Next, the period with the active disturbance sequence is from step 20 to step 400. The left side of the figure shows how SMOCPro cannot control any of the CVs to their setpoints. Again, this is due to the fact that all three of them are at the same priority and with the same weights and only two MVs available for control. The right side of the figure shows the desired behavior where the user has specified the priorities and SMOCPro only gives up on the lowest priority CV and controls the remaining two CVs to their corresponding setpoints.
3、Just as in the previous cases, after step 400 SMOCPro is able to manipulate all three MVs again and uses all three handles to bring the three CVs to their setpoints, regardless of the choice of CV priorities.
**Take Home Message **
The CV priority concept and its correct implementation when it comes to ramp CVs is extremely important. The user must take care in specifying ramp CV priorities in such a way that if either competing control objectives and/or crippled mode are encountered then the control behavior will be the desired behavior on a per application basis. When possible and practical, ramp CVs should not be placed at the same priority level if they share all MVs and there is a potential for encountering crippled mode. The important thing to consider here is the case where the priorities are incorrectly setup which can potentially result in a ramp CV “ramping up or down” without control.
2016.6.5
