Stats

  • Locked Locked
  • Replies 5
  • Subscribers 90
  • Views 15948
  • 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

About GCELLGRID and TRACK Statement in DEF

archive

How are the parameters for following statements used in DEF file calculated GCELLGRID TRACK For example, in a DEF file, statements appear as: TRACKS Y 500 DO 146 STEP 1000 LAYER metal1 ; GCELLGRID Y -50 DO 2 STEP 9950 ; GCELLGRID X 173250 DO 1 STEP 7450 ; How are the parameters for these statements calculated. GCELLGRID and TRACK are two of the statements which are used to define the floorplan for a particular design. But, how are the values for these statements calculated? Thanks.


Originally posted in cdnusers.org by johariph
Parents

  • I think half-track offset is the default. No setting required. Did you get the DEF TRACKS section from somewhere, or did you let FE create this?

    Also, I'm not aware of the GCELLGRID having any impact on placement, at least not directly. It affects routing, but if trialRoute uses it, and placement looks at trialroute results, then I suppose it could indirectly affect placement. I'm not sure about this though.

    I think the real question is, what are you trying to achieve in your placement? :-)

    - Kari


    Originally posted in cdnusers.org by Kari
Reply

  • I think half-track offset is the default. No setting required. Did you get the DEF TRACKS section from somewhere, or did you let FE create this?

    Also, I'm not aware of the GCELLGRID having any impact on placement, at least not directly. It affects routing, but if trialRoute uses it, and placement looks at trialroute results, then I suppose it could indirectly affect placement. I'm not sure about this though.

    I think the real question is, what are you trying to achieve in your placement? :-)

    - Kari


    Originally posted in cdnusers.org by Kari
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.