Stats

  • Locked Locked
  • Replies 9
  • Subscribers 144
  • Views 6688
  • 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

Schematic net/inst name mapping: case-insensitive to case-sensitive

tweeks
Here's a fun SKILL problem to chew on:

I have a tool that reads SPF (Standard Parasitic Format) files and spits out case-INsensitive hierarchical net and instance names. I want to probe them in Virtuoso Schematic Editor (latest version) using geAddNetProbe().

Problem: how to map the case-insensitive names from the SPF tool like this

"/rtop/r<0>/rdb<0>/decovst/nd_share"

to names that will be recognized by geAddNetProbe() like this:

"/rtop/r<0>/rdb<0>/DECOVST/nd_share"

(in this case, "DECOVST" is in upper-case in the Virtuoso schematic.)

You can assume there will never be a schematic with two instance or net names differentiated only by case.

I'd like to avoid traversing the entire hierarchy to build a mapping table of every instance and net name, but as I comb the SKILL docs, it's starting to look like there is no other way.... 

   --tweeks
Parents

  • How else would you imagine it being done?  Unless you know what's in each schematic, you won't know what to map to - and you'll need to traverse the hierarchy to collect that information. Of course, you can optimize it by only storing the mapping per cellView rather than per hierarchical path, but I can't see how you would know what to map to unless you know what's there.

    Andrew

Reply

  • How else would you imagine it being done?  Unless you know what's in each schematic, you won't know what to map to - and you'll need to traverse the hierarchy to collect that information. Of course, you can optimize it by only storing the mapping per cellView rather than per hierarchical path, but I can't see how you would know what to map to unless you know what's there.

    Andrew

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.