[ibis-macro] IBIS-ATM teleconference - Agenda for 8/2/2011
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 2 Aug 2011 17:15:07 +0000
Time: August 2, 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_tips.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:
Arpad: Update BIRD 137 with the comments in the last ATM meeting
- done (see attachments)
Arpad: Update BIRD 127 according to the rules in BIRD 137
- pending
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) Backchannel BIRD draft update (Ken)
- discussion, questions, comments?
5) BIRD 137 (Arpad)
- My notes from the last meeting say:
In 5.1 say: Never be a null pointer, always point to a string
which contains the root name.
This conflicts the notes I took in the same meeting:
Null pointer,
Pointer to a null,
String with root name only
Which rule do we want?
6) Parameter string syntax question
- See BIRD137.1 definition for parameter and message strings
- this includes now the definition of empty parameter and
message strings
- See BIRD 135.1 for the definition of empty string parameters
(under #8)
7) BIRD 127.1 needs to be corrected, because it contradicts the
the AMI_parameters_in/out string rules (optional vs. must):
|* The EDA tool must pass a string to the AMI executable model
|* through the AMI_parameters_in argument which contains all of
|* the leaf/value pair formatted Usage In and Usage InOut AMI
|* parameters defined in the .ami file and nothing else.
|*
|* The AMI executable model must return a string to the EDA tool
|* through the AMI_parameters_out argument which contains all of
|* the leaf/value pair formatted Usage InOut and Usage Out AMI
|* parameters defined in the .ami file and nothing else.
8) BIRD 121.1, data management parameters (file support) (Walter)
- discussion, questions, comments?
9) BIRD 122; Analog Buffer BIRD (Walter)
- replaced with ISS_Buffer_BIRD.doc
10) BIRD 123.2.2, jitter parameters (includes Row 37) (Walter)
- review latest changes and graphics
- do these changes answer the questions raised before:
- remove Usage Out from the BIRD? or
- specify which function (Init or GetWave) can return values?
- specify what the EDA tool should do with the returned values?
11) BIRD 124.1, dependency table (Walter)
- questions, comments?
12) Info, Out, InOut BIRD (Arpad)
- latest wording includes "in order to be compliant with this
specification, Model_Specific parameters ... must not ...",
and omits the word "simulation" so it's meaning doesn't have
to be defined
- any comments, questions on this draft?
Thanks,
Arpad
=====================================================================
Other related posts:
