The last one may surprise you but I do feel that including for
example a 3rd VT table buys more than increasing the number of points
for most models.
I do agree the number of points could be increased to say 256 to
pick yet another arbitrary spot on the wall. I would prefer to
see a model creator like Arpad propose a new limit based on=20
actual demonstrated requirements where some form of data reduction is
I feel we should keep this number as small as we can and still create
accurate models to insure the files sizes and download times are reasonable.
I think the biggest problem here is spice to ibis. People are always
generating models with the maximum number of points. I see many many models
that will work EXACTLY the same with 1/3 this many points if they are placed
sensibly instead of using a linear spread.
I am worried that if we set the limit at 1000 we will have all the new
models with 1000 points......
Just doesn't make sense to me sorry... especially with more and more
VT tables being used.
At 05:00 PM 6/8/99 -0700, Scott McMorrow wrote:
>I second Jon's opinon.
>There is no real reason to limit the number of points in
>IV or VT tables. I have often used a simulator which allows
>an arbitrary number of points over 100 to create high
>resolution simulations. 256 to 512 is often useful to
>capture rising edge timing information accurate to 1ps, along
>with driver overshoot behavior to within 1 mv of HSpice
>Model size makes no difference to me. It is the result that
>> I agree with Weston.
>> Either that or remove the quite artificial limit of number of points in
>> I have actually been faced with the problem that even with software to
>> extra points I cannot
>> create IBIS models to the accuracy that I desire with the 100 point
>> jon powell
>> Viewlogic Consulting Services
>> Beal, Weston wrote:
>> > Kellee,
>> > You're disagreeing a mute point. Your point was the same point I was
>> > to state by saying, "the IBIS creator tool should have an algorithm to
>> > remove points in linear regions." We should delete all these extra=
>> > points. The problem that s2ibis has now is that all points are equal
>> > difference. They should be closer in knee points and very sparse is
>> > regions. The IBIS creator tool should have an algorithm to clean out
>> > data.
>> > So, I agree with you and now you can agree with me.
>> > Later,
>> > Weston Beal
>> > Signal Integrity Engineer
>> > Compaq Computer Corp.
>> > -----Original Message-----
>> > From: Kellee Crisafulli [mailto:email@example.com]
>> > Sent: Monday, 07 June, 1999 2:19 PM
>> > To: Beal, Weston; firstname.lastname@example.org
>> > Subject: RE: [SI-LIST] : IBIS Subcommittee
>> > Review Spice to IBIS
>> > Hi
>> > I have a comment on Weston's comment on the number of
>> > points.
>> > I disagree on one point. Instead of increasing the
>> > of points generated
>> > in the IBIS file the spice to IBIS tool should improve
>> > quality of the
>> > points
>> > choosen.
>> > I can hand build files with 50 points that out perform
>> > with 400 points.
>> > The big gain is that the FILE SIZE is reduced with=
>> > accuracy.
>> > Large IBIS files will take up many megabytes on 1000's=
>> > hard drives.
>> > The V/I and V/T tables are the largest part of IBIS
>> > Increasing them 4 x will generally increase the file
>> > x or more.
>> > >The third thing that I changed was the number of
>> > the time
>> > >waveforms from 50 to 101. I have to remove one point=
>> > comply with the
>> > >golden parser, but I get better detail. On the issue=
>> > number of points in
>> > >a curve or waveform, I think the user should be able=
>> > define any degree of
>> > >granularity and the IBIS creator tool should have an
>> > algorithm to remove
>> > >points in linear regions. If the resulting curve
>> > too many points,
>> > >then increase the linearity tolerance and try it=
>> > Best wishes...
>> > Kellee
Have a great day....
HyperLynx, a division of Pads Software Inc.
SI,EMC,X-talk and IBIS tools for the Windows platform