Stats

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

What happened when compile graphic pcell to skill code?

richardyuan

Hello, 

I want to create a little tool that can capture the user action in GUI, then convert it into pCell, something like user create graphic pcell and then compile it to skill code. 

Are there any more detail when compile graphic pcell to skill code is only one step? I want to know what happened and so I can start from.

Any good suggestion is preferred. Thank you for advance.

Parents
  • skillUser

    Hi Richard,

    What you are asking for is not trivial, if I understand the request correctly. If I understand correctly you want some way of capturing user actions in a layout as a sequence of SKILL commands and then somehow make this into a PCell?  I would think that the easiest place to start is actually the log file - I would suggest that you have some sort of "START" and "STOP" markers to demarcate the start and end of the captured actions, and then copy these off to a separate file.  However, the commands that you use interactively are typically not the commands that you would use in a PCell.  It would take a developer to then convert that file into a repeatable function, and then they would need to decide on which 'variables' would be parameters (take a simple rectangle: width, height, layer, bBox, connectivity? and so on) or arguments to the function. The last step would be to wrap that function in a PCell (i.e. add the pcDefinePCell statement around the function that does all the work, passing each function argument from a PCell parameter).

    Hopefully this is a "good suggestion".

    Best regards,

    Lawrence.

Reply
  • skillUser

    Hi Richard,

    What you are asking for is not trivial, if I understand the request correctly. If I understand correctly you want some way of capturing user actions in a layout as a sequence of SKILL commands and then somehow make this into a PCell?  I would think that the easiest place to start is actually the log file - I would suggest that you have some sort of "START" and "STOP" markers to demarcate the start and end of the captured actions, and then copy these off to a separate file.  However, the commands that you use interactively are typically not the commands that you would use in a PCell.  It would take a developer to then convert that file into a repeatable function, and then they would need to decide on which 'variables' would be parameters (take a simple rectangle: width, height, layer, bBox, connectivity? and so on) or arguments to the function. The last step would be to wrap that function in a PCell (i.e. add the pcDefinePCell statement around the function that does all the work, passing each function argument from a PCell parameter).

    Hopefully this is a "good suggestion".

    Best regards,

    Lawrence.

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.