[ibis-macro] Re: Comments on BIRD 145 AMI_Resolve Dependency BIRD
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
- Date: Wed, 4 Sep 2013 06:58:40 +0000
Walter,
This is supposed to be comments on BIRD 155 (not BIRD 145),
correct?
Regarding: "We have spent about 50 man hours on this, and how using (Usage
Dep) affects other BIRDS (e.g. BIRD 160 is still not resolved),"
as far as I can tell, the questions we are discussing in BIRD 155
related to BIRD 160 would still be the same regardless whether we
had "Usage Dep", or "Dependency_Usage Out". So I don't see how we
would have saved that many man hours by calling it a different name.
Thanks,
Arpad
=====================================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Walter Katz
Sent: Saturday, August 31, 2013 8:58 AM
To: IBIS-ATM
Subject: [ibis-macro] Comments on BIRD 145 AMI_Resolve Dependency BIRD
All,
Comments on BIRD 145 AMI_Resolve Dependency BIRD
On June 25, I sent out the following to this reflector:
I strongly suggest that we have a new parameter leaf "Dependency_Usage" that
determines what the inputs and outputs of the AMI_Resolve function. The
following describes the "Dependency_Usage" leaf.
1. A new optional leaf for all parameters "Dependency_Usage", which can
have the values "In" or "Out". If "In" then the parameter is an independent
parameter. If "Out" then the parameter is a dependent parameter.
a. Usage and Dependency_Usage are independent, except Usage Out cannot
also have Dependency_Usage.
b. Any parameter (Reserved or Model Specific) parameter can have
Dependency_Usage "In" (except if Usage Out) .
c. Any parameter (Reserved or Model Specific) parameter can have
Dependency_Usage "Out" (except if Usage Out) . In addition, the following
parameters cannot have Dependency_Usage "Out".
i.
The following Reserved Parameters
1. DLL configuration Info parameters
a. GetWave_Exists
b. Init_Returns_Impulse
c. Max_number_of_agressors
d. AMI_Version
e. Supporting_Files
f. ResolveDependentParam_Exists
2. Parameters filled in by EDA tool
a. DLL_Path
b. DLL_id
June 25 Minutes
- Walter: The model user first has to make various parameter value selections.
- Input to Resolve function is "Info".
- Output of Resolve is classic "Info" parameters.
- We need to know which are "Dep-In" and which are "Dep-Out". Which are
which?
- Overloading Usage with "Dep" is a confusing way to handle it.
July 2 Minutes
- Walter: I propose a Dependency_Usage leaf with values In or Out.
- Walter: In BIRD 160 we have a parameter passed in, nothing says it can't be
Usage Out.
- All an EDA tool can do with Model_Specific Out parameters is report their
values.
The ATM group decided to go with (Usage Dep) instead of (Dependency In|Out). My
statement on June 25 "Overloading Usage with "Dep" is a confusing way to handle
it." Has been born out based on extensive discussions in the last 9 IBIS - ATM
meetings. We have spent about 50 man hours on this, and how using (Usage Dep)
affects other BIRDS (e.g. BIRD 160 is still not resolved),
On June 25 I said that (Usage Dep) was a mistake, I repeat that statement now.
If (Usage Dep) remains in the BIRD I will still support BIRD 155 in the Open
Forum, but will record my objections at that time.
Walter
Walter Katz
wkatz@xxxxxxxxxx<mailto:wkatz@xxxxxxxxxx>
Phone 303.449-2308
Mobile 303.335-6156
Other related posts:
