[ibis-macro] Re: IBIS-ATM teleconference - Agenda for 3/22/2011
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 22 Mar 2011 09:18:21 -0700
Forgot to mention that Bob has a few questions about
AMI related bugs discovered in the IBIS parser which
we need to discuss. We will spend a few minutes on
that today (see attachments).
Thanks,
Arpad
====================================================
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Tuesday, March 22, 2011 10:53 AM
To: IBIS-ATM
Subject: [ibis-macro] IBIS-ATM teleconference - Agenda for 3/22/2011
Time: March 22, 2011 Noon US Pacific Time
=====
Audio:
======
Voice dial-in: (800) 637-5822
International: +1 (647) 723-3937 <--- (For Canada)
0114501530 <--- (For Sweden)
0201400572 <--- (For Sweden Toll Free)
069509594672 <--- (For Germany)
08001014542 <--- (For Germany Toll free)
Access Code: 685-0440
Web
===
Click Here to Join Live Meeting:
http://tinyurl.com/yvmesj
or:
https://www.livemeeting.com/cc/sisoft/join?id=NKQQN3&role=attend&pw=TP8j
%23-%25%7E5
Mentor Global Crossing Teleconference commands:
http://www.globalcrossing.com/customer/collaboration/cust_ready_access_t
ips.aspx
FIRST TIME USERS: To save time before the meeting, check your
system to make sure it is compatible with Microsoft Office Live
Meeting.
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Call for any related patent disclosures
3) Review of ARs:
Radek: Start an email thread with comments on cross talk BIRD draft
- not done
Arpad: Update BIRD 120 with the additional sentence on the
GetWave block size
- done (http://www.eda.org/pub/ibis/birds/bird120.1.txt)
Ambrish: Start a BIRD draft for the Table syntax
- done
Bob: Check BIRD 127 for type clarification possibilities
- done
Ken: Draft language to clarify handling of multiple channels
(cross talk BIRD)
- done
Ambrish: Start a BIRD on row 25 in the Task List
- done
Bob: Write a BIRD on correcting Table 1-3 in the spec.
(Row 23 in the Task List).
- in progress
Any other AR-s?
Old ARs:
Arpad: Review the documentation (annotation) in the macro libraries.
- deferred until a demand arises or we have nothing else to do
4) Cross talk BIRD draft
- need a list of issues so we can update the BIRD draft
and get it ready for voting
5) (Format) Table (including Row 21, 22)
- discuss BIRD draft from Ambrish (attached)
6) Define relationship between Type and Format (Row 25)
- discuss BIRD draft from Ambrish (attached)
7) Model_Specific parameters Usage Out/InOut
- Since we do not know the meaning of these, what is
the EDA tool expected to do with them?
- Type Tap has a unique meaning, we could allow this,
but something should be mentioned in the spec on what
the tool is expected to do (plot, log file, etc).
- how about the rest of the Types? Does it make sense
to allow them?
8a) BIRD 123, jitter parameters
- how do we deal with Usage Out? (includes Row 37)
- remove it from the spec?
- specify that only the Init function can return values?
8b) BIRD 121, data management parameters (file support)
- questions, comments?
8c) BIRD 124, dependency table
9) Back-channel proposals from SiSoft and Sigrity
Remaining Task List items:
==========================
Row 18: What is the ambiguity between Format and Text Strings?
- answer: See row 25
Row 21: According to the BNF, the Format = Table syntax is invalid.
- If Format is removed, this s not a problem, but if Format
is there the problem still exists. Do we need to fix this?
- we will address this when talking about Table
Row 22: The syntax for a leaf is:
(Row 22 in Task List)
<leaf>: ( <parameter name> whitespace <value list> )
So in a Table which is written like this: (-50 -0.1 1e-35),
-50 is actually a parameter name, i.e. a string, not a value.
-deprecate Table back to List?
- we will address this when talking about Table
Row 23/24: Fix the two tables to reflect what is in the text
- Bob started a BIRD draft which will be finalized
as other BIRDs are completed
Row 25: Define relationship between Type and Format
- discuss Walter's suggestions
Row 26: This is basically the same as the items in Row 46-47.
Row 33: Is AMI_Init restricted to change first column of impulse_matrix
only?
- Sigrity is writing a BIRD draft on this (Ken)
Row 35: Clarify questions about impulse response
- this needs to be discussed
Row 37: Usage Out for reserved (jitter) parameters
- which function (Init or GetWave) can return these?
Row 46/47: Remove certain parameters and keywords
- this needs to be discussed
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
******************************************************************************
********************* IBIS GOLDEN PARSER BUG REPORT FORM *********************
******************************************************************************
INSTRUCTIONS
To report a bug in the IBIS golden parser. Please fill out the top part
of the following form and send the complete form to ibis-bug@xxxxxxxx
A list of reported bugs will be maintained on eda.org.
******************************************************************************
PARSER VERSION NUMBER: 5.0.4
PLATFORM (SPARC, HP700, PC, etc.): PC
OS AND VERSION: Windows 7
REPORTED BY: Bob Ross, Teraspeed Consulting Group
DATE: March 13, 2011
DESCRIPTION OF BUG:
The order dependence rule that the Reserved_Parameters section appear before
the optional Model_Specific section is not enforced:
| The Model Parameter File must be organized in the following
| way:
|
| (my_AMIname | Name given to the Parameter file
| (Reserved_Parameters | Required heading to start the
| | required Reserve_Parameters
| | section
| ...
| (Reserved parameter text)
| ...
| ) | End of Reserved_Parameters
| | section
| (Model_Specific | Required heading to start the
| | optional Model_Specific section
| ...
| (Model specific parameter text)
| ...
| ) | End of Model_Specific section
| (Description <string>) | description of the model
| | (optional)
| ) | End my_AMIname parameter file
The test case begins with the Model_Specific section before the
required Reserved_Parameters section. No Error or Warning is given.
INSERT IBIS FILE DEMONSTRATING THE BUG: (modified version of file from Bug 126)
(bug128
(Description "Receiver model configured for 1 tap DFE")
(Model_Specific
(taps
(1 (Usage InOut) (Format Range 0 -1.0 1.0)(Type Tap)
(Default 0) (Description "First DFE tap.")
)
)
) | End Model_Specific
(Reserved_Parameters
(Ignore_Bits (Usage Info) (Type Integer) (Default 50000)
(Description "DFE may take a 50,000 bits to converge.")
)
(Init_Returns_Impulse (Usage Info) (Type Boolean)
(Default True)
(Description "Init is provided in this model.")
)
(GetWave_Exists (Usage Info) (Type Boolean) (Default True)
(Description "GetWave is provided in the module.")
)
(Use_Init_Output (Usage Info) (Type Boolean) (Default False)
(Description "GetWave and Init function indpendent of each other.")
)
(Rx_Receiver_Sensitivity (Usage Info)(Format Range 0.25 0.0 0.5)
(Type Float)(Default 0.025)
(Description "Receiver sensitivity.")
)
) | End Reserved_Parameters
)
******************************************************************************
******************** BELOW FOR ADMINISTRATION AND TRACKING *******************
******************************************************************************
BUG NUMBER: 128
SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] (ANNOYING)
PRIORITY: [HIGH, MEDIUM, LOW] (MEDIUM)
STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] OPEN
FIXED VERSION:
FIXED DATE:
NOTES ON BUG FIX:
Classified at the IBIS teleconference meeting on XXXXXXXXX, 2011.
To be fixed in a later release.
******************************************************************************
************************************************************************************************************************************************************
********************* IBIS GOLDEN PARSER BUG REPORT FORM *********************
******************************************************************************
INSTRUCTIONS
To report a bug in the IBIS golden parser. Please fill out the top part
of the following form and send the complete form to ibis-bug@xxxxxxxx
A list of reported bugs will be maintained on eda.org.
******************************************************************************
PARSER VERSION NUMBER: 5.0.4
PLATFORM (SPARC, HP700, PC, etc.): PC
OS AND VERSION: Windows 7
REPORTED BY: Bob Ross, Teraspeed Consulting Group
DATE: March 13, 2011
DESCRIPTION OF BUG:
The occurance of one Reserved_Parameters section and one optional
Model_Specific section is not enforced:
| The Model Parameter File must be organized in the following
| way:
|
| (my_AMIname | Name given to the Parameter file
| (Reserved_Parameters | Required heading to start the
| | required Reserve_Parameters
| | section
| ...
| (Reserved parameter text)
| ...
| ) | End of Reserved_Parameters
| | section
| (Model_Specific | Required heading to start the
| | optional Model_Specific section
| ...
| (Model specific parameter text)
| ...
| ) | End of Model_Specific section
| (Description <string>) | description of the model
| | (optional)
| ) | End my_AMIname parameter file
The test case has repeated Reserved_Parameters and Model_Specific sections
and no Error or Warning is given.
INSERT IBIS FILE DEMONSTRATING THE BUG: (modified version of file from Bug 126)
(bug129
(Description "Receiver model configured for 1 tap DFE")
(Reserved_Parameters
(Ignore_Bits (Usage Info) (Type Integer) (Default 50000)
(Description "DFE may take a 50,000 bits to converge.")
)
(Init_Returns_Impulse (Usage Info) (Type Boolean)
(Default True)
(Description "Init is provided in this model.")
)
(GetWave_Exists (Usage Info) (Type Boolean) (Default True)
(Description "GetWave is provided in the module.")
)
(Use_Init_Output (Usage Info) (Type Boolean) (Default False)
(Description "GetWave and Init function indpendent of each other.")
)
(Rx_Receiver_Sensitivity (Usage Info)(Format Range 0.25 0.0 0.5)
(Type Float)(Default 0.025)
(Description "Receiver sensitivity.")
)
) | End Reserved_Parameters
(Model_Specific
(taps
(1 (Usage InOut) (Format Range 0 -1.0 1.0)(Type Tap)
(Default 0) (Description "First DFE tap.")
)
)
) | End Model_Specific
(Reserved_Parameters
(Ignore_Bits (Usage Info) (Type Integer) (Default 50000)
(Description "DFE may take a 50,000 bits to converge.")
)
(Init_Returns_Impulse (Usage Info) (Type Boolean)
(Default True)
(Description "Init is provided in this model.")
)
(GetWave_Exists (Usage Info) (Type Boolean) (Default True)
(Description "GetWave is provided in the module.")
)
(Use_Init_Output (Usage Info) (Type Boolean) (Default False)
(Description "GetWave and Init function indpendent of each other.")
)
(Rx_Receiver_Sensitivity (Usage Info)(Format Range 0.25 0.0 0.5)
(Type Float)(Default 0.025)
(Description "Receiver sensitivity.")
)
) | End Reserved_Parameters
(Model_Specific
(taps
(1 (Usage InOut) (Format Range 0 -1.0 1.0)(Type Tap)
(Default 0) (Description "First DFE tap.")
)
)
) | End Model_Specific
)
******************************************************************************
******************** BELOW FOR ADMINISTRATION AND TRACKING *******************
******************************************************************************
BUG NUMBER: 129
SEVERITY: [FATAL, SEVERE, MODERATE, ANNOYING, ENHANCEMENT] (ANNOYING)
PRIORITY: [HIGH, MEDIUM, LOW] (MEDIUM)
STATUS: [OPEN, CLOSED, WILL NOT FIX, NOT A BUG] OPEN
FIXED VERSION:
FIXED DATE:
NOTES ON BUG FIX:
Classified at the IBIS teleconference meeting on XXXXXXXXX, 2011.
To be fixed in a later release.
******************************************************************************
******************************************************************************
Other related posts:
