All, If we allow the Jitter parameters to be Usage Info or Out, then then we can add the following note: Note: The EDA Tool/Simulator shall use the values of these Jitter and Noise parameters directly if they are Usage Info. If they are Usage Out, then the EDA Tool/Simulator shall use their values generated by AMI_Init. The model's AMI_GetWave function may return different values for these parameters than the values returned by AMI_Init; the EDA Tool/Simulator may report the values of such parameters to the user, but the EDA Tool/Simulator may not change any inputs to AMI models or change other result of the simulation based on the values returned for the parameters in this BIRD by AMI_GetWave. If we approve BIRD 155 (AMI_Resolve DLL entry), then we would allow these parameters to be Info, Dep, or Out. Walter -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Monday, July 08, 2013 12:56 PM To: 'IBIS-ATM' Subject: [ibis-macro] Re: Usage type of jitter parameters in ibis5.1 Bob, We can certainly discuss this tomorrow if needed. But, as far as I remember, the problem with Usage Out parameters is that both the AMI_Init and the AMI_GetWave functions have an argument "AMI_parameters_out" and the spec doesn't go into the details on which function of the model would/should return the Usage Out value(s). In the case of the jitter parameters, most (if not all) of them would inform the EDA tool on how to jitter the signal. But if the spec doesn't describe the rules for the model on when it should return these parameters to the EDA tool, or for the EDA tool on when to look for these parameters when executing the model, we can have serious problems. I am not saying that there are no situations when Usage Out jitter parameters might be needed or useful, or that these rules can't be defined in the specification, but as far as I remember, we didn't want to deal with all this at the time when the question was raised about Usage Out in the jitter parameters, so the easiest solution at the time was to remove Usage Out for the jitter parameters. Considering that defining such rules would require considerable amount of writing and discussion, I doubt that we can just take care of this as an editorial change and put back Usage Out for the jitter parameters. If we did that, we would open the door for all kinds of incompatibilities and ambiguities which is not desirable. As usual, comments welcome... Thanks, Arpad ======================================================================= -----Original Message----- From: <mailto:ibis-macro-bounce@xxxxxxxxxxxxx> ibis-macro-bounce@xxxxxxxxxxxxx [ <mailto:ibis-macro-bounce@xxxxxxxxxxxxx> mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross Sent: Monday, July 08, 2013 10:57 AM To: <mailto:mike@xxxxxxxxxxx> mike@xxxxxxxxxxx; <mailto:fangyi_rao@xxxxxxxxxxx> fangyi_rao@xxxxxxxxxxx Cc: 'Walter Katz'; 'IBIS-ATM' Subject: [ibis-macro] Re: Usage type of jitter parameters in ibis5.1 All: Is this worth bringing up at the next ATM meeting? If there is need to revert back to including Usage Out for Tx_Jitter and Tx_DCD in Version 6.0 we could do it with a quick correction BIRD. Usage Out is currently supported in Version 5.1, so there is no known damage. We could consider other Jitter and Noise Parameters at that time. We are editing this area, so we want to get this right for the next release. Bob --------------------------------------------------------------------- IBIS Macro website : <http://www.eda.org/pub/ibis/macromodel_wip/> http://www.eda.org/pub/ibis/macromodel_wip/ IBIS Macro reflector: <//www.freelists.org/list/ibis-macro> //www.freelists.org/list/ibis-macro To unsubscribe send an email: To: <mailto:ibis-macro-request@xxxxxxxxxxxxx> ibis-macro-request@xxxxxxxxxxxxx Subject: unsubscribe