Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 5460
  • 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

What are the possible ways of exporting layout to a text file and importing it back while retaining layout and pcell properties

MFahmy

Hi, 

I wanted to ask what are the different possible ways of exporting the layout to a text file and then importing it back while retaining the layout instances properties and the pcells

I came across "dbWriteSkill" but I am not sure what is meant by t_release -> The release in which the file will be loaded

then there is also "dbDumpPcDefinePcell" and "pcSkillGen" I am not sure what is the difference compared to the dbWriteSkill and which one to use 

I need this to modify export and compare layouts from different PDKs and then modify them accordingly, I have considered using skill directly to do the comparisons and the modifications but there are multiple limitations blocking this approach 

virtuoso version ICADVM20.1-64b

sub-version ICADVM20.1-64b.500.28.EHF13629

Thanks, 

Fahmy 

Parents

  • Fahmy,

    Using dbWriteSkill is mostly for debug purposes and it not guaranteed to be complete (it was used in the past to be able to go back to an older version, but it doesn’t support all data stored in the database and so can be lossy and should not be used for any round trip - I think the documentation makes this clear). Comparison would also be hard because the database ids are unique to the session and that would make it very hard to compare the (potentially incomplete) data.

    Comparing layout data is often best done using XOR (PVS and Pegasus have a FastXOR) that makes this easy - although that is then just comparing physical data rather than any logical info in the database.

    There isn’t a text format supported that is complete and survives round trip fully. Changing the database this way would absolutely not be the recommended approach; instead you’d be better off using an appropriate SKILL API to change the database as you need (I’ve no idea what kind of changes you want to make though).

    Andrew

Reply

  • Fahmy,

    Using dbWriteSkill is mostly for debug purposes and it not guaranteed to be complete (it was used in the past to be able to go back to an older version, but it doesn’t support all data stored in the database and so can be lossy and should not be used for any round trip - I think the documentation makes this clear). Comparison would also be hard because the database ids are unique to the session and that would make it very hard to compare the (potentially incomplete) data.

    Comparing layout data is often best done using XOR (PVS and Pegasus have a FastXOR) that makes this easy - although that is then just comparing physical data rather than any logical info in the database.

    There isn’t a text format supported that is complete and survives round trip fully. Changing the database this way would absolutely not be the recommended approach; instead you’d be better off using an appropriate SKILL API to change the database as you need (I’ve no idea what kind of changes you want to make though).

    Andrew

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.