Stats

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

Optimal (fast) callback for pcells

Vasili

 What is the optimal (fast) callback procedure for pcells?

For example, I have a pcell that draws a shape that has a resistance. The value of the resistance is calculated inside pcell. I need to know the resistance of the instance, for example, to create another resistorwith a predefined total resistance. Is CDF callback the best solution or it could be avoided?

I even not sure that "callback" is the correct term. I simply want to know the numerical value of a local variable that has been used inside pcell to execute dbCreatePCell or rodCreatePCell.For example, I can creare a handle and assign to this handle the numeric value of my parameter and then get its value from the instance by using get ...handle. But maybe there is a "recommended" solution?.

Vasili 

Parents

  •  Hi Andrew,

     Thank you very much. Your comments are good for me. I am doing strange things (in particular, I pretend that the superconductor electronics exists), and I should appology for strange questions. It would be very natural for any new comer that different views of one cell should have common properties. Of course one can argue that, say, (Virtuoso) layout view deals with geomety, while schematic view deals with electric properties. But I would like to state that geometrical properties are derivative of electric properties and parasitic electrical properties are derivative of geomerty. I already know how to use pcell technique to derive geometry from required electrical properties and I know how to extract parasitic electrical properties from the layout. But I did not find a convenient way to bound together scematics and layout views. Ideally it could be that the layout adjusts itself if some schematics parameter is changed or the schematic change itself if the layout is edited.

    I guess, there are fundamental problems with joining different cell views. Where I can read about such view unification? I know that CDF allows to synchronize views (and parameter values) but why not to declare that could be a single parameter that is shared by several cell views?  

Reply

  •  Hi Andrew,

     Thank you very much. Your comments are good for me. I am doing strange things (in particular, I pretend that the superconductor electronics exists), and I should appology for strange questions. It would be very natural for any new comer that different views of one cell should have common properties. Of course one can argue that, say, (Virtuoso) layout view deals with geomety, while schematic view deals with electric properties. But I would like to state that geometrical properties are derivative of electric properties and parasitic electrical properties are derivative of geomerty. I already know how to use pcell technique to derive geometry from required electrical properties and I know how to extract parasitic electrical properties from the layout. But I did not find a convenient way to bound together scematics and layout views. Ideally it could be that the layout adjusts itself if some schematics parameter is changed or the schematic change itself if the layout is edited.

    I guess, there are fundamental problems with joining different cell views. Where I can read about such view unification? I know that CDF allows to synchronize views (and parameter values) but why not to declare that could be a single parameter that is shared by several cell views?  

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.