Arpad: I think you captured all of the details, and this is ready for posting. However, there are some other issues. BIRD153 regarding parameters is also implicitly part of this BIRD and relates to the keyword [Converter Parameters] We need to make a reference to parameters defined under that keyword, where ever it is defined. Also the statement Any or all of these entries may be defined by parameter names, which must be declared and initialized by one or more Converter_Parameters subparameter needs work and clarification. I do not think the port1 and port2 names or corner can be parameterized. for A_to_D, the rule explicitly applies only to vlow, vhigh, trise, tfall. For D_to_A, only vlow and vhigh can be parameterized. They do not have to be parameterized. This can be discussed next time. The examples for polarity show different trise and for the Inverting, but that is ok. Also, all " i.e." should be followed by a comma: "i.e.," This is for document consistency and also the most common way it is done in most articles and papers. (In some cases, it is better to break it up into two sentences.) I may catch more later. Bob -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Tuesday, April 09, 2013 10:50 AM To: bob@xxxxxxxxxxxxx; 'IBIS-ATM' Subject: [ibis-macro] Re: BIRD160 - parameters comments Bob, Thanks for your comments. Good catch about adding the [Converter Parameters] to the table and keyword tree. Regarding your questions on the parameters, here are my quick reactions. We can have more discussion on it as necessary. The Booleans might be needed for *-AMS models which can have such parameter types, so I would think that we should support them too. Starting each parameter assignment on a new line is fine with me, I just thought that we could make things a little more efficient this way, but I am fine with new lines too. Regarding default, you are correct that the called IBIS-ISS or *-AMS files might have their own defaults, but this is not guaranteed. But I think you are incorrect about saying that "all of the tree definitions have default values". The Default in the tree definitions are really a default for the selection from a multi valued parameter (list, range, etc...) so that there will be a value even if the user doesn't make a selection. But this mechanism doesn't guarantee that the IBIS-ISS parameter will always have a value, even if the parameter or tree from which the value supposed to come from is not found. I don't mind leaving out the default value from this parameter assignment syntax, but I want to make sure we all know what this would have done for us, and what we will be missing if we don't have it... Thanks, Arpad =================================================================== -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross Sent: Tuesday, April 09, 2013 12:04 PM To: 'IBIS-ATM' Subject: [ibis-macro] BIRD160 - parameters comments All: Attached is a document for reference with some questions at the end - aiming for simplification of the syntax. Also the [Converter Parameters] are added in the tree diagram in Section 6B. Bob -- Bob Ross Teraspeed Consulting Group, LCC http://www.teraspeed.com bob@xxxxxxxxxxxxxx Direct : 503-246-8048 Teraspeed Labs: 971-279-5325 Headquarters: 401-284-1827 Teraspeed is a registered service mark of Teraspeed Consulting Group LLC --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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