• 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. Digital Implementation
  3. Doubt regarding SDF

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 92
  • Views 15361
  • 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

Doubt regarding SDF

selvam27
selvam27 over 13 years ago

What is the difference between writing sdf from encounter and from ETS?

  I had written sdf(write_sdf) from encounter after postRoute and also write sdf(write_sdf) in ETS using spef generated by encounter.

I have doubt that

What is the difference between writing sdf from encounter and from ETS? 

  • Cancel
Parents
  • kienu
    kienu over 12 years ago

     Hi Kari,

    What i actually wanted to ask is, I wrote out  SDF and SPEF using the encounter tool for a routed design. I then invoked this same SPEF in ETS, performed the SPEF flow and wrote out another SDF in ETS. I compared the SDF written from EDI and ETS and found no difference, but according to my understanding the Parastic data inclusion should have made some delay difference. Shouldn't there have been a difference in the two SDF's?


     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • kienu
    kienu over 12 years ago

     Hi Kari,

    What i actually wanted to ask is, I wrote out  SDF and SPEF using the encounter tool for a routed design. I then invoked this same SPEF in ETS, performed the SPEF flow and wrote out another SDF in ETS. I compared the SDF written from EDI and ETS and found no difference, but according to my understanding the Parastic data inclusion should have made some delay difference. Shouldn't there have been a difference in the two SDF's?


     

    • 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