Search Results

Simulation and testing are often done by different engineers in different departments of a company. This can lead to disconnects and unrealistic predictions, especially if the person doing simulations does not have an experimental background. On the other hand, experimental results can also include errors that result in misleading answers. It is important for the engineer doing either testing or simulation to have a good understanding for what results are plausible and what results might be suspect. This paper will provide examples where error crept into testing or simulation that could have been caught and corrected early if a good feel for “reasonable” results had been in place. The importance of understanding how a software package is analyzing the data will be explained, since settings buried deep within a menu structure can drive misleading results.