Hi Arpad, My understanding about Walter's comment at yesterday's meeting on this issue is that, bit_time MUST be passed as seconds and, all other parameters can be passed in either seconds or UI (the choice of the model creator). I think this makes sense and should be the right way to interpret the Specification. Basically the EDA tool MUST pass the absolute bit_time (in second) at least in one occasion to the DLL before other parameters can use the UI unit. And bit_time is the only parameter to achieve this. A related comment on sample_interval, the 5.0 Specification hinted but did not clearly say that this should be a unitless fraction number. It would be better to clarify the unit of sample_interval as well. Because the term "interval" suggests it has the dimension of time (second). Regards, James -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Wednesday, April 18, 2012 3:09 PM To: IBIS-ATM Subject: [ibis-macro] A technical question on UI Hello everyone, An interesting question was raised in the Editorial Committee meeting this morning, and I got the AR to write an email on this reflector to solicit for some comments and feedback. The question is revolving around parameters which are expressed in terms of UI (unit interval). A statement was made in the Editorial Committee meeting this morning, that if a parameter is a Reserved_Parameter, the tool will know what to do with it because all Reserved_Parameters are completely described in the specification. However, if the parameter is a Model_Specific parameter, the EDA tool will have to convert the value from UI to time and pass the time value to the AMI executable model. For example, if the bit time is 400e-12 (ps) and the UI value is 0.5 for a certain parameter, the EDA tool would have to pass 200e-12 to the DLL, and not 0.5. (Please correct me if this summary is not accurate). This surprised me, because I don't recall anything in the IBIS-AMI specification that states that the EDA tool has to convert parameters expressed in UI to time and pass the time value to the DLL. If I were writing the simulation software, I would just pass 0.5 to the DLL. Does anyone have any comments on how this is supposed to be handled by the EDA tool? Once we have consensus on that question, the next question will be whether we can correct/clarify this as part of the Editorial Committee, or whether a BIRD is necessary to address this question. Thanks in advance for the comments, Arpad ====================================================================== --------------------------------------------------------------------- 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 This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. --------------------------------------------------------------------- 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