• 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 to set default corners in maestro

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 8495
  • 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 to set default corners in maestro

MikeVP
MikeVP over 3 years ago

We have a set of corners defined in a csv file.  How can I set these corners to be the defaults when a new maestro view is created?

I saw this post, but it was not answered.  Have corners' sweep and temperature sweep corners be auto-populated in maestro. - Custom IC SKILL - Cadence Technology Forums - Cadence Community

Thanks!

  • Cancel
Parents
  • MikeVP
    MikeVP over 3 years ago

    Sorry, I should have dug a little more.  

    envSetVal("adexl.gui" "defaultCorners" 'string "<path to file>")

    It doesn't make sense that I have to use adexl, when that tool is deprecated.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • MikeVP
    MikeVP over 3 years ago

    Sorry, I should have dug a little more.  

    envSetVal("adexl.gui" "defaultCorners" 'string "<path to file>")

    It doesn't make sense that I have to use adexl, when that tool is deprecated.  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • ShawnLogan
    ShawnLogan over 2 years ago in reply to MikeVP

    Dear MikeVP,

    MikeVP said:
    It doesn't make sense that I have to use adexl, when that tool is deprecated.  

    I think I can provide some insight on this MikeVP.

    In a case I filed some time ago, I specifically asked why the syntax for a maestro setting was labeled "adexl.XXX". I believe it was with respect to the command envSetVal(“adexl.distribute” “continueICRPRunOnAbruptGUIExit” ‘boolean t).

    The Application Engineer I was working with told me that there are so many customers with significant amounts of SKILL code written using the  "adel.XXX" syntax, it was considered too burdensome to change or retire the "axexl.XXX" syntax and migrate to a "maestro.XXX" syntax.

    Hence, the adexl.XXX syntax remains in spite of the tool's sunset mode classification.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to ShawnLogan

    Shawn is correct. Since a lot of the underlying infrastructure is that from ADE XL, we did not duplicate everything and so many settings which are common to XL and Explorer/Assembler remain with the cdsenv settings being for adexl. It would be riskier to change all those to maestro, and mean that carefully chosen defaults for customers would need updating or replicating. We do however use the maestro tool name in the cdsenv settings for functionality that is only in Explorer/Assembler.

    The perils of treading carefully with legacy setup and behaviour!

    Andrew

    • 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