• 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. Import some particular shape in to Cadence layout L

Stats

  • Locked Locked
  • Replies 23
  • Subscribers 128
  • Views 21755
  • 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

Import some particular shape in to Cadence layout L

engine2011
engine2011 over 13 years ago

 Hi everyone,

 I want to use standard technology to fabricate a device which is basically a circle shape realized with the toppest level metal layer. Because the process resolution is 0.01um, the smooth brim of circle is not acceptable and will introduce some class a DRC errors. 

 Now I am making the brim of circle replaced by 90 degree polygon to solve these errors. The problem is, if I want to make it a good approximation to a circle, the polygon will be very complex. I can use Matlab to generate this shape without much effort, however, it will be very complex to draw it manually in Cadence. Does cadence have some function to import the shape data from Matlab?

 Thanks!

EF

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

    The problem is that you've changed the code so that it is now not syntactically correct! You've changed the name of the argument to that function to be a literal string - and that's not allowed. Nor is it necessary. The whole point of defining a function with an argument is to allow you to call that function with whatever value you like - you should not have to change the code for each pathname you want to use.

    So, leave the code as it was, and then do:

    abPixMapReadFile("/h/efu01/ibm180/final.XPM")

    Or even just call:

    abXpmToLayout()

    and then use the form to navigate to the file you wish to import. Calling abPixMapReadFile alone will not produce the image - it just parses the pixmap and stores it in some data structures, ready to be drawn later. The function that does the drawing is abPixMapDrawLayout() - but you'll need to see how the various callbacks work to see how the data structures are assembled so that they are ready to be called by abPixMapDrawLayout(). Using the form saves you that bother - it will read the file and then pop up another form to get you to choose which layers you want to be used for which colours in the original pixmap file.

    Regards,

    Andrew.

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

    The problem is that you've changed the code so that it is now not syntactically correct! You've changed the name of the argument to that function to be a literal string - and that's not allowed. Nor is it necessary. The whole point of defining a function with an argument is to allow you to call that function with whatever value you like - you should not have to change the code for each pathname you want to use.

    So, leave the code as it was, and then do:

    abPixMapReadFile("/h/efu01/ibm180/final.XPM")

    Or even just call:

    abXpmToLayout()

    and then use the form to navigate to the file you wish to import. Calling abPixMapReadFile alone will not produce the image - it just parses the pixmap and stores it in some data structures, ready to be drawn later. The function that does the drawing is abPixMapDrawLayout() - but you'll need to see how the various callbacks work to see how the data structures are assembled so that they are ready to be called by abPixMapDrawLayout(). Using the form saves you that bother - it will read the file and then pop up another form to get you to choose which layers you want to be used for which colours in the original pixmap file.

    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