Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 14595
  • 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

pcell conditional include default overrides any selection

gkaatz
When I instantiate a pcell created with the pcell tool, the checkbox on the Create Instance form or Edit Instance Properties has no effect. The default state of the conditional include is shown. It used to work but with various edits has stopped doing so.

  • Hi Gkaatz,

    Which checkbox?  Do you expect anybody to be able to answer your question without sufficient detail of the problem?  Which version are you using?  What "pcell tool" created the PCell?  It sounds as though the pcell has been edited/changed so that the conditional inclusion parameter is no longer working - I would expect the PCell developer to be the best person to ask about this.

    I am sorry if this is not helpful, but there is very little information to go on.  An incomplete question will yield an incomplete answer (or no answer at all).

    Regards,

    Lawrence.

  • The checkbox I am referring to is the one created when you make a shape a conditional inclusion from within the pcell tool of Virtuoso Layout editor. I am using 5.1.41 (5141_ISR144).

  • Are you making/editing a graphical PCell then?   You should be able to perform a Summary of the parameters and check that the shape(s) are still correctly associated with the parameter for inclusion. You might need to supply more information, perhaps screen shots?

    Regards,

    Lawrence.

  • Lawrence, Yes it is a graphical pcell. The summary shows the conditional include, see below. When the pcell is instantiated, the default state of the conditional inclusion is reflected in the new cell. If I invert the default state and recompile, when I instantiate another cell, the new default state is reflected in the new cell and the first one does not change. Gary Parameters defined in this parameterized cell: FPlength driftLength driftSpaceToPoly includeThkOxide? l Stretch ------- Stretch Type: Horizontal Name or Expression for Stretch: l Stretch Direction: right Reference Dimension (Default): 0.250000 Min Value: 0.250000 Stretch Type: Horizontal Name or Expression for Stretch: ((FPlength - driftSpaceToPoly) + 0.3) Stretch Direction: right Reference Dimension (Default): 0.500000 Stretch Type: Horizontal Name or Expression for Stretch: driftSpaceToPoly Stretch Direction: right Reference Dimension (Default): 0.300000 Stretch Type: Horizontal Name or Expression for Stretch: ((driftLength - FPlength) + 0.5) Stretch Direction: right Reference Dimension (Default): 1.000000 Conditional Inclusion --------------------- Number of Objects in this group: 1 Name or Expression: includeThkOxide? Dependent Stretch: Adjustment to Stretch:

  • Little hard to follow, but my guess is that you have a CDF parameter defined and the CDF default is different from the pcell default for this parameter. If you've done that (not a wise idea), then what can happen is that if you instantiate the component where the value on the form matches the CDF default, it omits the property on the instance, and hence the pcell gets the pcell default. If  you have a value which is different from the CDF default, it stores the property on the instance - but since that's the same as the pcell default, you still get the pcell default.

    If you really must have the CDF default different from the pcell default, use storeDefault=yes on that CDF parameter. But it's really best to ensure that the CDF default values match the pcell default values.

    This however is a bit of a guess as to what your problem is - the info supplied above is a big confusing.

    Regards,

    Andrew.

  • Andrew, Thanks for the suggestion but the boolean default seems to be the same in both the pcell and the CDF. Gary

  • Hi Gary,

    In that case I'd probably need to see the data. Given that you probably can't post it here - you'd be best creating a service request.

    Best Regards,

    Andrew.

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.