?關于外部輸入位號的仿真，當前（PCTP 2009 Build 1）版本的一個重要限制是值中缺少原始的“存儲器”。例如，如果已經開發了用于檢查外部輸入位號覆蓋功能的計算，則在激活位號之后的仿真中，仿真器將永遠不會恢復到原始值。
?由于實現方式不同，離線仿真（PCTP）行為與在線EXASMOC嵌入行為是不同的。當處理遞歸計算時，經常會遇到這個問題。例如，令[A] = [A] +1，并假設[A]的初始值= 10。則在每個內核執行時，離線仿真會增加[A]的值，即11,12,13 ...，然而，在線EXASMOC控制器將保持[A]的值恒定，即11,11,11，...
?在方案構建過程中必須指定許多重要的可在線修改的參數。否則控制器構建時將使用“默認”值。這些參數為：
? CV優先級
? CV設定點跟蹤濾波器
? DV濾波器時間常數
? POV脈沖因子
?從PCTP 2010 Build 1版本開始，用戶可以為白噪聲指定隨機數生成器種子。種子值可以是零或任何正數。默認種子值為0，其與先前版本中的行為一樣：當每個仿真運行時種子將在內部改變，由一個仿真跳至另一個仿真時將生成不同的噪聲序列。如果用戶指定了一個非零值的種子，則除非用戶更改種子，否則在運行時噪聲序列是相同的（可重復的）。此功能對于比較不同整定參數時，控制器對相同噪聲干擾響應性能非常有用。
?注意：即使噪聲種子參數在通用選項卡中的每個干擾和子控制器選項卡中的MV出現，也不能為單個干擾或MV指定噪聲種子。改變任何給定仿真方案的噪聲種子參數將影響干擾和MVs的所有噪聲干擾。如果用戶要求從一個運行轉到另一個運行時噪聲序列自動改變，則用戶必須確保所有干擾和MVs的噪聲種子參數值被設置為零（0）。
原文：
? An important limitation of the current (PCTP 2009 Build 1) release with regards to the simulation of external input tags is the lack of original “memory” in the values. For example, if a calculation has been developed to check the override function of an external input tag, in simulation once the tag has been activated, the simulator will never revert back to the original value.
? Due to different implementations, the offline simulation (PCTP) behavior is NOT identical to the online EXASMOC embedding behavior. The problem is mostly observed when dealing with recursive calculations. For example, let [A]=[A]+1 and assume the initial value of [A] =10. The offline simulation increases the value of [A] at each kernel execution, i.e. 11, 12, 13, ..., however, the online EXASMOC controller keeps the value of [A] constant, i.e. 11, 11, 11, ...
?There are a number of important online modifiable parameters that MUST be specified during the scenario build process. Otherwise ‘default’ values are used in the controller build. The parameters are:
? CV priorities
? CV setpoint tracking filters
? DV filter time constants
? POV impulse factors
? ?Starting with the PCTP 2010 Build 1 release, users can specify the seed of the random number generator for the white noise. The seed value can be zero or any positive number. The default seed value is 0, which has the same behavior as in previous releases: the seed is changed internally for each simulation run, generating different noise sequences from simulation run to simulation run. If users specify a non-zero seed, the noise sequence is the same (repeatable) from run to run until users change the seed. This functionality is very useful to compare controller performance with different tunings reacting to the same noise disturbance.
?NOTE: Even though the Noise Seed parameter appears with every disturbance in the general tab and MV in the sub-controller tabs one cannot specify noise seeds for individual disturbances or MVs. Changing any Noise Seed parameter for the given Simulation Scenario will affect all noise disturbances for the disturbances and MVs. If the user requires the noise sequence to automatically change from run to run then the user must ensure that the Noise Seed parameter values for ALL the disturbances and MVs are set to zero (0).
2010.10.16
