I tend to think that the full hierarchy should be specified for
hierarchical parameters, as twig-level names may be terse enough to be
commonly duplicated elsewhere, e.g. a fictitious hierarchical parameter
"PAM4_SlicerThreshold(lower" which is in it's fullness quite descriptive
and unique but "lower" is dangerously common.
Bob
On Tue, Sep 29, 2015 at 3:53 PM, Muranyi, Arpad <Arpad_Muranyi@xxxxxxxxxx>
wrote:
Mike,
You raised an interesting question. I tend to agree with Walter
that we should keep it simple. So I wonder whether it is
necessary at all to indicate the hierarchy of the special
parameter. Wouldn’t it be enough to just list its name, and
nothing else?
(SpecialParameters (Usage Info) (Type String)
(Table
(“TStoneFile”)
)
)
On the other hand, the next question is whether someone would make
a model which has more than one branch in which the same parameter
name appears in two different contexts, one being compliant and
the other not. In that case we would need to preserve the entire
hierarchy of the parameter name to be able to distinguish one from
the other… Would anyone ever do this?:
(Model_Specific
(AnalogModel_1
(TStoneFile (Usage Info) (Type String) (Value “something.s4p”)
(Description “Spec compliant on-die model”))
)
(AnalogModel_2
(TStoneFile (Usage Info) (Type String) (Value “something.s4p”)
(Description “Non-compliant on-die model”))
)
)
Thanks,
Arpad
=================================================================
*From:* Walter Katz [mailto:wkatz@xxxxxxxxxx]
*Sent:* Tuesday, September 29, 2015 3:37 PM
*To:* mlabonte@xxxxxxxxxx; Muranyi, Arpad
*Cc:* ibis-macro@xxxxxxxxxxxxx
*Subject:* RE: [ibis-macro] Out InOut Info BIRD nested parameters
Mike,
No need to be so complicated:
(SpecialParameters (Usage Info) (Type String)
(Table
(“AnalogModel(TStoneFile”)
)
)
Since in “’s (‘s are allowed.
Walter
*From:* ibis-macro-bounce@xxxxxxxxxxxxx [
mailto:ibis-macro-bounce@xxxxxxxxxxxxx <ibis-macro-bounce@xxxxxxxxxxxxx>] *On
Behalf Of *Mike LaBonte
*Sent:* Tuesday, September 29, 2015 2:26 PM
*To:* Arpad Muranyi
*Cc:* ibis-macro@xxxxxxxxxxxxx
*Subject:* [ibis-macro] Out InOut Info BIRD nested parameters
Hi Arpad,
A followup to the IBIS-ATM call today: the Model_Specific parameters that
we want to list in SpecialParameters could possibly be nested under
intermediate branches. For example:
(Model_Specific
(AnalogModel
(TStoneFile (Usage Info) (Type String) (Value “something.s4p”)
(Description “Broadband on-die model”))
)
)
How should that be represented in SpecialParameters? A few ideas:
1. Use spaces to delimit hierarchical elements, since parameter names
cannot contain spaces:
(SpecialParameters (Usage Info) (Type String)
(Table
(“AnalogModel TStoneFile”)
)
)
2. Use table columns:
(SpecialParameters (Usage Info) (Type String String)
(Table
(“AnalogModel” “TStoneFile”)
)
)
3. Only top level can be specified, everything under it is special:
(SpecialParameters (Usage Info) (Type String)
(Table
(“AnalogModel”)
)
)
There may be other ways …
Mike
