• 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 Design
  3. Positioning the instances in Layout editor by using SKI...

Stats

  • Locked Locked
  • Replies 34
  • Subscribers 126
  • Views 32016
  • 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

Positioning the instances in Layout editor by using SKILL

RFStuff
RFStuff over 12 years ago

 Dear All,

I am trying to place copies of an instance/object ( say a simple via ) with 'x' distance separation in X-direction.

Is there any in-built feature already available in IC5141 ?

Otherwise, is there any solution ( SKILL script) already posted in the forum ? I searched but couldn't find so.

The code needs three functions:

1) Find the cordianate of the OBJECT/INSTANCE ( this I have already found in the Forum)

2) Copy the object. For this what is the SKILL function ?

3) Paste the desired distance separation ( For palcing wht is the simple SKILL function)

Couls anybody please tell regarding this.

Kind Regards,

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    There are a family of built-in functions typically used for digitizing points - these can also rubber-band the points being entered. These functions all begin with "enter" and the available functions are:

    enterArc, enterBox, enterCircle, enterDonut, enterEllipse, enterLine,
    enterMultiRep, enterNumber, enterPath, enterPoint, enterPoints,
    enterPolygon, enterScreenBox, enterSegment, enterString

    They're documented functions.

    Anyway, these have various callbacks which get triggered upon various events (e.g. when you add a point, when you delete a point, when you're done). In the case of the doneProc, it's called with three arguments, the windowId, whether it was "done", and the list of points. Since I don't care about the second two arguments (and I'm not using them in the callback), I used the convention of prefixing them with underscore. The reason for doing this is so that when I run SKILL Lint on the code, it doesn't mark me down for having arguments to my function which aren't used. Apart from that, it doesn't matter - the arguments have to be there, but just don't get used in my code.

    In your other post, it might be a matter of using one of these, or it might just be that you build a form and interact with the user that way.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    There are a family of built-in functions typically used for digitizing points - these can also rubber-band the points being entered. These functions all begin with "enter" and the available functions are:

    enterArc, enterBox, enterCircle, enterDonut, enterEllipse, enterLine,
    enterMultiRep, enterNumber, enterPath, enterPoint, enterPoints,
    enterPolygon, enterScreenBox, enterSegment, enterString

    They're documented functions.

    Anyway, these have various callbacks which get triggered upon various events (e.g. when you add a point, when you delete a point, when you're done). In the case of the doneProc, it's called with three arguments, the windowId, whether it was "done", and the list of points. Since I don't care about the second two arguments (and I'm not using them in the callback), I used the convention of prefixing them with underscore. The reason for doing this is so that when I run SKILL Lint on the code, it doesn't mark me down for having arguments to my function which aren't used. Apart from that, it doesn't matter - the arguments have to be there, but just don't get used in my code.

    In your other post, it might be a matter of using one of these, or it might just be that you build a form and interact with the user that way.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information