Hi, Walter; Thanks for your clarification. Based on your reply I think we should make it clear in the BIRD that if the .ami file specifies jitter usage is In or InOut, EDA tool should assume model handles jitter in GetWave if it exists. Fangyi From: Walter Katz [mailto:wkatz@xxxxxxxxxx] Sent: Thursday, December 10, 2009 3:32 AM To: RAO,FANGYI (A-USA,ex1); ibis-macro@xxxxxxxxxxxxx Subject: RE: [ibis-macro] jitter parameter usage in the proposed BIRD Fangyi, Jitter can be handled by the simulator as it sees fit. I can be put on the stimulus, or it can be used when processing the results. IBIS AMI does not tell the EDA tool how to incorporate Jitter, it just expresses to the EDA tool how much there is. SO the AMI standard should not tell the EDA tool how to use it. IC Vendors can choose how to describe to the EDA tool how much Jitter there is. An IC Vendor can choose to implement components of Jitter in their model. This Jitter can be hard coded within the model, are passed into the model as a Usage In parameter if it is configurable. Walter Walter Katz 303.449-2308 Mobile 720.333-1107 wkatz@xxxxxxxxxx www.sisoft.com -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of fangyi_rao@xxxxxxxxxxx Sent: Wednesday, December 09, 2009 10:05 PM To: ibis-macro@xxxxxxxxxxxxx Subject: [ibis-macro] jitter parameter usage in the proposed BIRD Hi, Walter; Is my understanding of the usage of jitter reserved parameter in your new BIRD correct? Tx jitter if GetWave exists Usage Info/Out: jitter added by simulator Usage In/InOut: jitter added by model dll if no GetWave always added by simulator Rx jitter if GetWave exists and returns clock ticks Info/Out: jitter added by simulator In/InOut: jitter added by model dll if no GetWave, or GetWave exists but doesn't return clock ticks always added by simulator Thanks, Fangyi