[ibis-macro] Revised SiSoft priorities of resolving AMI issues, and BIRD to address the issues raised by the IBIS 5.0 Parser developer

  • From: "Walter Katz" <wkatz@xxxxxxxxxx>
  • To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
  • Date: Mon, 31 Aug 2009 13:57:11 -0400

All,

Based on the discussions in the recent Open Forum, and recent ATM meetings I
would like to modify the priorities for my discussions on resolving AMI
issues as follows.

1.      BIRD to clarify use of Format and Default for the IBIS 5.0 Parser
2.      Discussion on an additional, optional Init output
3.      BIRD to clarify flows that support Non-LTI Tx GetWave
4.      Apply exiting keyword ?Labels? to parameters with Format List.
5.      New Keyword Vector
6.      Make Format optional
7.      Make Type optional for certain reserved keywords
8.      Make Usage optional for certain reserved keywords
9.      Make Reserved_Parameters and Model_Specific Branches optional
10.     Add AMI Version to .ami files.

Specifically, the BIRD to clarify use of Format and Default is clearly of
the highest priority. I think the following interpretation should be
satisfactory for all concerned, and resolves all ambiguities in IBIS 5.0,
and should allow the parser developer to complete his task with no
ambiguity. In addition, since nothing in the above list of potential
improvements to the BIRD will deprecate anything, it will support the
fundamental IBIS premise that no model will become obsolete, and that to be
compliant, an AMI simulator should support all versions of AMI models, and
just increasing the rev of an AMI model will still make it a valid.

And change the following line on page 140
|   Format: (default is range)
to
|   Format:

Add at the bottom of page 141 a third note in Section 6c, DEFINITIONS:

3. The Format and Default keywords are two ways of specifying the value, or
allowed values for a parameter. It is legal to use the Format keyword, the
Default keyword, both the Format and Default keyword, or neither of the two.
If both Format and Default are used, then the Default value must be an
allowed value in the Format statement. If a parameter has Usage Info, then
it must have Format and/or Default. If a parameter Usage is In, Out or
InOut, and the parameter has neither Format nor Default, then any value
consistent with its Type is allowed as input to the DLL or as output of the
DLL. This shall apply to all Model Specific and Reserved Parameters.
Descriptions or examples in this document may show any of these four
methods, and the method used for that description or example would not
prohibit using the other three methods.


I propose we discuss this BIRD on Tuesday, with the goal of agreeing to
formally submitting this to the Open Forum at the next Open Forum meeting. I
would hope we would have sufficient support for this BIRD in the Tuesday
meeting that the IBIS Parser sub-committee would have confidence that the
full Open Forum will approve this BIRD in a timely fashion.

Please also note, that SiSoft will introduce a BIRD at some later time that
would make using the keyword Format optional, and elevating the following
Format directives to keywords: Value, Corner, Range, List, Increment, Steps,
Table, Gaussian, Dual-Dirac, and DjRj.

Walter


Walter Katz
303.449-2308
Mobile 720.333-1107
wkatz@xxxxxxxxxx
www.sisoft.com

Other related posts: