WalterI'm on the same page as Kumar. The EDA tool can set the sample_interval to anything that it desires, to generate uniformly sampled data that is as accurate as required. A model that requires a fixed sample_interval is contrary to the spec and is non-compliant. There is nothing new here. If a model is non-compliant, it needs to be sent back to the model maker and get fixed. How is this different than any other non-compliant IBIS model? Sometimes an IBIS model quality problem can be fixed by the user. Sometimes it cannot be fixed. Any fix at the EDA tool level using re-sampling is like putting lipstick on a pig. In the end, it's just a pig that does what it wants to do, not what it should do.
Scott Scott McMorrow Teraspeed Consulting Group LLC 121 North River Drive Narragansett, RI 02882 (401) 284-1827 Business (401) 284-1840 Fax http://www.teraspeed.com Teraspeed® is the registered service mark of Teraspeed Consulting Group LLC On 9/29/2011 10:19 AM, Walter Katz wrote:
Kumar, On page 188 of IBIS 5.0: | 3.2.2 Arguments | | 3.2.2.1 wave | | A vector of a time domain waveform, sampled uniformly at an interval | specified by the ‘sample_interval’ specified during the init call. The | wave is both input and output. The EDA platform provides the wave. The | algorithmic model is expected to modify the waveform in place by applying | a filtering behavior, for example, an equalization function, being | modeled in the AMI_Getwave call. The waveform in and out of AMI_GetWave is " sampled uniformly at an interval specified by the ‘sample_interval’ specified during the init call" I think this is "uniformly sampled data". So your comment "Your proposal will prevent the eda tool to pass continuous waveform as accurately as possible." Is not logical and does not apply. What did you mean by "Your proposal will prevent the eda tool to pass continuous waveform as accurately as possible." Walter -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of ckumar Sent: Thursday, September 29, 2011 10:09 AM To: Arpad_Muranyi@xxxxxxxxxx Cc: IBIS-ATM Subject: [ibis-macro] Re: Samples per bit for AMI there are various ways of "digitizing". You probably meant uniformally sampled data. Your proposal will prevent the eda tool to pass continuous waveform as accurately as possible. On Thu, 29 Sep 2011 13:54:40 +0000, "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx> wrote:Kumar, Regarding: "It does not make any sense for the eda tool to be doing the part of the models job.", I don't think this is what I am suggesting. In the computer world there is no such thing as continuous waveform. Everything is sampled, digitized. I don't see how we can go without knowing how things are digitized. Thanks, Arpad=========================================================================-----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of ckumar Sent: Thursday, September 29, 2011 7:25 AM To: twesterh@xxxxxxxxxx Cc: IBIS-ATM Subject: [ibis-macro] Re: Samples per bit for AMI I do not agree. Resampling may part of a adc(analog to digitalconversion)which may be more or less complex. The key part is that the model should treat the incoming waveform as an analog/continuous waveform and take it from there. It does not make any sense for the eda tool to be doing the part of the models job. On Thu, 29 Sep 2011 08:10:46 -0400 (EDT), "Todd Westerhoff" <twesterh@xxxxxxxxxx> wrote:I'm with Arpad on this (which should surprise no one). This is a practical issue - there are models out there withundocumentedrequirements (e.g. samples per bit) and this is a standardized way of documenting those requirements so that users (and tools) can dosomethingabout them. The mere act of documenting a requirement should serve asahint to the model developer that generalizing the model might be a good idea. What bothers me most are models that have an undocumented requirement,runwhen that requirement isn't met, but produce incorrect results. What's the chance that the user notices a problem and does something about it? Virtually nil, in my experience. The models that flatline or crash(I'veseen both) are actually doing the user a favor. Better to have noresultthan the wrong one. No one is suggesting that having a fixed (or limited) Samples_Per_Bit setting is a good idea. We're not promoting bad programming practices; we're trying to ensure good simulation results. If others are willingtotell system designers to wait while suppliers rewrite algorithmicmodels,great. Seems silly to me, but maybe their users are more patient than mine. Todd.--------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe1 + +^ i 0 Z ? f u p i y h m y b ( {.n + zwZ 隊T艸 + -~ +- + - {.n + --------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe --------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe
--------------------------------------------------------------------- IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe