TGSim Plus™—Real-Time Dynamic Simulation Suite of Gas Turbine Systems for the MATLAB®/Simulink® Environment
Round 1
Reviewer 1 Report
Your paper is well written. However I appreciate if you could add a chapter on LIST OF SYMBOLS; ABBREVIATIONS to make your paper more easily understandable. In Addition, please add figures to the axes of Figure 7 and show the origin of the coordinate systems.
Please correct some minor spelling Errors:
i.e. l. 26 Comparison with Benchmark design ..... shows
Author Response
Thank you very much. We have correct some minor spelling Errors:
line 21: Simulink®
line 27: shows
line 75: Simulink®
line 103 - 107: Additional info about solver.
line 441: Figure 7: added axes tick labels
line 415 - 416: Figure 7: amended caption
line 428: Figure 6
line 430: Figure 6
line 547: New section “List of symbols and abbreviations” with the table below.
line 577 - 578: Added Reference item 15
Reviewer 2 Report
-
- there are few commercial modelling/simulation tools are available (like EASY5, SAE, 3Keymaster etc.) could you please make a review/comparison to your TGSIM which is MATLAB/SIMULINK based
- you mentioned offline mode of the hardware (control system), could you please explain more of transfer/emulation of control SW, i.e. how do you convert the control system SW(logic to the SIMULINK blocks?
- Figure2. The signal name of the output of the MUX must be ‘WS_Plant_in’ instead of ‘WS_Plant_out’
- Figure6(d). the simulation result shall large deviation to the reference value around ignition speed. It shall be explained
Author Response
comments 1. there are few commercial modelling/simulation tools are available (like EASY5, SAE, 3Keymaster etc.) could you please make a review/comparison to your TGSIM which is MATLAB/SIMULINK based
response 1: please kindly see line 476 - 518 New section 4.3 “Comparison with other commercial software”.
comments 2. you mentioned offline mode of the hardware (control system), could you please explain more of transfer/emulation of control SW, i.e. how do you convert the control system SW(logic to the SIMULINK blocks?
response 2: Please kindly see line 76 - 91: More detailed info about offline simulated version of GTCS.
comments 3. Figure2. The signal name of the output of the MUX must be ‘WS_Plant_in’ instead of ‘WS_Plant_out’
response 3: Indeed, as to comment 3, we clarify that WS_Plant_out represents a bus (not a mux) of output signals from the whole controlled physical system (i.e. GT_MAIN_SYSTEM, AUX1 and AUX2), i.e. it is a model signals logging set.
It is then an output from the model.
Therefore changing its bus name into WS_Plant_in, would be incorrect and would lead to misunderstandings.
Finally the I/O interface between the physical and the controller systems are made through another interface that can have a sampling time different from that of the WS_Plant_out bus set.
comments 4. Figure6(d). the simulation result shall large deviation to the reference value around ignition speed. It shall be explained
response 4:Please kindly see line 433 - 434, Added “…, which could not be matched completely, in lack of details about the reference one.”
