Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14166
  • 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

Memory only scratch view

theopaone

Has a memory only scratch view ever been implemented in Virtuoso or do we still have to have a writable library to create one?

Previous post from about 6 years ago

http://community.cadence.com/cadence_technology_forums/f/48/t/14177

Ted

Parents

  • Thanks, Andrew

    I was trying not to have to create a new temporary scratch library as the design library may not be writable.

    I want to represent nested shapes found with dbGetTrueOverlaps as top level shapes but not put them in the current cellView where they would have to be deleted after they have served their purpose.

    There seems to be a way to create an extension to a library in the cds.lib which uses the assign keyword:

    ASSIGN <libName> TMP </tempDirectory>

    The documentation says that this can be used by applications for derived data such as derived cellViews. How does one create a cellView which is guaranteed to be be in this temp directory which would be writable?

    Thanks

    Ted

Reply

  • Thanks, Andrew

    I was trying not to have to create a new temporary scratch library as the design library may not be writable.

    I want to represent nested shapes found with dbGetTrueOverlaps as top level shapes but not put them in the current cellView where they would have to be deleted after they have served their purpose.

    There seems to be a way to create an extension to a library in the cds.lib which uses the assign keyword:

    ASSIGN <libName> TMP </tempDirectory>

    The documentation says that this can be used by applications for derived data such as derived cellViews. How does one create a cellView which is guaranteed to be be in this temp directory which would be writable?

    Thanks

    Ted

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.