Stats

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

using letseq or parameterized property/parameter in graphical PCell

leichtfm
Hello,
I'm trying to edit an existing graphical PCell (layout) using IC6.1.6.
There are multiple stretches & parameterized properties that share a major part of their expression.
for example:
Stretch 1:
((evalstring(w)+2.0+dx)*(nx-1))
Inherited Parameter 1:
(xTotal-((evalstring(w)+2.0+dx)*(nx-1))+0.02)

I thought about using parameterized property for the shared part, however they would not accessible within the layout.
Another idea was to use letseq with the intention to make it easier to make changes, however this would still require to change all expressions.
Besides that, there seems to be a small bug, as the parameter "width" is automatically added to the pcell parameters, even if this parameter is not used.
Stretch 1:
letseq(((w evalstring(w))(width (w+2.0+dx)*(nx-1)))) width)
Inherited Parameter 1:
letseq(((w evalstring(w))(width (w+2.0+dx)*(nx-1)))) (xTotal - width + 0.02))
Is there any flexible way to implement that?
thx in advance & best regards,
Michael

  • Hi Michael,

    Not really. The Graphical PCell capability has not really been enhanced for many years, and certainly doesn't support letseq or using localised variables this way.

    If you want a graphical UI-based means of creating PCells then Cadence PCell Designer is the best way of achieving that (the link is to the data sheet - you'd need to contact your account team for more details). Alternatively, writing your PCell using SKILL could also achieve your desire of sharing computation using local variables.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    thank you for the fast response, I really appreciate your help.

    I'll take a look into the PCell-Designer!

    Regards,

    Michael

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.