Walter, I would like to ask you to complete your last sentence so we could understand what you were trying to say. (See red comment in the sentence). Thanks, Arpad ======================================================== From: Walter Katz [mailto:wkatz@xxxxxxxxxx] Sent: Friday, December 03, 2010 11:09 AM To: Muranyi, Arpad; ibis-macro@xxxxxxxxxxxxx Subject: RE: [ibis-macro] Re: About the Typos BIRD comments from Fangyi Arpad, Actually the current released 5.0 BIRD is rather complete in this area. It is very short on examples, and of course Tables is lacking any coherent explanation on how data in Tables can get passed in or out of the DLL. I would support WHAT? if any other members of the committee feel that the specification needs additional explanation required in addition to a good set of examples. Walter From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Friday, December 03, 2010 11:32 AM To: ibis-macro@xxxxxxxxxxxxx Subject: [ibis-macro] Re: About the Typos BIRD comments from Fangyi Hello AMI Experts, This thread stopped a day or so ago without reaching a conclusion. I am going to summarize the questions I would like to get answered. 1) When does a branch become an "AMI parameter"? Does this have to be spelled out in the IBIS-ATM specification, or does this belong to a Cookbook or HOWTO document? Currently this is what I have in the Typos BIRD draft: |* A branch in the .ami file is an "AMI Parameter" if it |* contains the leaves Type, Usage, and any of the following |* leaves: |* |* Default |* <data_format> or Format <data_format> |* |* and does not contain another branch. A branch which |* contains one or more sub-branches may only contain the |* Description <string> leaf/value pair in addition to the |* sub-branches. 2) What is supposed to be passed into the AMI executable model in the parameter string, and what is supposed to be omitted from this string? Does this have to be spelled out in the IBIS-ATM specification, or does this belong to a Cookbook or HOWTO document? Currently this is what I have in the Typos BIRD draft: ************************************************************************ ******** REMOVE THIS PARAGRAPH if the next few are agreed on:**************************** |* The tree data structure passed in and out of the DLL |* described in section 3.1.2.6 of Section 10 of this document |* is similar to the tree data structure in the .ami file except |* the 'Reserved_Parameters' and 'Model_Specific' branch names are |* not included, the "AMI Parameter" branches become leaves and |* the "AMI parameters" of Usage Info and Out are not included. END OF REMOVED PARAGRAPH******************************************************** ************************************************************************ ******** |* |* The parameter string passed in and out of the DLL (described in |* section 3.1.2.6 of Section 10 of this document) is formatted |* the same way as the tree data structure in the .ami file with |* the following exceptions: |* |* 1) The "Reserved_Parameters" and "Model_Specific" branch |* names are not included |* 2) None of the Description leaf/value pairs are included |* 3) AMI Parameter branches or sub branches with Usage Info |* or Usage Out are omitted, but all other branches or sub |* branches are included |* 4) AMI Parameter branches with Usage In or Usage InOut |* become leaves |* 3) Define how/where the DLL returns Out or InOut parameters and how/where the EDA tool is supposed to look for these values. Does this have to be spelled out in the IBIS-ATM specification, or does this belong to a Cookbook or HOWTO document? There is nothing on this topic in the Typos BIRD draft, nor can I find anything about this in the current IBIS specification. Thanks, Arpad ======================================================================== ======