[ibis-macro] Re: New wording for what is in the parameter string
- From: Ambrish Varma <ambrishv@xxxxxxxxxxx>
- To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
- Date: Wed, 12 Jan 2011 11:13:48 -0800
Arpad,
There is nothing wrong with what you changed - just that I liked the previous
version because it gives a much clearer direction on what should be included
and how (to me, anyway) - for example - one of the things that you removed is
the clarification regarding including the string "Reserved_Parameter" and
"Model_Specific" in the string that goes in the model.
Regarding the 3rd point I added - it will go before the statement in red - so
there is no question of contradiction.
Maybe it might make sense if I put the whole thing:
|* The EDA tool must process the content of the .ami file so that
|* 1) the 'Reserved_Parameters' and 'Model_Specific' branch
|* names and their associated open and close parentheses "()"
|* are not included in the AMI_parameters_in string, and
|* 2) the AMI Parameter branches with Usage In or Usage InOut
|* are converted to leaf/value pairs for the AMI_parameters_in
|* string, possibly incorporating user selections. In this
|* conversion each AMI parameter branch name becomes a leaf
|* name in the AMI_parameters_in string and each leaf name
|* is followed by a white space, a value and a closing
|* parentheses ")".
|* 3) only parameters defined in the .ami file can be included in
the
|* AMI_parameters_in string.
|*
|* The EDA tool must include all Usage In and Usage InOut AMI
|* parameters in the AMI_parameters_in string. The AMI model will
|* ignore any parameter included in the AMI_parameters_in string
|* that is not Usage In or InOut. The AMI
|* executable must return a string in AMI_parameters_out
|* which includes all AMI parameters of Usage InOut and Usage
|* Out. The string must be in the parameter tree format using
|* branches and leaf/value pairs.
It is just a suggestion - you may ignore it completely.
Thanks,
Ambrish.
[cid:image002.gif@01CBB262.EDC79410]
Ambrish Varma | Member of Consulting Staff
P: 978.262.6431 www.cadence.com<http://www.cadence.com>
________________________________
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Muranyi, Arpad
Sent: Wednesday, January 12, 2011 1:41 PM
To: IBIS-ATM
Subject: [ibis-macro] Re: New wording for what is in the parameter string
Ambrish,
Thanks for your comment. I have a few problems with it.
The red text says that the AMI DLL will ignore anything that
is not Usage In or InOut. This statement doesn't prohibit
a Usage In or InOut parameter to be passed into the DLL by
the EDA tool which is not in the .ami file. It only says
that a Usage Out in the "in" string will be ignored by the DLL.
The sentence you say on the bottom of your email to add a "3)"
on the other hand contradicts the above somewhat (or is at least
inconsistent) because this says that nothing else other than
what is in the .ami file can be passed to the DLL.
Separating these two thoughts into two different paragraphs is
bothering me. It gives me the impression that here you are
saying this, there you are saying that, are you sure you know
what you are trying to say? Make up your mind...
I attempted to capture the same thoughts in one sentence. (I
worked really hard to get that sentence into the form it is).
You didn't say what you didn't like about it. At this point
I still refer my proposed sentence(s), but I am open for
suggestions if something is wrong with them.
Thanks,
Arpad
=================================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Ambrish Varma
Sent: Wednesday, January 12, 2011 11:26 AM
To: IBIS-ATM
Subject: [ibis-macro] Re: New wording for what is in the parameter string
Arpad,
I actually like it the way it was. It gives a much clearer direction on what
should be included and how.
My suggestion is to change the second para (in the original text) to something
like this (changes in red):
|* The EDA tool must include all Usage In and Usage InOut AMI
|* parameters in the AMI_parameters_in string. The AMI model will ignore any |*
parameter included in the AMI_parameters_in string that is not Usage In |* or
InOut. The AMI executable must return a string in AMI_parameters_out |* which
includes all AMI parameters of Usage InOut and Usage Out. The |* string
must be in the parameter tree format using branches and leaf/value |* pairs.
Also, we should add a 3rd point to para 1 with something like this:
3) only parameters defined in the .ami file can be included in the
AMI_parameters_in string.
Thanks,
Ambrish.
Ambrish Varma | Member of Consulting Staff
P: 978.262.6431 www.cadence.com<http://www.cadence.com>
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Muranyi, Arpad
Sent: Wednesday, January 12, 2011 1:43 AM
To: IBIS-ATM
Subject: [ibis-macro] New wording for what is in the parameter string
Hello,
According to our discussions in the ATM teleconference,
I rewrote the paragraph about what should be included
in the AMI parameter string and what shouldn't. Here
is that section of the BIRD draft:
|* The EDA tool must process the content of the .ami file
so that
|* 1) the 'Reserved_Parameters' and 'Model_Specific'
branch
|* names and their associated open and close
parentheses "()"
|* are not included in the AMI_parameters_in string,
and
|* 2) the AMI Parameter branches with Usage In or Usage
InOut
|* are converted to leaf/value pairs for the
AMI_parameters_in
|* string, possibly incorporating user selections. In
this
|* conversion each AMI parameter branch name becomes a
leaf
|* name in the AMI_parameters_in string and each leaf
name
|* is followed by a white space, a value and a closing
|* parentheses ")".
|*
************************************************************************
********
|* The EDA tool must include all Usage In and Usage InOut
AMI
|* parameters in the AMI_parameters_in string and the AMI
|* executable must return a string in AMI_parameters_out
|* which includes all AMI parameters of Usage InOut and
Usage
|* Out. The string must be in the parameter tree format
using
|* branches and leaf/value pairs.
************************************************************************
********
|* The following two paragraphs are to replace the previous one:
************************************************************************
********
|* The EDA tool must pass a string to the AMI executable
model
|* through the AMI_parameters_in argument which contains
all of
|* the leaf/value pair formatted Usage In and Usage InOut
AMI
|* parameters defined in the .ami file and nothing else.
|*
|* The AMI executable model must return a string to the EDA
tool
|* through the AMI_parameters_out argument which contains
all of
|* the leaf/value pair formatted Usage InOut and Usage Out
AMI
|* parameters defined in the .ami file and nothing else.
************************************************************************
********
|*
|* For Usage In, the value in the "AMI Parameter" leaves
are
|* determined by the EDA tool based on the "AMI Parameter"
|* branches in the .ami file. For Usage Out, the value in
the
|* "AMI Parameter" leaves are determined by the Algorithmic
|* Model. For Usage InOut, the value in the "AMI
Parameter"
|* leaves are first determined by the EDA tool based on the
|* "AMI Parameter" branches in the .ami file and passed
into
|* the Algorithmic Model which may return a new value in
the
|* "AMI Parameter" leaves after some processing.
|*
Please let me know whether this wording captures the thoughts
we discussed in the meeting, and make suggestions if not.
Thanks,
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
Other related posts:
