I think my original question is more true to my intended inquiry, than either alternative you propose. And, understand that the case I'm envisioning is one in which the user doesn't want EDA tool driven co-optimization to occur. (Otherwise, he'd do that.) In such an instance, and if the user has opted to NOT use the Tx model 'co-opt' mode, but rather to use some 'auto' feature of the Tx model, in which that model chooses the optimum FIR coefficients based solely upon the channel impulse response and not expecting to take part in any Tx/Rx co-optimization, why must the Tx AMI_Init() function alert the EDA tool that it has done so? (Mike M., that is what you were suggesting; right?) Thanks, -db From: Walter Katz [mailto:wkatz@xxxxxxxxxx] Sent: Tuesday, April 15, 2014 1:29 PM To: David Banas; ibis-macro@xxxxxxxxxxxxx Subject: RE: [ibis-macro] Unanswered question from last week. David, Your statement is not quite correct. I think the statement should be: Why must the Tx .ami file tell the EDA tool, if it assisted the user in choosing "optimum" tap weights? or Why must the Tx .ami file tell allow the EDA tool to tell the Tx AMI_Init() to assist the user in choosing "optimum" tap weights? The reason for letting the EDA tool know what the Tx AMI_Init() function is doing (or controlling what the Tx AMI_Init() function is doing is important in co-optimization, particularly in the statistical flow. The Rx AMI_Init needs to know the Tx equalization used to generate the input to the Rx AMI_Init, and when the Rx AMI_Init returns an optimized Tx tap coefficients, the Tx AMI_Init function needs to be called with these coefficients, and the Tx AMI_Init must use the equalization for these tap coefficients. Does this answer your question? Walter From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx> [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of David Banas Sent: Tuesday, April 15, 2014 2:30 PM To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx> Subject: [ibis-macro] Unanswered question from last week. Hi all, I asked a question, at the end of Walter's presentation last week, which I don't think was ever answered. So, I'd like to ask it, again: Why must the Tx AMI_Init() function tell the EDA tool, if it assisted the user in choosing "optimum" tap weights? (How, for instance, is this use case different than the user relying on, say, MATLAB to help him find optimum tap weights and setting those MATLAB-prescribed values in the AMI model, by hand?) Thanks, -db ________________________________ Confidentiality Notice. This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you. ________________________________ Confidentiality Notice. This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.