gsphelp  Creating an engine project

<< Click to Display Table of Contents >>

Navigation:  GSP environment > GSP Projects > Project window > Building models >

gsphelp  Creating an engine project

Previous pageReturn to chapter overviewNext page

The creation of a well organized model ensures proper encapsulation of the modeling task. The creation of an engine layout is described in the Creating a model layout. This section will more closely describe the model design philosophy per the developers of the GSP gas turbine simulation tool.

 

A base configuration or reference model is always the starting point for a model and should contain at least the components that are shared with all child configurations. This means for instance that an incomplete  cycle can be modeled here (e.g. only gas path components and no fuel control components when the modeler is interested in e.g. manual fuel control and governor fuel control simulation). Note that the base configuration model can also be empty, this can be beneficial, but breaks with the inheritance approach.

 

A reference model should always be followed by a model configuration where the modeler completes the engine cycle (e.g. adding the fuel controller). To tune this model it is advised to always immediately create a design case model under this configuration to obtain a means to fine tune the created model configuration. Once the model design point (or better called, the reference point as the design of the actual engine not necessarily is the data the modeler has to create the model reference point; an engine design usually is a concession or trade-off between multiple design/important engine power settings and operational conditions) is fine-tuned, the model component input should be copied into the parent model configuration (and even further to the reference model).

 

Once the parent of the tuning case model (and even higher up the tree to the base configuration model) is updated, the model is ready for either sibling off-design case models (do not put these under your tuning case!) or child configurations as siblings to the tuning case model.

 

Please take a look below at the model setup of a turboshaft engine model where the base configuration model does not contain a fuel controller as the model is used for steady state analysis and transient analysis. Also note that the Manual_fuel_control configuration contains configurations that alter the model to either allow the user to input power (PW_as_input) or input fuel flow (PW_as_state) as power setting.

 

CreateModel_01

 

CreateModel_02