• 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. ViVa: Modifying Various Graph Properties

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 9233
  • 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

ViVa: Modifying Various Graph Properties

sgcad
sgcad over 2 years ago

I'd like to modify several ViVa (IC6.1.8-64b.500.29) settings related to the appearance of graphs:

  1. Is there a way to remove the number that appears on the top right of every graph ("1" in the attached PDF sample graph)? This number is, in most cases, useless and just clutters things up.
  2. Is there a way to change the default "Marker Significant Digits" setting from "auto" to "manual" with 3 significant digits?
  3. Legends and marker areas are transparent such that the grid is visible (see attached PDF sample graph). I'd find the graph less busy and thus easier to read if those areas were solid white, hiding the grid. Is there a way to achieve this?
  4. When choosing "Legend Position" as "Inside", the legend always appears on the top right. In many cases, however, it would be beneficial to choose another location, for example top left. Is there a way to change this?

Thanks very much for your input on these topics.

ViVa_sample_graph.pdf

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago
    1. I am not aware of a way of hiding the subwindow number.
    2. These are example settings for point markers. There are equivalent settings for various types of marker:
      envSetVal("viva.pointMarker" "sigDigitsMode" 'string "Manual")
      envSetVal("viva.pointMarker" "significantDigits" 'string "3")
      Other types of marker would be: horizMarker,referenceLineMarker,vertMarker,pointMarker,refPointMarker,multiDeltaMarker,refLevelMarker,regionExtentMarker,riseFallEdgeMarker,delayMarker
      so use that as the word after viva to change the other marker types.
    3. This is not possible currently as far as I can tell; you should contact customer support to request an enhancement (I found some requests that seemed to be asking for something similar, but nothing that concrete)
    4. This is also not possible currently; I would say that "inside" doesn't get used that commonly in my experience, but nevertheless this is worth asking for via custom support.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sgcad
    sgcad over 2 years ago in reply to Andrew Beckett

    Thanks very much, 2. working fine.

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

    Closely related to the above: I've noticed that when I'm exporting a graph with a legend positioned 'inside', it sometimes is collapsed to a text saying '3 more...' after exporting to PDF ('Resize Image(s)' deactivated, I didn't yet experiment with other formats as PDF is what I'd like to use).

    That's how it looks like directly in ViVa:

    And here what it looks like after export:


    Any ideas how to fix this without touching the font? The legend font is set as follows in my .cdsinit:

    envSetVal("viva.traceLegend" "font" 'string "DejaVu Sans,10,-1,5,75,0,0,0,0,0")
    envSetVal("viva.traceLegend" "printSaveImageFont" 'string "DejaVu Sans,10,-1,5,75,0,0,0,0,0")

    Thanks very much.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to sgcad
    sgcad said:
    Closely related to the above: I've noticed that when I'm exporting a graph with a legend positioned 'inside', it sometimes is collapsed to a text saying '3 more...' after exporting to PDF ('Resize Image(s)' deactivated, I didn't yet experiment with other formats as PDF is what I'd like to use).

    I suspect this is related to the issue in this post. Unfortunately the workaround of "Render exactly as on screen" won't help if you're outputting to PDF, unfortunately. It proved a little tricky to reproduce - I could reproduce it but a colleague in R&D couldn't - however, it's font-related in some way.

    There isn't really a workaround if you are producing PDF (that I know of) - so it would be best if you contact customer support and ask for a duplicate of CCR 2617845 to be filed to increase the priority of getting this fixed.

    Regards,

    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