Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13878
  • 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 know the name of the properties of the device without editing this property?

dell1

For example: I want to know the name of length and width properties of the nmos without editing in these properties(its length and width) then using nmos->prop->??  that show me an array like the following

("l" value "5u" valuetype "string" -----------) ("w" value "5u" valuetype "string")

but the problem is that these names(l, w) are technology dependent, so I want in my code to know these names in any technology 
so as to make my code technology independent .

 

Thanks in advance.

Parents
  • Given that both the property name (w and l in your example) and the prompt for these properties (defined in the CDF for the component) are technology specific, I can't see how you can do this without storing a mapping somewhere as to the property names that you're interested in for that technology.

    There is nothing special to Virtuoso about w and l. They called be called anything, and could mean anything.

    You might be able to look in the propMapping in the spectre simInfo in the CDF to see what gets netlisted as w and l, but even that's not reliable because the parameter that gets output may be one computed by a CDF callback, and thus there would be no way to know what the source parameter was from which they were derived.

    Best Regards,

    Andrew
Reply
  • Given that both the property name (w and l in your example) and the prompt for these properties (defined in the CDF for the component) are technology specific, I can't see how you can do this without storing a mapping somewhere as to the property names that you're interested in for that technology.

    There is nothing special to Virtuoso about w and l. They called be called anything, and could mean anything.

    You might be able to look in the propMapping in the spectre simInfo in the CDF to see what gets netlisted as w and l, but even that's not reliable because the parameter that gets output may be one computed by a CDF callback, and thus there would be no way to know what the source parameter was from which they were derived.

    Best Regards,

    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.