[ibis-editorial] Re: IBIS Editorial Task Group Dec. 21 Minutes and Jan. 10 Agenda

  • From: "Bob Ross" <bob@xxxxxxxxxxxxx>
  • To: <ibis-editorial@xxxxxxxxxxxxx>
  • Date: Wed, 11 Jan 2012 12:06:22 -0800

Walter:

Per our discussion on 2, this seems reasonable
as long as we communicate with and get clear  buy in
from all parties (and particularly each of the 7 EDA
vendors who have implemented some or part of IBIS-AMI V5.0)
what we plan to do and why.  Some discussion should occur
privately since vendor-specific plans and concerns are legally
of bounds for public IBIS discussions.

a) However, everything in .ami that is supported must
be documented - even if deprecated.  So the Use_Init_Output
must be documented as a legal reserved parameter
and mentioned that it is  no longer legal in 5.1 and beyond
because of flow changes.  AMI-Version is not required for
V5.0 models, and this must be documented.

b) The string exception  should not exist.  The
conflicting documentation on this was resolved, and the
official interpretation is that quotes are required.
The parser should check for compliance, and all non-compliant
models should  be fixed.

c) The V5.1 parser can print an appropriate Warning message for
AMI-Ver 5.0 models.  The Spec must also have verbage clearly
describing that the .ami V5.1 syntax rules (some relaxed
and new restrictions) now apply to V5.0 .ami files.  Also it
should be noted that some original flow assumptions and
executable model rules have changed and are no longer
part of any official flow supported by IBIS-AMI.  We do not
need to document the old flow.

Bob

-----Original Message-----
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz
Sent: Wednesday, January 11, 2012 6:20 AM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: IBIS Editorial Task Group Dec. 21 Minutes and
Jan. 10 Agenda

All,

I would like to add two items to the agenda:

1. IBIS 5.1 will have a format for describing Reserved Parameters (I do
not know what the status of this is yet). BIRD 123.2 obviously does not
follow this new format. I hope 123.2 get approved by the OPEN Forum before
5.1 is finished. Will BIRD 123,2 need to be amended to comply with the new
format, or will this be a task for the editorial committee when IBIS 5.2
gets written.

2. At some point I would like to discuss the IBIS 5.1 AMI parser. I
propose that the IBIS 5.1 AMI parser just follow the 5.1 rules. I believe
that IBIS 5.0 AMI models should pass the IBIS 5.1 rules with the following
exceptions:
        a. Reserved parameters Version and Use_Init_Output
        b. Quotes around strings
        c. IBIS 5.0 models that do not follow the New Rules, should have,
and I think that they should be flagged.

Walter

-----Original Message-----
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Tuesday, January 10, 2012 11:55 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] IBIS Editorial Task Group Dec. 21 Minutes and
Jan. 10 Agenda

======================================================================
IBIS EDITORIAL TASK GROUP MEETING MINUTES AND AGENDA

http://www.eda.org/ibis/editorial_wip/   

Mailing list: ibis-editorial@xxxxxxxxxxxxx 
Archives at //www.freelists.org/archive/ibis-editorial/   

======================================================================
Next Meeting
Wednesday, January 11, 2012
9 AM US Pacific Time 

               Telephone     Bridge   Passcode
              916-356-2663     92     748-2862

(for international and alternate US numbers, contact Michael Mirmak)

Join online meeting
https://meet.intel.com/michael.mirmak/B79DHKGF 


Agenda:
- Attendees
- Call for patents
- Review of Minutes
  * December 21, 2011
- Opens
- Timeline for IBIS 5.1 document revisions/review of new document
- Agenda for Next Meeting
- Approve Next Meeting Dates:
  * January 17
  * January 24
======================================================================

Attendees:
----------
(* denotes present)
Agilent                    - Radek Biernacki
Ansoft                     - Denis Soldo
Cadence Design Systems     - Terry Jernberg, Brad Griffin, Dennis Nagle
I/O Methodology            - Lance Wang
Intel                      - Michael Mirmak*
Mentor Graphics Corp.      - John Angulo, Arpad Muranyi*
Micron Technology          - Justin Butterfield, Randy Wolff
SiSoft                     - Walter Katz
Teraspeed Consulting Group - Bob Ross*
========================================================================

No patents were declared.

Michael Mirmak reviewed the status of approved and pending IBIS 5.1 BIRDs 
and a combination ASCII draft of IBIS 5.1.  Three BIRDs are pending for
5.1;

no others are expected.

Arpad Muranyi suggested that everything between "Table" and the following 
text should be indented:

|   Gaussian <mean> <sigma>
|   Dual-Dirac <mean> <mean> <sigma> 
|    Composite of two Gaussian
|   DjRj <minDj> <maxDj> <sigma>
|      Convolve Gaussian (sigma) with uniform Modulation PDF

Gaussian, Dual-Dirac, DjRj should all be at the same level as Table
(they're

all formats).

Bob Ross suggested that all changes should be presented in "standard" IBIS

(ASCII) format first and collected in one document before formatting
changes

are made.

Bob also asked whether terms such as "tree", "root", "subtree", "branch", 
and "leaf" are defined.  Michael will check on these, plus whether
consistent 
terms are used between Section 6x and Section 10.






Other related posts: