• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Non-volatile files in Cadence

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 13083
  • 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

Non-volatile files in Cadence

itos
itos over 11 years ago

Hi,

 I want to use Subversion (Revision Control System) with Cadence, in particular for analog design (ADE).

Which files should I check in (i.e., which files contain data and not temporary/volatile stuff) and which are temporary?

For me, there is an "opus" directory and a "simulation" directory.

Do I assume correctly that simulation directory contains only sim results and is hence not to be checked in?

Inside opus, what about the ".cadence" directory? What about the state directories and files? 

Thanks!

PS: I do not want to use any other RCS or "complicated" plugins/interfaces.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Really you should use a proper DM integration rather than trying to manage files yourself. The Cadence database used in the IC tools typically have multiple files per cellView, and these are designed to be "co-managed" - i.e. managed as a single entity rather than individual files being managed. There are a number of different DM integrations from connection partners. In no particular order, there's DesignSync from Dassault MatrixOne, SOS from ClioSoft, IC Manage, MethodICs EDA VersIC and IBM ClearCase. MethodICs VersIC can use subversion as its underlying revision control mechanism.

    In general you would not manage simulation directories or results because these can be recreated  and are thus "derived" data. Normally you'd manage the input data - your schematics, layouts, symbols and ADE setup data (i.e. ADE state cellViews).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information