The National Academies Press

Currently Skimming:

Pages 113-127

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 113... ... 111 CHAPTER 4 PROCEDURES INTRODUCTION The purpose of this Chapter is to present potential procedures for verification and validation for computer simulations in roadside safety applications. The procedures described herein apply primarily to incremental improvements to roadside safety hardware. Read the entire page →
From page 114... ... 112 DEFINITIONS The definitions of verification, validation and calibration, as they are used in these procedures, were adopted with slight modifications from the definitions presented in the ASME "Guide for Verification and Validation in Computational Solid Mechanics," ASME V&V 102006.(17) These definitions were discussed in detail in Chapter 2 but are summarized below. Read the entire page →
From page 115... ... 113 Calibration Calibration is often confused with validation and verification. Verification and validation involve comparisons with physical experiments or known solutions that are independent of the model development, whereas calibration is the use of physical experiments, the literature or analytical solutions to estimate the parameters needed to develop the model. Read the entire page →
From page 116... ... 114 Figure 41. Roadside safety validation and incremental design process. Read the entire page →
From page 117... ... 115 1. Identify the baseline experiment, 2. Read the entire page →
From page 118... ... 116 Build the Model Next in Figure 41 on the left hand side, models of the vehicle, barrier and support conditions are developed to exactly match the baseline experiments. The development of the models may involve calibration, verification or validation of parts, materials, subassemblies and assemblies of the complete model. Read the entire page →
From page 119... ... 117 level of the model hierarchy would be unreasonably burdensome and may not even be possible in some cases. Calibrating and validating as many of the components as possible will, however, increase the overall confidence in the accuracy and robustness of the model predictions. Read the entire page →
From page 120... ... 118 phenomena that are included in the model so that subsequent users of the model or reviewers of the results will know what types of phenomena can reasonably be expected. Examples of roadside hardware and vehicle PIRTS are included in Chapter 6 and Appendix C Read the entire page →
From page 121... ... 119 of each "Comparison Metric Evaluation Table" (e.g., Table C6-2) and entered into the PIRT (e.g.., Table C6-8) Read the entire page →
From page 122... ... 120 The first part, basic information, lists important information about what the baseline test is, what organization performed the baseline test, what organization performed the numerical solution, the impact conditions, etc (see Appendix E) Read the entire page →
From page 123... ... 121 percent of the linear and angular momentum in the crash test, the longitudinal channel will have a weight of 0.8 and the other channels will have smaller weights summing to 0.2 Table E-3, the multi-channel option, has been included in the validation procedure to account for such cases. The user can use RSVVP in multi-channel mode to calculate the weighted Sprague-Geers and ANOVA metrics for the six channels of data that are typically collected in full-scale crash testing of roadside hardware; namely, 1) Read the entire page →
From page 124... ... 122 350/MASH limit on the criterion was taken and the value corresponding to 20 percent of the Report 350/MASH acceptance value was calculated. For example, Report 350 limits the ridedown accelerations to 20 g's so 20 percent of 20 g's is 4 g's. Read the entire page →
From page 125... ... 123 and the pickup truck) should be validated and documented in a validation report as described in the last section. Read the entire page →
From page 126... ... 124 3. A vehicle PIRT similar to the examples provided in Chapter 6 and Appendices C7-C8. Read the entire page →
From page 127... ... 125 decision-maker is satisfied with the documentation and the results, an acceptance letter can be written in exactly the same way as is currently done for crash tested hardware. Another important implementation detail is providing access to the RSVVP code, user's manual, benchmark models and benchmark case documentation. Read the entire page →

From page 113...

... 111 CHAPTER 4 PROCEDURES INTRODUCTION The purpose of this Chapter is to present potential procedures for verification and validation for computer simulations in roadside safety applications. The procedures described herein apply primarily to incremental improvements to roadside safety hardware.