• 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. save schematic options

Stats

  • Locked Locked
  • Replies 15
  • Subscribers 125
  • Views 11441
  • 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

save schematic options

StreamCX
StreamCX over 15 years ago

I set some schematics option like net names to derived.

When I exit Virtuoso that does not saves.

How can I save schematic options for long time? 

  • Cancel
  • Quek
    Quek over 15 years ago

    Hi StreamCX

    Please add the following line to your .cdsinit file:

    envSetVal("schematic" "netNameMethod" 'cyclic "derived")

    After you have modified the settings, go to "ciw:Options->Save defaults" and save them in a file. You can then check the names of the settings from that file.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StreamCX
    StreamCX over 15 years ago

     Quek

    Thanks, but when I write this in .cdsinit, I do not need to save defaults in CIW.

    How make that without wtiting code in CIW?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 15 years ago

    Hi StreamCX

    I don't quite understand your question. So let me make a guess. You do not need to have the setting in both .cdsinit and .cdsenv file. You just need to have the "envSetVal(...)" line in your .cdsinit file and it will be ok. There is no need to write any codes in ciw. Just add the line to your .cdsinit file. It is an initialization file that can be in your working directory or home directory. If it currently does not exists, simply create a text file named ".cdsinit" and add in the line.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StreamCX
    StreamCX over 15 years ago

    Quek

    I know that adding code to .cdsinit works. I did this.

    But how do this without writing code? Writing code is hard, because I also need to write more than 1 param. 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    If in the CIW you use Options->Save Defaults, and save into the .cdsenv in your home directory, it should save settings performed interactively, without needing to write any code.

    This should then get picked up automatically on the next session, unless you either have code in your .cdsinit to overwrite it, or have set your environment not to read the .cdsenv from the home directory.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StreamCX
    StreamCX over 15 years ago

    If in the CIW you use Options->Save Defaults, and save into the .cdsenv in your home directory, it should save settings performed interactively, without needing to write any code.

    I do, That does not work.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 15 years ago

    Hi StreamCX

    Would you please provide the output of the following?

    terminal>env | grep CDS

    Thanks
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StreamCX
    StreamCX over 15 years ago

    Quek 

    Output: 

    [user@blabla ~]$ env | grep CDS
    CDS_Netlisting_Mode=Analog

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 15 years ago

    Hi StreamCX

    Please add the following line to your cshrc file. It will load the .cdsenv file in your working directory.

    setenv CDS_LOAD_ENV addCWD

    This should solve the problem.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StreamCX
    StreamCX over 15 years ago

     Quek

    That does not work. 

    // All my path environments in .bashrc file, no csh.

    I write  export CDS_LOAD_ENV addCWD

    • 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