Re: BIRD25.1 DATA DERIVATION EXPANSION

Text item:

Bob, Jon, et al,

Perhaps we need to rev V1.1 to V1.2 to clarify this. I think we should check
with model developers and see how they have interpreted this in the past. Let
them know of the clarification, and let them rev their models if they
interpreted it backwards. Fixing the column placement and rev-ing the model to
V1.2 or V2.2 would allow them to continue to supply C_comp in existing models.

Will Hobbs
Intel Corp.

|
| The [Model] sub-parameter C_comp allows optional "min" and "max" values.
| If extractable, the values under the "min" and "max" columns shall be
| obtained under the same conditions that the other data is extracted.
| Otherwise, if only the range of values is known, the smallest value
| should be placed in the "min" column, and the largest value in the
| "max" column.

I feel that this statement is too weak. We are proposing a change to the way a
model is created. Presumably this means a change to the IBIS version number
(2.1 -> 2.2). I think it is reasonable to require that 2.2 rev. models follow
the stronger requirement of min max definition. If you don't know where the data
came from then it is either a) a 2.1 model b) unsuitable for use c) wrong.

The problem is that if we allow this multiple definition there is no
way to determine
how the data was collected and so me must ALWAYS assume that the data
is WRONG and so
this strengthening does not accomplish anything.

It is as if we have said: You can fix the problem or not, and you don't
have to tell
us which you did.

respectfull submitted,
jon powell

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Subject: BIRD25.1 DATA DERIVATION EXPANSION
In-Reply-To: Bob Ross's message of Tue, 7 Feb 95 19:18 PST <m0rc2vg-000Gi0C@icx
Cc: uunet!uunet!vhdl.org!ibis@uunet.uu.net
To: uunet!uunet!icx.com!bob@uunet.uu.net
Received: by f14.qdt.com (4.1/SMI-4.1)
        id AA10649; Wed, 8 Feb 95 10:24:03 PST
Message-Id: <9502081825.AA28081@hal.qdt.com>
From: uunet!qdt.com!jonp@uunet.uu.net (Jon Powell)
Date: Wed, 8 Feb 95 10:25:37 PST
Received: from f14.qdt.com by hal.qdt.com (4.1/SMI-4.1)
        id AA28081; Wed, 8 Feb 95 10:25:37 PST
Received: from hal.qdt.com by qdt.com (4.1/SMI-4.1)
        id AA00578; Wed, 8 Feb 95 10:22:19 PST
Received: from qdt.UUCP by uucp1.UU.NET with UUCP/RMAIL
        ; Wed, 8 Feb 1995 14:03:20 -0500
Received: from uucp1.UU.NET by relay3.UU.NET with SMTP
        id QQycfs24879; Wed, 8 Feb 1995 14:03:34 -0500
Received: from qdt.com by hal.qdt.com (4.1/SMI-4.1)
        id AA28445; Wed, 8 Feb 95 11:06:24 PST
Received: from hal.qdt.com by qdt.com (4.1/SMI-4.1)
        id AA00765; Wed, 8 Feb 95 11:03:07 PST
Received: from qdt.UUCP by uucp2.UU.NET with UUCP/RMAIL
        ; Wed, 8 Feb 1995 15:20:43 -0500
Received: from uucp2.UU.NET by relay3.UU.NET with SMTP
        id QQycfx12482; Wed, 8 Feb 1995 15:20:49 -0500
Received: from relay3.UU.NET by vhdl.vhdl.org (4.1/SMI-4.1/BARRNet)
        id AA02242; Wed, 8 Feb 95 12:26:55 PST
Received: from vhdl.vhdl.org by hermes.intel.com (5.65/10.0i); Wed, 8 Feb 95 12:
Received: from hermes.intel.com by ichips.intel.com (5.64+/10.0i); Wed, 8 Feb 95
Received: from ichips.intel.com by relay.jf.intel.com with smtp
        (Smail3.1.28.1 #2) id m0rcJDd-000twcC; Wed, 8 Feb 95 12:42 PST
Received on Wed Feb 8 13:13:21 1995