[ibis-macro] FW: Re: IBIS AMI Specification Questions/Proposal
- From: "Ambrish Varma" <ambrishv@xxxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 25 Aug 2009 11:02:01 -0400
Seems like there was a copy paste error in the example.
The correct example is as follows:
(Model_Specific
(txtaps
(-2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.1
0.2)(Default 0.1)
(Description "Second Precursor Tap"))
(-1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.4
0.4)(Default 0.1)
(Description "First Precursor Tap"))
(0 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -1
2)(Default 0.1)
(Description "Main Tap"))
(1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.4
0.4)(Default 0.1)
(Description "First Post cursor Tap"))
(2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.1
0.2)(Default 0.1)
(Description "Second Post cursor Tap"))
)
(tx_freq_offset (Format Range) (Value 1 0 150) (Type UI) (Default
1))
)
Sorry about that.
-Ambrish.
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Ambrish Varma
Sent: Tuesday, August 25, 2009 10:44 AM
To: IBIS-ATM
Cc: Arpad_Muranyi@xxxxxxxxxx
Subject: [ibis-macro] Re: IBIS AMI Specification Questions/Proposal
Hi Arpad,
Thanks for your questions. They will help in understanding the parameter
passing mechanism to dlls for AMI.
My statement "we have used the word Default to specify the value for
that model/simulation" was directed towards the reserved parameters.
Default is not explicitly needed for Required parameters in the AMI
file. Those parameters that are not required, (refer to table 1) the EDA
tool will use the default to begin with. If the user wants to use a
value other than default, then they put it in the .ami file.
Observe the difference between
(Ignore_Bits (Usage Info) (Type Integer) (Default 21) (Description
"Ignore 21 Bits"))
And
(Ignore_Bits (Usage Info) (Type Integer) (Value 21) (Description "Ignore
21 Bits"))
Keep in mind that the spec says the default value of Ignore_Bits is 0
(table 1) and it is an optional reserved parameter.
To your question, specifically, we need to clarify in the spec that typ
= default for range.
Re: 2) looking at an example (the one I sent yesterday):
(Model_Specific
(txtaps
(-2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 -0.1
0.2)(Default 0.1)
(Description "Second Precursor Tap"))
(-1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.2 -0.4
0.4)(Default 0.1)
(Description "First Precursor Tap"))
(0 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 1 -1
2)(Default 0.1)
(Description "Main Tap"))
(1 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.2 -0.4
0.4)(Default2 0.1)
(Description "First Post cursor Tap"))
(2 (Usage Inout)(Type Tap) (Format Range) (Value 0.1 0.1 -0.1
0.2)(Default 0.1)
(Description "Second Post cursor Tap"))
)
(tx_freq_offset (Format Range) (Value 1 0 150) (Type UI) (Default
1))
)
In this section of the AMI file, the model maker sets the default (and
the user can safely assume that the model will perform at its best using
these default values - and choose not to do anything further).
As such, an example of the string that will get passed to the model CAN
be:
(Model_Specific
(txtaps
(-2 0.1)
(-1 0.1)
(0 0.1)
(1 0.1)
(2 0.1)
)
(tx_freq_offset 1)
)
The user might also want to change the tap values (as long as they are
in the range set by the model maker to
(Model_Specific
(txtaps
(-2 -0.1)
(-1 0.4)
(0 2)
(1 0.4)
(2 0.2)
)
(tx_freq_offset 10)
)
And so on ..
So maybe a clear directive is missing in the spec, but this was the
original intent.
Hope I have not added to the confusion.
Thanks,
Ambrish.
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, August 25, 2009 12:17 AM
To: IBIS-ATM
Subject: [ibis-macro] Re: IBIS AMI Specification Questions/Proposal
Ambrish,
Thanks for pointing this problem out. I am sure we will address
these issues as our discussions on AMI improvements continue.
I would like to ask you a couple of questions about the usage of
"default".
1) Considering your statement that "we have used the word Default
to specify the value for that model/simulation", what would you say
is the difference between the typical value of a range and the default?
2) Your statement "we have used the word Default to specify the
value for that model/simulation" opens up the question I asked a
several weeks ago about parameter strings. Remember, my impression
about the specification was that the entire .ami file was supposed
to be passed into the DLL's parameter string and consequently
the DLL was supposed to parse it and extract the values from it.
Your statement that "we have used the word Default to specify the
value for that model/simulation" seems to underline that thinking,
because it seems that you are saying that the DLL will extract the
default value and simulate using that. In this case, the EDA tool
could modify the original .ami file's default values before passing
it to the DLL according to the user's wishes for each specific
simulation.
On the other hand, if this was not the intent, in other words, if
the DLL is supposed to get only a subset of the .ami file in the
parameter string, I am still looking for a description in the AMI
specification that explains how to formulate that subset.
Thanks,
Arpad
======================================================================
-----Original Message-----
From: Ambrish Varma [mailto:ambrishv@xxxxxxxxxxx]
Sent: Monday, August 24, 2009 3:03 PM
To: IBIS-ATM
Cc: Muranyi, Arpad
Subject: RE: [ibis-macro] Re: IBIS AMI Specification Questions/Proposal
Hi All,
I feel there is some real confusion about "Values" and "Default".
Defaults, generally mean that if there is no value provided, the tool
will use the default value. In the spec, we have used the word Default
to specify the value for that model/simulation (particularly in the
reserved parameters section).
There is also confusion because we have defined the format for declaring
the parameters at 2 places for the reserved parameters (one with format,
one without).
Please refer to the attached document to see the changes that I am
proposing to the parameter section.
Thanks,
-Ambrish.
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, August 18, 2009 6:51 PM
To: IBIS-ATM
Subject: [ibis-macro] Re: IBIS AMI Specification Questions/Proposal
Bob,
Thanks for posting this summary of the problem.
I read trough the attached file and I am not sure what
the reasons are for these inconsistencies. In order to
make the right decisions, I feel we need to ask those
who wrote these portions of the AMI spec to find out
what was their intent. Authors, please speak up...
Thanks,
Arpad
========================================================
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Tuesday, August 18, 2009 5:11 PM
To: IBIS-ATM
Subject: [ibis-macro] IBIS AMI Specification Questions/Proposal
All:
This is being sent out per the issue raised at the Aug. 18
meeting concerning parser interpretation of the AMI Spec.
The ibischk5 parser with the -ami flag will check the
syntax of the <file name>.ami file. The attached document
shows several forms for <parameter_name> that are in the
specification. Some of the forms imply a restricted set of
parameters, but then this is contradicted by the example
at the end.
This implies that some parameters are really optional and
not excluded according to the syntaxes given.
The propposal is simply to make all parameters at least
optional, and some required according to a draft Table 4
that is NOT in the specification.
Do the choices in Table 4 look reasonable?
Bob
--
Bob Ross
Teraspeed Consulting Group LLC Teraspeed Labs
121 North River Drive 13610 SW Harness Lane
Narragansett, RI 02882 Beaverton, OR 97008
401-284-1827 503-430-1065
http://www.teraspeed.com 503-246-8048 Direct
bob@xxxxxxxxxxxxx
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
---------------------------------------------------------------------
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
Other related posts:
- » [ibis-macro] FW: Re: IBIS AMI Specification Questions/Proposal - Ambrish Varma
