Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 14458
  • 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

leSearchHierarchy() layers origin problem

Sarvani

 Hi all,

 1) I have used m1=leSearchHierarchy( cv cv~>bBox 32 "any shape" list(list("layer" "==" list("M1" "drawing")))) to get all M1 layers (from hirerchy also). But when I enter dbLayerSize(cv list("y2" "drawing")  m1 0.2) in CIW then Y2 layer is placed at different points from original m1 layers(getting mismatch for hirerchy m1 layers only). Please let me know how can I overcame this.

2) And  is there any command which is faster than leSearchHierarchy.

 

Thank you,

Sarvani

 

Parents
  •  I think the problem is leSearchHierarchy does not give the hierarchy path of the shape. Try using:
    dbShapeQuery(

    d_cellviewId
    l_layerPurposePair
    l_bBox
    [ x_startLevel ]
    [ x_stopLevel ]
    [ n_filterSize ]
    [ l_transform ]

     

    Another good function to use is but you have to flatten the list output:

    dbGetTrueOverlaps(
    d_cellView
    l_bBox
    [ l_layerPurposePair ]
    [ lx_level ]
    [ g_doRowCol ]
    )

     

    As far as speed, anytime you are creating polygons it is going to take time. Thing I have noticed that slow down a script: print outs as the scripts is running and doing a dbSave in a loop really slows the script down.
Reply
  •  I think the problem is leSearchHierarchy does not give the hierarchy path of the shape. Try using:
    dbShapeQuery(

    d_cellviewId
    l_layerPurposePair
    l_bBox
    [ x_startLevel ]
    [ x_stopLevel ]
    [ n_filterSize ]
    [ l_transform ]

     

    Another good function to use is but you have to flatten the list output:

    dbGetTrueOverlaps(
    d_cellView
    l_bBox
    [ l_layerPurposePair ]
    [ lx_level ]
    [ g_doRowCol ]
    )

     

    As far as speed, anytime you are creating polygons it is going to take time. Thing I have noticed that slow down a script: print outs as the scripts is running and doing a dbSave in a loop really slows the script down.
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.