[ibis-macro] Re: ibischk5, Version 5.1.0 Under Development Question
- From: "Bob Ross" <bob@xxxxxxxxxxxxx>
- To: <wkatz@xxxxxxxxxx>, "'IBIS-ATM'" <ibis-macro@xxxxxxxxxxxxx>
- Date: Wed, 15 Aug 2012 17:07:09 -0700
Walter:
Thanks. I missed that.
Bob
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz
Sent: Wednesday, August 15, 2012 4:43 PM
To: bob@xxxxxxxxxxxxx; 'IBIS-ATM'
Subject: [ibis-macro] Re: ibischk5, Version 5.1.0 Under Development Question
Bob,
IBIS 5.1 is clear on this:
"Branches may define AMI Parameters and/or other branches. A branch which
contains one or more sub-branches may only contain the (Description
<string>) leaf in addition to the sub-branches. Each sub-branch of a
branch must have a unique name."
So I vote for 2.
Walter
-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Wednesday, August 15, 2012 7:38 PM
To: 'IBIS-ATM'
Subject: [ibis-macro] ibischk5, Version 5.1.0 Under Development Question
All:
The parser developer asked a question for ibischk5, Version 5.1.0 under
development:
"Currently there are no checks on Model_Specific branch/parameter names
being unique. Specifically, the parser will allow a duplicate Tap
parameter name to be specified. The spec does not say anything about this
either."
What should we do?
1. No checks since nothing is specified.
2.Warning if any parameter and/or branch is duplicated (e.g., Tap
parameter name 1 and branch 1, or Tap parameter name 1 repeated or branch
name 1 repeated)
in the Model_Specific section regardless of hierarchy.
Note, the Tap parameter is used as an example, but the checks would apply
to any set of branch/parameter names
3. Warning if parameter names are repeated Distinct Warning if branch
names are repeated.
So branch names can be the same as parameter names as long as branch names
are checked separately from parameter names. So 1 is allowed as a Tap
parameter name and also as a branch name.
4. Warning if a parameter is repeated only in the same branch hierarchy,
and if a branch name is repeated within the same sub-hierarchy - e.g., a
bank of distinctly named Tap parameters under branch 1 and a similar set
of names under branch 2 are permitted.
5. Any other rule.
I favor rule 2 or 3 to keep the check simple.
Advice?
Bob
--
Bob Ross
Teraspeed Consulting Group, LCC
http://www.teraspeed.com
bob@xxxxxxxxxxxxxx
Direct : 503-246-8048
Teraspeed Labs: 503-430-1065
Headquarters: 401-284-1827
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
---------------------------------------------------------------------
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:
