Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13816
  • 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

Consistent Pcell naming scheme for strmout

rotanudad

Hi,

I'm currently on ICADV12.3-64b and I'm looking for a way to generate a gds file such that the instance names for Pcells(or any other cells that do not have unique names) are the same(e.g suffix is a counter which counts up for every instance encountered) each time I strmout  a gds.

So far, I've tried options such as "flatten PCells" and  "flatten Vias" when exporting the gds, but the results of the fastxor run do not seem to match the fastxor run where I select "create gdsii"(let fastxor create the two gds's).

I need this so that I can run fastxor on a list of cells that exist in multiple libraries through the command line.

Thanks.

  • Andrew Beckett

    Not sure you really mean instance names since stream format doesn't normally store instance names. Perhaps you mean the structure (cell) names used for each variant of the pcell that's used?

    You can turn off the timestamp part of the mapped cell name by going to More Options->General and then turning on "Ignore current timestamp". Perhaps that's what you want?

    Andrew.

  • rotanudad
    in reply to Andrew Beckett

    Yes that is what I mean, and thank you for the feedback.

    I've tried your suggestion to disable the timestamp, and the results appear to be more similar, but not the same as the gds's generate from the fastxor gui. 

    When I stream back the generated gds from both the streamout and the fastxor gui, I see that the counter for the pcell variants are different.

    So I guess a better question is how do I have a streamout(strmout) that looks exactly like the gds that the fastxor gui is generating?

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.