• 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. Automating SOC Encounter Timing Optimization

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13354
  • 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

Automating SOC Encounter Timing Optimization

fieldy
fieldy over 12 years ago

Hi All, I have a couple of questions on running SOC Encounter. My goal is to run the encounter using a tcl script and be able to have a flow that runs through all the necessary steps by running the script, instead of having to use the GUI.

 

1. Does anybody know a good way (or if it is even possible) to automate the timing optimization process in SOC Encounter using tcl script?  Currently, it looks like you have to run optDesign command for setup/hold/DRV optimization and if the violations are not fixed the first time around, you have to run optDesign command multiple times until timing is met. Is there a good way of using the tcl script to do this automatically? For instance is it possible to have encounter run the timing optimizations automatically through tcl scripts until all the timing and DRV violations are fixed?

2. Also, is it possible to have Encounter skip the optimization process if the timing slacks meet the target? The way Encounter works now (for me anyway) is that if I run optDesign command the tool will perform optimization even if the design currently meets all timing/DRV constraints. When running optDesign, is it possible to have Encounter check the timing constraints and skip optDesign process if the constraints are met?

 

Thanks!! 

  • Cancel
  • Kari
    Kari over 12 years ago
    Have you tried the Foundation Flow (under the Flows menu)?
    • 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