|
Sanity Checks Ron Graham with Paul E. Bennett, David Bower, Christopher Garlick, Scott A. Hill, JKnapp, Pat March, Neill McKay, and John Nichols |
|
No matter how complex the structure or how sophisticated the computer software it is always possible to obtain most of the important design parameters by relatively simple hand calculations. Such calculations should always be done, both to check the computer results and to improve the engineer's understanding of the critical design issues.-- Engineering World, 12.97/01.98 I'm not sure where the term "sanity check" comes from. In my work experience, it seems engineers would have thought themselves insane to depend on results of complex calculations, simulations, finite element or finite difference analyses before looking at something simple first. We've learned this habit from our earliest days as students, when nearly all problems we faced were of the "given/find" variety: we were given all the inputs and were told to find a single output based directly on the inputs. In the workplace, problems seldom come nicely shrink-wrapped -- we have to find some of the inputs ourselves, and may not even know what outputs are of interest. Complex analyses of various types are generally developed with the intent of using them again and again. If the analysis you're doing isn't to be repeated, you may find that algebraic solutions have no value. If what you're doing is of general use, develop a general model; if it's specific, use the numbers directly -- even on "the back of the envelope" or "on a cocktail napkin" if that's what's at hand. It's a time-honored tradition!
In either case, try to solve the simplest problem you can with the numbers you have first. If the answers you get make sense, then you take a deep breath and move on. If the answers don't make sense, here are some questions you can ask yourself:
On manufacturing
|
|