Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 19970
  • 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 keep some instances un-movable (fixed position) in virtuso

RFStuff

 Dear All,

 I think one definitely would have faced this problem while integratiing many instances/blocks in the top level layout in Virtuso.

The problem I am facing is as follows:-

In the top level of the layout, I have to integrate many instances of layout blocks.

While connecting two blocks ( these two blocks are inside a bigger blocks (like PAD array) or may be crossing over another small block) , some how some  the other blocksare getting moved.

Ideally like to keep the positions of other instances ( let's say A, B, C) fixed, while editing the desired instances ( let's say E,F)  as movable.

I tried in LSW. I dehighlighted the 'inst'. In that process, all the instances are becoming un-movable. Even if you bring a VIA , you can't move it around.

Could anybody please tell what I should do thing smoothly.

Kind Regards,

Parents

  • Given that this code is for the layout editor, it's hardly surprising that nothing is covered in the Cadence Analog Design Environment SKILL Language Reference.

    There are functions from three groups in this code:

    • Cadence SKILL Language Reference (worth reading the User Guide too). The code is written using the SKILL++ lexical scoping capabilities, which provides the ability to create local functions - in this case it's written as a package which exports a number of functions, whilst keeping some functions and some data private.
    • Virtuoso Design Environment SKILL Reference (for the ge (Graphics Editor) and db (Database) functions used in the code)
    • Virtuoso Layout Suite SKILL Reference (this is in fact just for the leRegUserObjectSelectionFilter function)

    The code is written using LISP style (SKILL also allows you to use a C-style which is probably more common, but I tend to write most of my code using LISP style; the language is really a LISP flavour underneath, but it makes no difference to efficiency or speed which style you choose).

    Hope that helps!

    Kind Regards,

    Andrew.

Reply

  • Given that this code is for the layout editor, it's hardly surprising that nothing is covered in the Cadence Analog Design Environment SKILL Language Reference.

    There are functions from three groups in this code:

    • Cadence SKILL Language Reference (worth reading the User Guide too). The code is written using the SKILL++ lexical scoping capabilities, which provides the ability to create local functions - in this case it's written as a package which exports a number of functions, whilst keeping some functions and some data private.
    • Virtuoso Design Environment SKILL Reference (for the ge (Graphics Editor) and db (Database) functions used in the code)
    • Virtuoso Layout Suite SKILL Reference (this is in fact just for the leRegUserObjectSelectionFilter function)

    The code is written using LISP style (SKILL also allows you to use a C-style which is probably more common, but I tend to write most of my code using LISP style; the language is really a LISP flavour underneath, but it makes no difference to efficiency or speed which style you choose).

    Hope that helps!

    Kind 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.