Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 13971
  • 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

Multi-part path makes cadence hang?

stuso

 Hi there,

i'm finding that my otherwise ok cadence session is fine UNTIL i draw or re-shape a multi-part path. This multpart path is for a guard ring so i suppose it may be relatively complex in that it does have around 4 sub paths and subtectangles for x5 rows of contacts.

I was wondering if this is a known issue. I have known multi-part paths to casue me issues in various versions of cadence in the past, in that cadence would completely stall and not come back. Howeve in this case it does come back alive after 5mins or so.

My current cadence version is: IC5141_ISR200806270515

Thanks

Stu 

 

 

 

Parents

  • We have seen problems with Multi-part paths (MPPs) with lots of contacts. The larger we make this path, the more contacts the MPP has to maintain, the slower things ran in our session. We finally ended up writing some wrapper code for flattening MPPs. We determined that ultimately we wanted our symbolic contacts placed instead of the sub-rectangles of an MPP, so when we flatten the MPP, we replace the rectangles with symbolic instances. We then decided that since our flatten code does this automatically, we modified our large MPPs to no longer have sub-rectangles in them. We use a temp layer and draw it as a sub path in the MPP. We can still stretch and chop the MPP as usual. When we flatten the MPP later on, we convert the temp layer to contact instances. Stretching and reshaping an MPP with 8 to 10 sub-paths is much more efficient than dealing with thousands of sub-rectangles. In general, we found that all of Cadences ROD objects add a performance hit (we used to use a lot of these in our pcells). The ROD objects are useful, but sometimes you have to use them sparingly so you can take advantage of the features only when it is needed.

     -Derek

Reply

  • We have seen problems with Multi-part paths (MPPs) with lots of contacts. The larger we make this path, the more contacts the MPP has to maintain, the slower things ran in our session. We finally ended up writing some wrapper code for flattening MPPs. We determined that ultimately we wanted our symbolic contacts placed instead of the sub-rectangles of an MPP, so when we flatten the MPP, we replace the rectangles with symbolic instances. We then decided that since our flatten code does this automatically, we modified our large MPPs to no longer have sub-rectangles in them. We use a temp layer and draw it as a sub path in the MPP. We can still stretch and chop the MPP as usual. When we flatten the MPP later on, we convert the temp layer to contact instances. Stretching and reshaping an MPP with 8 to 10 sub-paths is much more efficient than dealing with thousands of sub-rectangles. In general, we found that all of Cadences ROD objects add a performance hit (we used to use a lot of these in our pcells). The ROD objects are useful, but sometimes you have to use them sparingly so you can take advantage of the features only when it is needed.

     -Derek

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.