現(xiàn)在，讓我們通過(guò)步驟仿真來(lái)驗(yàn)證預(yù)期的行為。為了確認(rèn)計(jì)算結(jié)果，我們可以利用調(diào)試瀏覽器，并打開(kāi)內(nèi)核調(diào)試。在第5步時(shí)我們遵循下列條目：
?頂部質(zhì)量和底部質(zhì)量CVs都是控制問(wèn)題的一部分（沒(méi)有被移除）；
?子控制器處于活動(dòng)狀態(tài)；
?控制器處于優(yōu)化模式；
?由于計(jì)算7規(guī)定了經(jīng)濟(jì)函數(shù)追蹤濾波器時(shí)間常數(shù)必須介于5~10mins，輸入的值100mins將被截?cái)嘣谏舷?0mins。
?對(duì)底部質(zhì)量，由于經(jīng)濟(jì)優(yōu)化的結(jié)果，穩(wěn)態(tài)目標(biāo)被推動(dòng)到觸碰約束。
在第6步我們注意到：
?底部質(zhì)量CV被移除（因?yàn)榈撞繙囟群偷撞抠|(zhì)量POVs都斷開(kāi)）；
?因?yàn)榈撞抠|(zhì)量CV不再是控制問(wèn)題的一部分，內(nèi)核后計(jì)算中的約束活動(dòng)變?yōu)?。
在第7步，我們斷開(kāi)頂部溫度測(cè)量。鑒于頂部質(zhì)量測(cè)量依舊可用，頂部質(zhì)量CV并沒(méi)有被移除。
在第8步，我們需遵循以下條目：
?由于頂部溫度和頂部質(zhì)量測(cè)量量都斷開(kāi)，頂部質(zhì)量CV將被移除（計(jì)算2）；
?因此，子控制器被調(diào)至非活動(dòng)狀態(tài)（頂部和底部質(zhì)量CVs都被移除了）；
?由于控制器只包含了一個(gè)子控制器，而這個(gè)子控制器現(xiàn)在處于非活動(dòng)狀態(tài)，控制器將切換到掛起狀態(tài)。
現(xiàn)在檢查確認(rèn)步驟9的底部溫度測(cè)量處于重新連接狀態(tài)。我們預(yù)計(jì)底部質(zhì)量不會(huì)被移除。然后子控制器的請(qǐng)求狀態(tài)是活動(dòng)的，且預(yù)計(jì)現(xiàn)在控制器將切換回優(yōu)化模式。下面的截圖證實(shí)了步驟9的預(yù)期行為。
帶回家的消息
SMOCPro中內(nèi)置的計(jì)算引擎是可用于運(yùn)行簡(jiǎn)單以及精密用戶代碼的一個(gè)工具。有兩種允許的計(jì)算類型：預(yù)內(nèi)核和內(nèi)核后計(jì)算。預(yù)內(nèi)核計(jì)算用于修改控制器執(zhí)行之前輸入的內(nèi)核參數(shù)。內(nèi)核后計(jì)算可用于記錄參數(shù)和存儲(chǔ)歷史。提供給了用戶有關(guān)參數(shù)和函數(shù)的一個(gè)完整列表，若要查閱，請(qǐng)參閱本用戶指南的計(jì)算部分。
原文：
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
