>>So perhaps the best resolution is just to require the max C_comp value
>>to be positioned in the "max" column, regardless of conditions under which
>>it is extracted. The surprising tradeoff is that by overriding some
>>extractions which give the most accurate model, one creates a set of models
>>which function in a more consistent manner and which taken together are
>>more useful for worst case analysis and design.
This requirement would effectively make the C_comp value an un-correlated variable,
so If we were doing a monte-carlo simulation it would enter in as another free variable.
To me this change is no different than the current specification and so I can see no
need for the bird (at least, on this point).
Of course, we could come up with a COR_C_comp or some such thing.
I am thinking that we are moving toward a situation where we want more that two variables
and perhaps multiple corners and this whole discussion may be more appropriate aimed at
a major 3.0 type enhancement.
jonp
Received on Thu Feb 9 10:58:28 1995
This archive was generated by hypermail 2.1.8 : Fri Jun 03 2011 - 09:52:28 PDT