[ibis-macro] Re: New version of the Typos BIRD draft is on the ATM web site

  • From: Bob Ross <bob@xxxxxxxxxxxxx>
  • To: Arpad_Muranyi@xxxxxxxxxx
  • Date: Tue, 18 Jan 2011 11:32:55 -0800

Arpad:

The section 10 definition looks fine, and is the basis
for "leaf/value pair" meaning that only at the end
of each branch, only the parameter name and its value(s)
are sent to/from the .dll.  I would not change this.

You state, "In this context "parameter name" could mean anything,
including the reserved words."

I understand that the words "Type", "Usage",
"Format" (and/or <data_format>, "Default", and "Description"
are called leaves in Section 6c, but are NOT included in the
part AMI_parameters_in or AMI_parameters_out strings because
they are NOT parameter names in the context of the Section 10
definition. Am I correct?

So in simple words, the EDA tool constructs *_in strings
by stripping off all of the leaves of an .ami file parameter and
inserts the value or values associated with it to form a new
leaf/value(s) pair where the leaf_name is a parameter name.

We have not resolved this, but "Table" has special case syntax.
"Table" is defined as a 'parameter name' that "names a branch of
a parameter tree rather than a single leaf."  A Table has "Labels" and
its row(s) as leaves.

We should note that "Table" is an exception that it is not included
as part of the <data_format> "leaf" definition, nor is it a true
parameter_name in the sense of the page 6-7 format for parameters:

   (parameter name, (Usage <usage>) ....)

My main concern was that mixing definitions creates more confusion
and requires more work to be precise in what is legal and illegal.
That is why I wanted to back off rather than expand on using leaf.
Alternatively we could use a different term such as ami_leaf.

Bob


Muranyi, Arpad wrote:
Bob,

I think the problem is that a leaf is not only (<parameter name>
<value>)
as defined in Section 10.  (Usage In) is also a leaf/value pair, but
"Usage" is not a parameter name, it is a reserved name.  So I would
correct the definition in Section 10 so that it wouldn't define the
leaf/value pair as (<parameter name> <value>).  By the say, notice that
in this BIRD we define what an "AMI parameter" is, which seems to have
a different meaning from the "parameter name" used in this area in
Section 10.  In this context "parameter name" could mean anything,
including the reserved words.

Thanks,

Arpad
========================================================================
==

-----Original Message-----
From: Bob Ross [mailto:bob@xxxxxxxxxxxxx] Sent: Tuesday, January 11, 2011 1:21 PM
To: Muranyi, Arpad
Cc: IBIS-ATM
Subject: Re: [ibis-macro] New version of the Typos BIRD draft is on the
ATM web site

Arpad:

Changes look good:

Here is my "leaf" issue on page 4 that I found confusing.

Based on the reference to Section 10, and specifically page 187,
a leaf is defined as:

<leaf>:
   ( <parameter name> whitespace <value list> )

On page 4 of this draft:

All "leaves" of the .ami file must begin with one of the following
reserved words:

    Type
    Usage
    ....

Technically a "leaf_name" would be a parameter name and not the
reserved word according to Section 10 definition.

So perhaps the wording should be ...

"All "AMI parameters" must begin with the parameter name followed
by one of the following reserved words:

     Type
     Usage
     ....

Later it is stated, "Multiple leaves containing the same reserved word
are not allowed within an AMI Parameter branch."

This could be modified to

"Reserved words shall not be repeated within an AMI Parameter branch."

Bob





Muranyi, Arpad wrote:

This is to announce that a new version of the Typos BIRD draft
has been posted to the ATM web site:



http://www.vhdl.org/pub/ibis/macromodel_wip/archive/20110111/arpadmurany

i/IBIS-AMI%20Typographical%20Corrections%20BIRD%20draft%208/Typos_Format

_Value_Default_BIRD_8.pdf

(This is the same file that was emailed out a few minutes ago
with the Agenda for today's meeting).  In this version I made
the following changes:

   - added "(defined below)" for Default
   - added words to disallow duplicate leaves in the same branch
   - removed the "graceful" stuff
   - moved editorial notes on the bottom to background information

and I am planning to discuss this in the ATM teleconference
today.  Please familiarize yourself with these changes so we
can have a meaningful discussion.

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







--
Bob Ross
Teraspeed Consulting Group LLC     Teraspeed Labs
121 North River Drive              13610 SW Harness Lane
Narragansett, RI 02882             Beaverton, OR 97008
401-284-1827                       503-430-1065
http://www.teraspeed.com           503-246-8048 Direct
bob@xxxxxxxxxxxxx

Teraspeed is a registered service mark of Teraspeed Consulting Group LLC

---------------------------------------------------------------------
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: