[ibis-macro] Re: IBIS-ATM teleconference - Agenda for 6/30/2009, Re. AMI Related Questions
- From: "Walter Katz" <wkatz@xxxxxxxxxx>
- To: <Arpad_Muranyi@xxxxxxxxxx>, "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 30 Jun 2009 14:44:00 -0400
Arpad,
"Default" was added at the very end of developing the BIRD, and the BIRD was
not carefully reviewed to handle the combinations of
Value/Corner/List/Range/Increment and Default. There are a number of these
inconsistencies that we found, and we intended them to be a part of AMI
clarification, and improvement BIRD.
The following statement is False.
"Also, both Init_Returns_Impulse and GetWave_Exists cannot be True
simultaneously."
They can be both True simultaneously.
Walter
Walter Katz
303.449-2308
Mobile 720.333-1107
wkatz@xxxxxxxxxx
www.sisoft.com
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of Muranyi, Arpad
Sent: Tuesday, June 30, 2009 2:13 PM
To: IBIS-ATM
Subject: [ibis-macro] Re: IBIS-ATM teleconference - Agenda for 6/30/2009,
Re. AMI Related Questions
Thanks Walter for the reply.
Here is another one that just came in from the
developer of the parser:
Here is an inconsistency pertaining to InitReturnsImpulse and
GetWaveExists
As per the spec:
The following reserved parameters are used by the EDA tool
| and are required if the [Algorithmic Model] keyword is
| present. The entries following the reserved parameters
| points to its usage, type and default value. All
reserved
| parameters must be in the following format:
| (parameter_name (Usage <usage>)(Type <data_type>)
| (Default <values>) (Description
<string>))
However, further down we find in the spec, that Default is NA ( which
makes sense since the parameter is required)
| | Reserved Parameter | Required Default | Info In Out InOut
|
| | Init Returns Impulse | Yes NA | X
|
| | GetWave Exists | Yes NA |
X |
And the table further down implies that the Format must be specified and
must be of format type "Value"
| | Data Format |
| ===================================================================
| | Reserved Parameter | V | R | C | L | I | S | G | D | D | T |
| | | a | a | o | i | n
| t | a | u | j | a |
| | | l | n | r | s | c
| e | u | a | R | b |
| | | u | g | n | t | r
| p | s | l | j | l |
| | | e | e | e | |
| s | | D | | e |
| +-------------------------+---+---+---+---+---+---+---+---+---+---+
| | Init Returns Impulse | X |
| | GetWave Exists | X
|
The example in the spec is
(Init_Returns_Impulse (Usage Info) (Type Boolean)(Default True))
(GetWave_Exists (Usage Info) (Type Boolean) (Default True))
Which is inconsistent as above. Also, both Init_Returns_Impulse and
GetWave_Exists cannot be True simultaneously.
Arpad
=================================================
-----Original Message-----
From: Walter Katz [mailto:wkatz@xxxxxxxxxx]
Sent: Tuesday, June 30, 2009 12:39 PM
To: Muranyi, Arpad; IBIS-ATM
Subject: RE: [ibis-macro] IBIS-ATM teleconference - Agenda for
6/30/2009, Re. AMI Related Questions
Arpad,
AMI Related Questions
a) The intent of the line length restrictions was to make it easier to
limit
the line width that EDA tools needed to deal with when displaying
Description information to users in an EDA tool GUI. Description data
can be
in multiple lines with <CR> and <LF> characters. Each line can be up to
120
characters, but the complete Description field between paired "'s can be
on
multiple lines and be more than 120 characters. I am not sure if the 120
character line limit applies to all lines in an AMI file, but we would
not
object to that interpretation or clarification for the purposes of
making it
more convenient to view and edit ami files. I would make it a Warning if
the
120 character line limit was exceeded.
b) The // appears in an example of "C" code, not in an example of AMI
text.
c) I do not understand this question.
d) There is a BNF description of the AMI syntax in the spec. "White
Space"
needs a definition.
e) The first token in the AMI file is a "root" or "tree" name. This is a
string that need not be the same name as the .ami or .dll file name.
Walter
Walter Katz
303.449-2308
Mobile 720.333-1107
wkatz@xxxxxxxxxx
www.sisoft.com
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of Muranyi, Arpad
Sent: Tuesday, June 30, 2009 12:11 PM
To: IBIS-ATM
Subject: [ibis-macro] IBIS-ATM teleconference - Agenda for 6/30/2009
Time: June 30, 2009 Noon US Pacific Daylight 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:
Walter: Redistribute the document with the changes discussed
- done
Arpad: Write a clarification BIRD to discuss accuracy issues
related to the various AMI clock_tick algorithms in an
IBIS-AMI DLL
- not done yet
Todd: Update the BIRD for IBIS S-parameter box based on
feedback from discussion
- not done yet
Any other AR-s?
Old ARs:
- Arpad: Write parameter passing syntax proposal (BIRD draft)
for *-AMS models in IBIS that is consistent with the
parameter passing syntax of the AMI models
- not done
- TBD: Propose a parameter passing syntax for the SPICE
[External ...] also?
- Arpad: Review the documentation (annotation) in the macro libraries.
- deferred until a demand arises or we have nothing else to do
4) Discuss AMI related questions raised by IBIS parser developer
a) The AMI file *is* restricted by the overall IBIS line length, as
shown
below. Was this intended? Are *all* lines in AMI files so
restricted?
Description <string>:
| ASCII string following Description describes a reserved parameter,
| model specific parameter, or the Algorithmic model itself. It is used
| by the EDA platform to convey information to the end-user. The entire
| line has to be limited to IBIS line length specification. String
| literals begin and end with a double quote (") and no double quotes
are
| allowed inside the string literals.
---------------------------
b) What is the official comment character for AMI files? If it is not
//,
why is this character sequence featured in an example?
c) Related to this, why are the AMI comment rules listed outside the AMI
file section in the IBIS specification?
d) What other syntax is permitted in AMI files (tab characters, etc.)?
We
are looking for something similar to IBIS Section 3.
e) Was the first token in the AMI file intended to be the filename and
*only*
the filename?
5) Finish our discussion on the IBIS-Interconnect-SPICE document
on topics marked with "further discussion needed".
(section on Library Integrity, it gives rules that are useful)
6) Comment on the latest document Walter distributed
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 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:
