Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 15683
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NLPLabels vs ILLabels

theopaone

I am cleaning up a bunch of schematic libraries and get them ready for reuse. The symbol instance display text is a mixed bag of ILLabels and NLPLabels.

I want to standardize on a single way of displaying the value of the instance name (cdsName() or [@instanceName]), pin connections (cdsTerm("termName") or [@<pinName>] and parameter values (cdsParam(<index>) or [@<paramName>]. I am leaning towards the NLP labels but are there cases where they won't work or the the ILLabels are prefered?

Also, there are these textDisplay objects, can they be used instead?

Thanks

Ted

Parents

  • Ted,

    If you have CDF (and are supporting ADE), then I would definitely suggest going with the ILLabels, specifically cdsName(), cdsParam(N) and cdsTerm("termName"). These have the benefit of being configurable via the annotation controls (View->Annotations in IC616, Edit->Component Display in older releases, and also via Results->Annotate in ADE). The cdsName can be used to show the instance name, cellName, both, neither; the cdsTerm can be used to display term name, net name, voltage, current, both (from DC or transient, say); the cdsParam can be used to display instance parameters, model parameters, operating point parameters, expressions of operating point parameters (in IC616) - and you can control which parameter gets displayed in which slot.

    If however you want to display a fixed property that you don't want the user to have control over, you can use NLP labels too. There's no harm in having both.

    Also ILLabels can be used for more complicated cases - where you need SKILL to look something up starting from ilInst.

    I don't think I've used textDisplays in a symbol - not sure the UI particularly has support for this (might be used for pin names in a pin symbol - can't remember off the top of my head). So I don't see any good reason for that.

    Regards,

    Andrew

Reply

  • Ted,

    If you have CDF (and are supporting ADE), then I would definitely suggest going with the ILLabels, specifically cdsName(), cdsParam(N) and cdsTerm("termName"). These have the benefit of being configurable via the annotation controls (View->Annotations in IC616, Edit->Component Display in older releases, and also via Results->Annotate in ADE). The cdsName can be used to show the instance name, cellName, both, neither; the cdsTerm can be used to display term name, net name, voltage, current, both (from DC or transient, say); the cdsParam can be used to display instance parameters, model parameters, operating point parameters, expressions of operating point parameters (in IC616) - and you can control which parameter gets displayed in which slot.

    If however you want to display a fixed property that you don't want the user to have control over, you can use NLP labels too. There's no harm in having both.

    Also ILLabels can be used for more complicated cases - where you need SKILL to look something up starting from ilInst.

    I don't think I've used textDisplays in a symbol - not sure the UI particularly has support for this (might be used for pin names in a pin symbol - can't remember off the top of my head). So I don't see any good reason for that.

    Regards,

    Andrew

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.