• 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. How do you deal with generated data

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 124
  • Views 15267
  • 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

How do you deal with generated data

archive
archive over 18 years ago

Hi there,

We are currently having a discussion, where we try to decide, what data we should manage.
For sure any primary data e.g hand-edited-schematics, or RTL code should be managed.

What do you do with generated data, e.g. a verilog netlist or an extraced cellview.
That generates dependencies between different views of the same object that one should track....

I am wondering, what the best approach is.
Does anyone have a suggestion or best practice advice?

Thanks,

Nena


Originally posted in cdnusers.org by Nena
  • Cancel
Parents
  • archive
    archive over 18 years ago

    As disk has gotten less expensive, I have seen the trend to save more generated data. If the DM system in use can help ensure all the source data is aligned with the generated data, this can save a lot of time when unwinding changes to find the last time something worked.

    Chris Goldstein


    Originally posted in cdnusers.org by chrisg
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    As disk has gotten less expensive, I have seen the trend to save more generated data. If the DM system in use can help ensure all the source data is aligned with the generated data, this can save a lot of time when unwinding changes to find the last time something worked.

    Chris Goldstein


    Originally posted in cdnusers.org by chrisg
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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