Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 13824
  • 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

hierarchial summary

deep242003

I want to derive hirerchial summary of a layout(instance names and mosaics. dbGetTrueOverlaps() gives the data in form of layers(please correct if I am missing anything).

while dbProduceOverlapIns() has no hierarchial option .

 

Any suggestion or hint willl be of great help.

 

  • Are you trying to find the instances in a particular region of the layout, or in the complete layout? It just seemed a slightly odd requirement to find all the hierarchical instances in just a portion of the layout, so thought I'd better ask you to clarify.

    Andrew
  • i need for the whole layout.. even if i can make for small area,i can use ~>bBox to aply for whole layout. i m looking sth similar to lehisummary() but needs hierarchial dta rather than only current layout.

  • Using a region query is kind of overkill in that case. You could just write a recursive function to do this - there have been many examples of similar things on this forum before. Since you want instance information, something like:

    procedure(MyUntestedLayoutInfo(@optional (cv geGetEditCellView()) (depth 0))
      let((format)
        foreach(inst cv~>instances
          sprintf(format "%%%ds%%s %%s\n" depth)
          printf(format "" inst~>name inst~>cellName)
          MyUntestedLayoutInfo(inst~>master depth+1)
        )
        t
      )
    )

    Needs a bit of work to handle mosaics (and as the function name suggests, I wrote this off the top of my head and didn't test it)

    Hope that helps,

    Regards,

    Andrew.

  • Hello Andrew,

     I'm curious, how to save the hierarchical summary file into certain directory?

    Thanks,

    Nony

  • You'd need to use fprintf() instead of printf() in the code, and pass in an open file handle (as produced by outfile()).

    Andrew.

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.