• 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. How to access the auto calculation command or function of...

Stats

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

How to access the auto calculation command or function of some devices' second-order parameters (e.g., SCA), better in command line form?

Alex Liao
Alex Liao over 8 years ago

Hey smart guys,

As you know, if you change the w, l and nf, and enable the WPE effects for lower-than-CMOS90nm technology MOSFET device, you can see the SCA/SCB/SCC are auto-calculated and reflected through the device property window. And if you change w and nf, the SCA dynamically updates. That means, when you change the w and nf, a black box function is called to do the calculation of such second-order parameters. If you only calculate couples of SCA based on few different w and nf, you can let the property window do it for you manually (i.e., GUI-based approach). If you have 1000 test cases, how can you do this? Is there a command line based approach that when you specify a change of w and nf in a netlist maybe, and you proceed to call a certain command or a function to do the calculation of SCA and then get the SCA value back annotated to the netlist to have the netlist consider the WPE effect?

Because the device property window have such dynamics, so behind the GUI, there must be a function called. Or I guess it kind of finds the corresponding SCA value through the foundry provided model. In this case, the Cadence must have a search or map function operated on the foundry model to be dynamic in terms of SCA calculation.

Any knowledge is appreciated.

Thanks,

Alex

  • Cancel
Parents
  • Alex Liao
    Alex Liao over 8 years ago
    Hi Andrew,

    After I played with the ADE XL I really learned a lot and benefited from those new features regardless of the more complex settings and some learning efforts. Initially I thought there were only w, l, fingers, and m that can be set as “Parameters”, but once I chose Variables and Parameters => from Whitelist by default to All, I could choose any parameter to be a “Parameter” and callbacks are enabled for sure. That’s a huge convenience. A lot of thanks here.

    One last thing that bothers me is that I do not know how to specify a Parameter dependent variable. For example, I can specify fingers (nf) as a Parameter, but when I do the sweeping, from nf = 1 to 8, w=8u, it goes to cases of 1*8u, 2*8u, 3*8u, …, 8*8u which is not what I want. If I also specify w to be a Parameter, then it will generate 64 points and only 8 of them are desired.

    I tried to put M0/nf and M0/w into a Group Parameter Set and specify nf changes from 1 to 8 with 8 steps, and w changes from 8u to 1u with 8 steps as well. Then it gives me 8 simulations but with incorrect combination. That is, 1*8u, 2*7u, 3*6u,…,8*1u (linear changes). Only the first and last simulations are wanted. Certainly I can specify the 8 changes of w in the inclusion list individually but very low efficient in a large sweep case. I tried to put ‘M0/w’ = 8u/nf with 8 steps in the Group Parameter Set with the ‘M0/nf’, but the XL treats the nf as a variable rather than a Parameter. I researched a little bit about Match Parameters and Ratio Parameters but do no help on this case. Do you have any idea on this?

    Thanks,
    Alex
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Alex Liao
    Alex Liao over 8 years ago
    Hi Andrew,

    After I played with the ADE XL I really learned a lot and benefited from those new features regardless of the more complex settings and some learning efforts. Initially I thought there were only w, l, fingers, and m that can be set as “Parameters”, but once I chose Variables and Parameters => from Whitelist by default to All, I could choose any parameter to be a “Parameter” and callbacks are enabled for sure. That’s a huge convenience. A lot of thanks here.

    One last thing that bothers me is that I do not know how to specify a Parameter dependent variable. For example, I can specify fingers (nf) as a Parameter, but when I do the sweeping, from nf = 1 to 8, w=8u, it goes to cases of 1*8u, 2*8u, 3*8u, …, 8*8u which is not what I want. If I also specify w to be a Parameter, then it will generate 64 points and only 8 of them are desired.

    I tried to put M0/nf and M0/w into a Group Parameter Set and specify nf changes from 1 to 8 with 8 steps, and w changes from 8u to 1u with 8 steps as well. Then it gives me 8 simulations but with incorrect combination. That is, 1*8u, 2*7u, 3*6u,…,8*1u (linear changes). Only the first and last simulations are wanted. Certainly I can specify the 8 changes of w in the inclusion list individually but very low efficient in a large sweep case. I tried to put ‘M0/w’ = 8u/nf with 8 steps in the Group Parameter Set with the ‘M0/nf’, but the XL treats the nf as a variable rather than a Parameter. I researched a little bit about Match Parameters and Ratio Parameters but do no help on this case. Do you have any idea on this?

    Thanks,
    Alex
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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