[ibis-macro] Re: AMI Parameter String question
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Wed, 9 Dec 2009 15:33:34 -0800
Thanks Mike for both of your emails.
As far as I can tell, the current specification does not
have such a detailed description for how to generate the
parameter string. I would highly recommend that Walter's
BIRD draft should include what you wrote here.
Thanks,
Arpad
==========================================================
-----Original Message-----
From: Mike Steinberger [mailto:msteinb@xxxxxxxxxx]
Sent: Wednesday, December 09, 2009 3:34 PM
To: Muranyi, Arpad
Cc: IBIS-ATM
Subject: Re: [ibis-macro] AMI Parameter String question
Arpad-
I agree with Ambrish's answer.
Perhaps we should re-read the IBIS spec to make sure it states these
points clearly, but here's how it goes:
1. The name of the root of the parameter tree is the name of the root of
the parameter tree which is to be passed into the model.
2. The .ami declares two classes of parameters: parameters intended for
use by the EDA platform and parameters for use by the model. The
parameters for the EDA platform go in the Reserved_Parameters branch of
the .ami file and the parameters for the model go in the Model_Specific
branch.
3. There is a BRANCH in the .ami file for every PARAMETER in the
parameter string sent to the model. The EDA platform has to have some
mechanism for producing or obtaining a parameter VALUE for each
parameter in the parameter string sent to the model. Each such parameter
value must be consistent with the information in the corresponding
branch in the .ami file.
4. It should not be necessary for every parameter declared in the .ami
file to appear in the parameter string for the model. Rather, the model
should have built in default values that will use when a parameter is
missing in the parameter string.
5. The model should silently ignore any parameter or branch it doesn't
recognize. As extra-good software craftsmanship, it would be nice if the
model echoed back through the msg interface the number of parameters it
did recognize.
Almost all of these points are reflected in Ambrish's example.
Hope this helps.
Mike S.
Muranyi, Arpad wrote:
> Hello everyone,
>
> At the expense of sounding like a broken record, I would
> like to ask the question (again) about how the EDA tool
> supposed to formulate the parameter string that is passed
> into the AMI DLL from the .ami file that is provided by
> the model maker with the DLL. Let's take the example from
> the IBIS 5.0 spec:
>
>
|=======================================================================
> ======
> | Example of Parameter File
>
|=======================================================================
> ======
> (mySampleAMI | Name given to the Parameter
> file
> (Description "Sample AMI File")
> (Reserved_Parameters | Required heading
>
> (Ignore_Bits (Usage Info) (Type Integer) (Default 21)
> (Description "Ignore 21 Bits"))
> (Max_Init_Aggressors (Usage Info) (Type Integer)(Default 25))
> (Init_Returns_Impulse (Usage Info) (Type Boolean)(Default True))
> (GetWave_Exists (Usage Info) (Type Boolean) (Default True))
> ) | End Reserved_Parameters
>
> (Model_Specific | Required heading
> (txtaps
> (-2 (Usage Inout)(Type Tap) (Format Range 0.1 -0.1 0.2)(Default
> 0.1)
> (Description "Second Precursor Tap"))
> (-1 (Usage Inout)(Type Tap) (Format Range 0.2 -0.4 0.4)(Default
> 0.2)
> (Description "First Precursor Tap"))
> (0 (Usage Inout)(Type Tap) (Format Range 1 -1 2)(Default 1)
> (Description "Main Tap"))
> (1 (Usage Inout)(Type Tap) (Format Range 0.2 -0.4 0.4)(Default2
> 0.2)
> (Description "First Post cursor Tap"))
> (2 (Usage Inout)(Type Tap) (Format Range 0.1 -0.1 0.2)(Default
> 0.1)
> (Description "Second Post cursor Tap"))
> ) | End txtaps
> (tx_freq_offset (Format Range 1 0 150) (Type UI) (Default 0))
> ) | End Model_Specific
> ) | End SampleAMI
> |
>
|=======================================================================
> ======
>
> If, for example, I want to formulate a simple parameter string for a
DLL
> that uses nothing else but the tap coefficient parameters, what would
> that
> parameter sting look like (taking the defaults from above)?
>
> (mySampleAMI
> (Description "Sample AMI File")
> (Model_Specific
> (txtaps
> (-2 0.1)
> (-1 0.2)
> (0 1)
> (1 0.2)
> (2 0.1)
> )
> )
> )
>
>
> or would it be ONLY:
>
> (txtaps
> (-2 0.1)
> (-1 0.2)
> (0 1)
> (1 0.2)
> (2 0.1)
> )
>
>
> Or anything else?
>
> 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
>
>
---------------------------------------------------------------------
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:
