在這種情況下，我們模擬一個(gè)影響底部質(zhì)量的斜坡干擾。這一干擾會(huì)導(dǎo)致底部質(zhì)量瞬間超過(guò)上限。如果該計(jì)算打開(kāi)，底部質(zhì)量CV違反上限后，我們預(yù)計(jì)有以下行動(dòng)：
?計(jì)算3將頂部質(zhì)量CV的priority（優(yōu)先級(jí)）設(shè)定為10；
?計(jì)算5將reflux（回流）的max move size（最大動(dòng)作幅度）設(shè)定為150；
?計(jì)算6將再沸器負(fù)荷的max move size（最大動(dòng)作幅度）設(shè)定為1.5；
當(dāng)?shù)撞抠|(zhì)量CV值在范圍之內(nèi)時(shí)，我們預(yù)計(jì)：
?計(jì)算3將把頂部質(zhì)量CV的priority（優(yōu)先級(jí)）恢復(fù)到1；
?計(jì)算5將reflux（回流）的max move size（最大動(dòng)作幅度）恢復(fù)到100；
?計(jì)算6將再沸器負(fù)荷的max move size（最大動(dòng)作幅度）恢復(fù)到1.5。
若要查看計(jì)算結(jié)果，當(dāng)控制器拒絕了仿真底部質(zhì)量干擾時(shí)，我們將內(nèi)核調(diào)試文件打開(kāi)并保持25步。
逐步運(yùn)行仿真直到第15步。如下面屏幕截圖所示，在這一點(diǎn)，我們可以通過(guò)單擊“bug”按鈕打開(kāi)調(diào)試文件：

?我們注意到的第一點(diǎn)是，盡管底部質(zhì)量在范圍內(nèi)，EF tracking filter（EF跟蹤濾波）值依舊改為300秒。注意在原始方案中我們將EF tracking filter設(shè)定為0.0。通過(guò)確認(rèn)EF tracking filter至少是5mins，計(jì)算7確認(rèn)該過(guò)程不受到過(guò)于激烈的動(dòng)作。
?對(duì)于內(nèi)核后計(jì)算，我們注意到底部質(zhì)量CV的穩(wěn)態(tài)約束行為表示了值101。值101意味著由于經(jīng)濟(jì)函數(shù)原因（即經(jīng)濟(jì)優(yōu)化將一個(gè)變量推向約束），在穩(wěn)態(tài)時(shí)約束是活動(dòng)的。
當(dāng)?shù)撞抠|(zhì)量違反了上限，計(jì)算將分別把回流的最大動(dòng)作和再沸器負(fù)荷設(shè)置為150和1.5。

當(dāng)?shù)撞抠|(zhì)量違反了上限時(shí)，頂部質(zhì)量CV的優(yōu)先級(jí)將降為10。

在第6步，我們預(yù)計(jì)計(jì)算1將移去底部質(zhì)量CV。在第8步，我們預(yù)計(jì)由于計(jì)算2的原因，頂部質(zhì)量CV將被移去。隨后由于計(jì)算4，子控制器將切換到非活動(dòng)狀態(tài)。鑒于控制器只有一個(gè)子控制器，我們預(yù)計(jì)在第8步控制器將變成standby（待機(jī)）狀態(tài)。

原文：
In this case, we simulate a ramp disturbance that affects the bottom quality. This disturbance causes the bottom quality to exceed its upper limit in the transient. If the calculations are turned ON, we expect the following when the bottom quality CV violates its upper limit
? Calculation 3 sets the priority for the top quality CV to 10
? Calculation 5 sets the max move size for reflux to 150
? Calculation 6 sets the max move size for reboiler load to 1.5
When the bottom quality CV is within limits, we expect
? Calculation 3 reverts the priority for the top quality CV back to 1
? Calculation 5 reverts the max move size for reflux back to 100
? Calculation 6 reverts the max move size for reboiler load back to 1.5
To view the results for the calculations, we turn the kernel debug file ON for 25 steps while the controller rejects the simulated bottom quality disturbance.
Run the simulation stepwise until the 15th step. At this point, we may open the debug file by clicking on the “bug” button as shown in the screenshot below
?The first aspect we notice is that even though the bottom quality is within limits, the EF tracking filter value has changed to 300 seconds. Notice in the original scenario that we left the EF tracking filter at 0.0. By ensuring that the EF tracking filter is at least 5 minutes, calculation 7 ensures that the process is not subject to overly aggressive moves.
? For the post-kernel calculations, we notice that the steady-state constraint activity for the bottom quality CV indicates a value of 101. A value of 101 implies that the constraint is active at steady state due to economics (i.e. due to the economic optimization pushing the variable against a constraint).
When the bottom quality violates its upper limit, the calculations set the max moves for the reflux and reboiler load to 150 and 1.5 respectively.
The priority for the top quality CV is lowered to 10 when the bottom quality violates its upper limit.
Once the controller rejects the disturbance and brings the bottom quality within limits, the calculations revert the variables back to their nominal values.
**Simulation 2 **
The next simulation that we observe is called “Disconnected POVs.” The simulation parameters are shown below.
At step 6, we expect calculation 1 to remove the bottom quality CV. At step 8, we expect the top quality CV to be removed as a consequence of calculation 2. Subsequently, the sub-controller is turned inactive due to calculation 4. Since the controller has just the one sub-controller, we expect the controller to shed to standby at step 8.

2016.6.16