What kind of data do I need to calibrate an Enginuity model?
You will need two kinds of data: (1) Model parameter data which describes the physical nature and the geometry of the engine components (inertia of rotating parts, manifold volumes, cylinder bore and stroke, valve lift profiles, etc.) and (2) empirical data which describes the engine performance under stationary conditions (engine mapping data). The latter reflects engine dyno data which OEMs typically collect according to standardized test procedures for each of their engine types. In general, engine mapping data is a collection of steady-state values of a selected number of sensor and actuator signals in a selected number of engine operating points. The selected engine operating points typically span the entire engine operating envelope. The set of required mapping data signals needed to calibrate a particular Enginuity engine model depends on the engine model type, i.e., PFI, CIDI, SIDI, and HCCI (since the required set is a subset of the entire set of model input and output signals
Related Questions
- Assuming we successfully use the current data to calibrate/validate the model, would the resulting model be applicable to other years? Also, what will happen with different dam-release alternatives?
- Does VelocityManager model velocities from well data and seismic velocities (stacking and migration velocities)?
- Is there a way to transfer data from the 2008 eLogic Model into the 2009 eLogic Model?
