• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Cannot annotate DC operating point of a MonteCarlo version...

Stats

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

Cannot annotate DC operating point of a MonteCarlo version of a mosfet

pollostrazon
pollostrazon 6 months ago

Good afternoon everyone,
I searched through the forum and opened a lot of discussions, but I am not really sure the problem I am facing is the same than the others, so I am posting my own thread. Please excuse me if I am missing something, bacause I have never programmed Skill or changed a CDF.

I am working with UMC 110. When changing the models from the standard ones, to the one implementing MC parametrization, I lose DC operating point annotation. From what I understand, these mosfets are implemented as "inline subckt," but when I browse through the result viewer, I see that if a "standard" mosfet has a list of dcOpInfos under its name (let's say NM0 and I am searching for "ids"), a "MonteCarlo" one has four different folders, and under one of them (let's say "mnig") I find the dcOpInfos I am looking for. Problem is that CDF for OP point to "ids" but cannot find it since it is one level below (NM0.mnig:ids).

I check with a TSMC 65 library I have access to. From what I understand, they implement opParamExprList = ("X" "OP(mappedRoot(\".sub\") \"X\") to bring X one level higher. So I tried to add to the (empty) opParamExprList = ("ids" "OP(mappedRoot(\".mnig\") \"ids\") for all the MC mosfet models, but I am not seeing any change in the annotation of the OP. I was expecting the line "ids=..." to be available. I also checked this for a similar problem with OPT and stepped through it, but it didn't help.

Hopefully I was explainatory enough.
Can someone help me out with this? That would be much appreciated. Another approach I have though about is to have a SKILL script that allow me to change the models from "normal" to MC one and back, but I couldn't get any to work.

Thank you,
Paolo

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information