• 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 evaluate the termMapping for Spectre when it contains...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 143
  • Views 732
  • 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 evaluate the termMapping for Spectre when it contains a "Function"

MFahmy
MFahmy over 2 years ago

Hi, 

I am using a script to submit a number of Spectre simulations, saving and reading the terminal current of specific instances for each simulation 

for the different simulations I would need to save different terminal currents of a group of devices i.e sim(n)-> save and process the terminal current of Inst(n) , and the instances are different cells, so they have different pin names

to get the pin mapping of the terminals I came across "asiMapTerminalName" which works if the terminal name is mapped to a string in some cases the mapping returns a "Function" rather than a string (as also visible in the simulator information section of the CDF editor), 

is there a way to evaluate the mapping functions to get back the mapped value ?

save=allpub is not really an option in my case, that's why I need the spectre mapped terminal names to be able to place it in the save statement and to be able to access the signal in the results db

virtuoso : ICADVM20.1-64b.500.28

Spectre: sub-version  21.1.0.546.isr13 

EDIT: 

I looked at the "useterms" options and if I understood correctly it wouldn't help as I would need to have a save all statement to be able to access current by index ?

Thanks, 

Fahmy 

  • 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