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

  • Here're my 2 cents.

    There's probably no right or wrong answer here. What you choose to DM depends a lot on your flow, and that's a function of how the tools in your flow behave. If your flow insists that netlists be generated every time right before they are used, DM the netlist might actually cause problems (think of AMS's netlists in cellviews and TMPDIR usage). On the other hand, not DM'ing netlists can leave you in a situation where the more recently generated netlists do not match an older version of schematic you just checked out, and if the tools in your flow just check for time stamp, you can very well be working on netlists which don't match your design.

    DM and archiving are related, but are really different. As our moderators said in their interviews, DM is so important for multi-site designs. If you look at DM as something that is active and current, versus archiving which is static, you will consider the management of secondary or generated files as important. The fact that you can generate these secondary files does not mean that your flow will always generate them as needed.

    Best regards,
    Teng-Kiat Lee
    Product Engineering, Central Architecture and Technology


    Originally posted in cdnusers.org by tklee@cadence.com
Reply

  • Here're my 2 cents.

    There's probably no right or wrong answer here. What you choose to DM depends a lot on your flow, and that's a function of how the tools in your flow behave. If your flow insists that netlists be generated every time right before they are used, DM the netlist might actually cause problems (think of AMS's netlists in cellviews and TMPDIR usage). On the other hand, not DM'ing netlists can leave you in a situation where the more recently generated netlists do not match an older version of schematic you just checked out, and if the tools in your flow just check for time stamp, you can very well be working on netlists which don't match your design.

    DM and archiving are related, but are really different. As our moderators said in their interviews, DM is so important for multi-site designs. If you look at DM as something that is active and current, versus archiving which is static, you will consider the management of secondary or generated files as important. The fact that you can generate these secondary files does not mean that your flow will always generate them as needed.

    Best regards,
    Teng-Kiat Lee
    Product Engineering, Central Architecture and Technology


    Originally posted in cdnusers.org by tklee@cadence.com
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.