案例8：使用计算 –使用案例1中的脱丁烷塔来研究一个普通案例-3

现在，让我们通过步骤仿真来验证预期的行为。为了确认计算结果，我们可以利用调试浏览器，并打开内核调试。在第5步时我们遵循下列条目：
•顶部质量和底部质量CVs都是控制问题的一部分（没有被移除）；
•子控制器处于活动状态；
•控制器处于优化模式；
•由于计算7规定了经济函数追踪滤波器时间常数必须介于5~10mins，输入的值100mins将被截断在上限10mins。
•对底部质量，由于经济优化的结果，稳态目标被推动到触碰约束。

在第6步我们注意到：
•底部质量CV被移除（因为底部温度和底部质量POVs都断开）；
•因为底部质量CV不再是控制问题的一部分，内核后计算中的约束活动变为0。

在第7步，我们断开顶部温度测量。鉴于顶部质量测量依旧可用，顶部质量CV并没有被移除。

在第8步，我们需遵循以下条目：
•由于顶部温度和顶部质量测量量都断开，顶部质量CV将被移除（计算2）；
•因此，子控制器被调至非活动状态（顶部和底部质量CVs都被移除了）；
•由于控制器只包含了一个子控制器，而这个子控制器现在处于非活动状态，控制器将切换到挂起状态。

现在检查确认步骤9的底部温度测量处于重新连接状态。我们预计底部质量不会被移除。然后子控制器的请求状态是活动的，且预计现在控制器将切换回优化模式。下面的截图证实了步骤9的预期行为。

带回家的消息
SMOCPro中内置的计算引擎是可用于运行简单以及精密用户代码的一个工具。有两种允许的计算类型：预内核和内核后计算。预内核计算用于修改控制器执行之前输入的内核参数。内核后计算可用于记录参数和存储历史。提供给了用户有关参数和函数的一个完整列表，若要查阅，请参阅本用户指南的计算部分。

---

原文：
Let us now step through the simulation to verify the expected behavior. To confirm the results from calculations, we utilize the debug viewer and turn the kernel debug on. At step 5, we observe the following：
• Both the top quality and bottom quality CVs are part of the control problem (not removed).
• The sub-controller is active.
• The controller is in optimization mode.
• Because calculation 7 stipulated that the economic function tracking filter time constant must lie between 5 and 10 minutes, the entered value of 100 minutes is truncated at the upper bound of 10 minutes.
• For the bottom quality, the steady-state target is pushed against a constraint as a consequence of the economic optimization.
At step 6, we notice that
•The bottom quality CV is removed (since both bottom temperature and bottom quality POVs are disconnected)
•Because the bottom quality CV is no longer a part of the control problem, the constraint activity in the post kernel calculation changes to 0.
At step 7, we disconnect the top temperature measurement. The top quality CV is not removed since the measurement for the top quality is still available.
At step 8, we observe the following
• Because the measurements for top temperature and top quality are disconnected, the top quality CV is removed (calculation 2)
• Consequently, the sub-controller is turned inactive (both top and bottom quality CVs are removed)
• Since the controller contains only one sub-controller, and that sub-controller is now inactive, the controller sheds to standby
Now examine the status at step 9 where the bottom temperature measurement is reconnected. We expect the bottom quality to not be removed. Subsequently, the sub-controller request status is active and the controller now is expected to switch back to optimize mode. The screenshot below confirms the expected behavior at step 9.
Take Home Message
The Calculation engine built into SMOCPro is a tool that can be used to run simple, as well as, elaborate user code. There are two types of calculations allowed: Pre-kernel and Post-kernel calculations. The pre-kernel calculations serve to modify the parameters entering the kernel before the controller execution. The post-kernel calculations may be used to record parameters and historize them. For a complete list of parameters and functions available to the user, please refer to the Calculations section of this User’s Guide.

---

2016.6.19