• 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 SKILL
  3. Most efficient db function to move all shapes in a design...

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 143
  • Views 19000
  • 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

Most efficient db function to move all shapes in a design?

jaleco
jaleco over 8 years ago

Working in ic5141, what is the most efficient way to move all shapes in a design using the db functions?

I'm dealing with millions of shapes and would like to use a function like Move Origin, but this is not a db function.

Is it more efficient to create a figure group, add each shape to the group and move the group, or to select and move each shape?

Neither seem like good options for a list of millions of shapes.

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

    There really should be no significant difference between nograph and normal graphical mode (other than any delay caused by the X server actually having to draw and display the shapes). When you run -nograph mode, Virtuoso (icfb) starts (in IC5141) a null X server (Xndx) which is used as the display for the session. This means it still does all the graphical operations (if you're calling it in a graphical mode) - it's just that the X traffic goes to this null display instead.

    However, running dbOpenCellViewByType and leMakeCell should not generate any graphical output - I don't believe there are any dialog boxes raised by leMakeCell - it outputs warnings, but no dialog boxes (dialog boxes can be a problem for no graph sessions because you can't see them and so obviously can't click on them).

    I see no benefit in trying to automate the UI this way, because all that happens is that the graphical version of the command, leHiMakeCell, collects data from the selected objects (obviously you can't do selection unless there's a window of some sort, which you can do in nograph, but just can't see), the options from the form, and then calls leMakeCell. So if you call leMakeCell with the same arguments that are called from the UI, it should have the same behaviour without all that tedious mucking about with forms.

    The problem you almost certainly have is that the code that launches the form will block and so it doesn't get to the next line; you typically have to workaround this using hiRegTimer (or hiEnqueueCmd in later versions), but as I said, this is an unnecessarily complication. I'd try to figure out what's different in the settings you're passing to leMakeCell from those when you use the form.

    This might be easier solved by talking to somebody in customer support who can take a look at precisely what you're doing.

    Regards,

    Andrew.

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

    There really should be no significant difference between nograph and normal graphical mode (other than any delay caused by the X server actually having to draw and display the shapes). When you run -nograph mode, Virtuoso (icfb) starts (in IC5141) a null X server (Xndx) which is used as the display for the session. This means it still does all the graphical operations (if you're calling it in a graphical mode) - it's just that the X traffic goes to this null display instead.

    However, running dbOpenCellViewByType and leMakeCell should not generate any graphical output - I don't believe there are any dialog boxes raised by leMakeCell - it outputs warnings, but no dialog boxes (dialog boxes can be a problem for no graph sessions because you can't see them and so obviously can't click on them).

    I see no benefit in trying to automate the UI this way, because all that happens is that the graphical version of the command, leHiMakeCell, collects data from the selected objects (obviously you can't do selection unless there's a window of some sort, which you can do in nograph, but just can't see), the options from the form, and then calls leMakeCell. So if you call leMakeCell with the same arguments that are called from the UI, it should have the same behaviour without all that tedious mucking about with forms.

    The problem you almost certainly have is that the code that launches the form will block and so it doesn't get to the next line; you typically have to workaround this using hiRegTimer (or hiEnqueueCmd in later versions), but as I said, this is an unnecessarily complication. I'd try to figure out what's different in the settings you're passing to leMakeCell from those when you use the form.

    This might be easier solved by talking to somebody in customer support who can take a look at precisely what you're doing.

    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