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

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
Parents

  • I'd certainly agree with all of the above. But I wanted to add one more thought.
    I believe that when you talk about "the data", you have to consider what that really means.
    Things move so fast and process are more complex than ever. Where I see people spending
    effort is not just in getting a configuration of data, but rather in determining how they got to that state.
    You have to have a way to store both the data and some of the key driving knowledge, such as intent.
    Otherwise, you may never know why some changes were made, by whom and when. Sure, your circuit designer and layout designer can ping-pong changes back and forth, but it's the additional layer of knowledge that makes that collaboration more valuable. And that gets magnified over time (how long do you need to keep old designs around?) and complexity.

    Just something to think about.
    Rick


    Originally posted in cdnusers.org by rkstanton
Reply

  • I'd certainly agree with all of the above. But I wanted to add one more thought.
    I believe that when you talk about "the data", you have to consider what that really means.
    Things move so fast and process are more complex than ever. Where I see people spending
    effort is not just in getting a configuration of data, but rather in determining how they got to that state.
    You have to have a way to store both the data and some of the key driving knowledge, such as intent.
    Otherwise, you may never know why some changes were made, by whom and when. Sure, your circuit designer and layout designer can ping-pong changes back and forth, but it's the additional layer of knowledge that makes that collaboration more valuable. And that gets magnified over time (how long do you need to keep old designs around?) and complexity.

    Just something to think about.
    Rick


    Originally posted in cdnusers.org by rkstanton
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.