Road vehicles — Objective rating metric for non-ambiguous signals
Introduction: Computer Aided Engineering (CAE) has become a vital tool for product development in the automobile industry. Various computer programs and models have been developed to simulate dynamic systems. To maximize the use of these models, the validity and predictive capabilities of these models are assessed quantitatively. Model validation is the process of comparing CAE model outputs with test measurements in order to assess the validity or predictive capabilities of the CAE model for its intended usage. The fundamental concepts and terminology of model validation have been established mainly by standard committees including the American Institute of Aeronautics and Astronautics (AIAA)[2], the American Society of Mechanical Engineers (ASME) Standards Committees on verification and validation of Computational Solid Mechanics[3] and Computational Fluid Dynamics and Heat Transfer[4], the Defense Modeling and Simulation Office (DMSO) of the U.S. Department of Defense (DoD)[5], the United States Department of Energy (DOE)[6] and various other professional societies [19],[20]. One of the critical tasks to achieve quantitative assessments of models is to develop a validation metric that has the desirable metric properties to quantify the discrepancy between functional or time history responses from both physical test and simulation result of a dynamic system[7],[16],[17]. Developing quantitative model validation methods has attracted considerable researchers’ interest in recent years [11]
Scope: This document provides validation metrics and rating procedures to calculate the level of correlation between two non-ambiguous signals obtained from a physical test and a computational model and it is aimed at vehicle safety applications. The objective comparison of time-history signals of model and test is validated against various loading cases under different types of physical loads such as forces, moments and accelerations. However, other applications can be possible too, but are not within the scope of this document. NOTE Annex A gives some examples of the application of this document.