• 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 SKILL
  3. Color argument in awvPlotWaveform() not working

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 149
  • Views 14795
  • 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

Color argument in awvPlotWaveform() not working

Ivars
Ivars over 11 years ago

Hi,

 I'd like to be able to control the color of the waveforms that I add to a VivaXL plot window but the ?color argument in awvPlotWaveforms doesn't seem to do anything. For example, with the following command, the waveform color simply increments to the next available color instead of being set to the value specified by "y2":

 awvPlotWaveform( awvGetCurrentWindow() list( eyeDiagram(v("/outp") 4e-09 1.49e-08 (2 / 28e9) ?intensityPlot nil) ) ?expr list( "I671:outp" ) ?stripNumber list( 1 ) ?color list("y2") )

 I've also tried using the RGB code  0X00FF50 as given in the manual example. The color option seems to have no effect. Neither does the ?lineThickness option.

 Has anyone had any success in manually setting the waveform colors..

 (The reason I want to do this is for comparing families of curves from multiple jobs -- I want each job to have a different color sequence so that if I make one "child" of the family visible from each job, their colors will be different.)

 I'm using IC6.1.5-64b.500.17

 Thanks.

Ivars

 

  • Cancel
  • Ivars
    Ivars over 11 years ago

    To follow-up on my own question, I contacted Cadence Support regarding this problem. After the support engineer demonstrated the ?color option working for his setup I spent some time investigating why it wouldn't work in my configuration.

    The problem turns out to be ADEXL -- more specifically the hierachy of result directories used by ADEXL.

    If I use openResults() on a specific results directory (I believe called a "design point" in Cadence terminolgy), then the ?color option works.

    However, if I use openResults() with the top level results directory, the ?color option is ignored, even if there is only a single design point. The top-level results directory is considered a "family" of curves, even it the family only contains a single curve. The ?color option doesn't work with "family" results.

    To provide a more concrete example of this, the ?color option will work if I use:

        openResults("/path/to/results/adexl/results/data/Interactive.100/1/testName/psf")

    which opens a single design point result, but not

        openResults("/path/to/results/adexl/results/data/Interactive.100/psf/testName/psf")

    which opens the family of results.

    The whole point of my using the ?color option was to change the color sequence when comparing families of results between two or more  simulation jobs, so this failure is unfortunate.

    I don't really care if I can control the specific colors of the curves within a family, I just want to be able to change the starting index of the color sequence when I plot the same signal from multiple jobs on the same plot. With different color sequence then I can distinguish the curves of the same "child" between multiple jobs. I've asked Cadence Support for help on this.

    Ivars

    • 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