• 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. default settings for ViVa waveform viewer

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 25574
  • 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

default settings for ViVa waveform viewer

vivkr
vivkr over 13 years ago

Is there any way to change/define default settings for ViVa waveform viewer? I usually start my simulations with a script instead of directly via ADE-L and view the results using the standalone ViVa viewer.

As I typically want to save the plots for embedding in reports, I need to make the traces fatter ("bold") which is very painful if one has to do it by hand for all the curves. 

How can I change this so that the traces are plotted bold by default? I'd also be glad to know what other settings I can modify at ViVa startup.

Thanks,

Vivek

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 11 years ago

     Dear Jeff,

     > Some of the viva settings seem relevant based on names but don't seem to have any effect.

    The number of variables that are actually implemented is limited.To find out which variables are available to set, look in the following file:

    <IC615_install_dir>/tools/dfII/etc/tools/viva/.cdsenv

    The variables that are not commented out have been implemented.

    To modify the variables permanently from your .cdsinit file, I've included a sample of the section of my .cdsinit file:

    ; ViVa default fonts to Clean

    ; Added from Wayne Ingram's note on 7/24/2013
    ;
    ; If customer is setting font related cdsenv variables in .cdsinit (via envSetVal API),
    ; there's a requirement to load the 'viva' context _before_ any envSetVal call is made.
    ; This can be achieved by the following in the .cdsinit file:

    loadContext(strcat(prependInstallPath("etc/context/") "viva.cxt"))
    callInitProc("viva")

    envSetVal("viva.graph" "titleFont" 'string "Clean,12,-1,5,55,0,0,0,0,0")
    envSetVal("viva.axis" "font" 'string "Clean,12,-1,5,50,0,0,0,0,0")
    envSetVal("viva.horizMarker" "font" 'string "Clean,12,-1,5,50,0,0,0,0,0")

    I hope this helps,

    Shawn

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 11 years ago

     Dear Jeff,

     > Some of the viva settings seem relevant based on names but don't seem to have any effect.

    The number of variables that are actually implemented is limited.To find out which variables are available to set, look in the following file:

    <IC615_install_dir>/tools/dfII/etc/tools/viva/.cdsenv

    The variables that are not commented out have been implemented.

    To modify the variables permanently from your .cdsinit file, I've included a sample of the section of my .cdsinit file:

    ; ViVa default fonts to Clean

    ; Added from Wayne Ingram's note on 7/24/2013
    ;
    ; If customer is setting font related cdsenv variables in .cdsinit (via envSetVal API),
    ; there's a requirement to load the 'viva' context _before_ any envSetVal call is made.
    ; This can be achieved by the following in the .cdsinit file:

    loadContext(strcat(prependInstallPath("etc/context/") "viva.cxt"))
    callInitProc("viva")

    envSetVal("viva.graph" "titleFont" 'string "Clean,12,-1,5,55,0,0,0,0,0")
    envSetVal("viva.axis" "font" 'string "Clean,12,-1,5,50,0,0,0,0,0")
    envSetVal("viva.horizMarker" "font" 'string "Clean,12,-1,5,50,0,0,0,0,0")

    I hope this helps,

    Shawn

     

    • 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