• 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. PCB Design
  3. scirpt to calculate area info

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 165
  • Views 12884
  • Members are here 0
More Content
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

scirpt to calculate area info

yogeshyogesh
yogeshyogesh over 16 years ago

Hello Everybody,

I have written a simple script to calculate (physical) area information using "extracta" command. I use SYM_EXTENTS_X1, SYM_EXTENTS_Y1, SYM_EXTENTS_X2, SYM_EXTENTS_Y2 variables. I am able to calculate area the scirpt is ok. BUT, the problem is that the area is sometimes too big (5-6 times) than the actual footprint and sometimes it is too small. I am wondering what is going wrong? any inputs ... please help.

I dont know how the extracta tool works, which layers it looks at for this info? if the footprint was created using mm (as units) and the layout is in mils, will that cause any difference? if the ref designator text of the component is way bigger than the body can this affect the cordinates I am extracting? these are vaious doubts that I have in my mind currently. Please help me to clear this clutter in my head. 

Thank you.

  • Cancel
  • redwire
    redwire over 16 years ago

     Hmmm....good question.  I actually haven't used extracta in my own post-processing but have done SKILL.  I assume the results are going to be the same.

     Can you post an example of what the extracta output looks like?  It should not matter that the symbol was built in one unit and is being used in another.

     

    Also, post your question over in the SKILL forum and you might get an answer.

    Bill

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • yogeshyogesh
    yogeshyogesh over 16 years ago

    Hello Redwire,

    Thank you for extending help to me. I guess I have figured out the problem. Instead of using SYM_EXTEND_X1 variables I used SYM_BOX_X1 variables in the view file and I am back on track, I guess.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

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