• 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. pnoise_pmjitter missing when running sweeps

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 14680
  • 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

pnoise_pmjitter missing when running sweeps

Martin Cochet
Martin Cochet over 5 years ago

Hello,

I am trying to run a pnoise jitter simulation in ADE Explorer (in Virtuoso ICADV12.3-64b) and I am encountering an issue when sweeping across corners.

When I run a single point I am able to get the desired waveform using the expression drplJitter(?result "pnoise_pmjitter" ?unit "Second" ?k 1 ?event 0)

However as soon as I try to run a sweep or corners simulation I get the following error

expression evaluation failed: drplJitter(?result "pnoise_pmjitter" ?unit "Second" ?k 1 ?event 0)
ERROR (WIA-1175): Cannot plot waveform signals because no waveform data is available for plotting.
One of the possible reasons can be that 'Save' check box for these signals are not selected in the Outputs Setup pane. Ensure that these check boxes are selected before you run the simulation

I was able to narrow down the issue to the saved results:

in single point mode, after opening the results with openResulrs("path/to/psf") results() returns:

(pss_td pss_fd pnoise_pmjitter variables)

When I do a sweep results() returns

(pss_td pss_fd pnoise pnoise_sb variables)

with no pnoise_pmjitter result. [The only difference between the 2 is if I do a single point vs 2 corners, nothing else changed]

I could not find any save option parameter that could be ticked to have pnoise_pmjitter saved as part of the results when running sweeps/corners.

Does anyone have an idea how to fix this?

Thanks in advance,

Martin

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Martin,

    Please give the exact IC version you're using (Help->About will give the full subversion number), plus the Spectre subversion (this will be at the top of the spectre log file). The reason I'm asking is that handling of Jitter analysis changed during that time frame and I want to ensure I both test the problem and give the right advice based on the sub-versions you're using.

    Thanks,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Martin Cochet
    Martin Cochet over 5 years ago in reply to Andrew Beckett

    Hi Andrew, thanks for the quick reply, here are the specific versions:

    For Virtuoso: ICADV12.3-64b.500.23

    For Spectre: Version 17.1.0.627.isr15_s02 64bit -- 10 Jun 2019

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Martin Cochet
    Martin Cochet over 5 years ago in reply to Andrew Beckett

    Hi Andrew, thanks for the quick reply, here are the specific versions:

    For Virtuoso: ICADV12.3-64b.500.23

    For Spectre: Version 17.1.0.627.isr15_s02 64bit -- 10 Jun 2019

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Martin Cochet
    Martin Cochet over 5 years ago in reply to Martin Cochet

    Hi Andrew, as I'm sure you have a lot a lot on your plate, I will post directly a support ticket regarding this issue.

      I will post the answer from support on this post too for reference if someone else runs into the same problem in the future.

    Best,
    Martin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to Martin Cochet

    Dear Martin,

    I was just wondering...in case this lends any insight into the issue...

    If you open the results for each individual simulation (as opposed to the ensemble of the two iterations) and issue the command results(), are the "pnoise_pmjitter" results present in each? In other words, is this possibly an issue with the ensemble result or is the result missing from a specific simulation within the set of 2 corner simulations.

    No need to respond if you are busy or my comment is not relevant in your opinion...

    Shawn

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

    Martin,

    I took a quick look (sorry, was busy the last few days to actually try it). It appears you have old expressions from before the new "sampled(jitter)" mode, and the results database now typically has these names:

    (pss_tran pss_td pss_fd pnoise_sample_pm0 model
      instance output designParamVals primitives subckts
      variables
    )

    I see that with both single runs and corner sweeps - it looks like you have (somehow) the old PM jitter analysis rather than the revamped jitter mode. Not sure why? The direct plot form generates different expressions now:

    rfJitter(?result "pnoise_sample_pm0" ?unit "Second" ?from 10 ?to 100000000 ?signalLevel "rms")
    rfJc(?result "pnoise_sample_pm0" ?unit "Second" ?from 10 ?to 100000000 ?k 1 ?multiplier 1)
    rfJcc(?result "pnoise_sample_pm0" ?unit "Second" ?from 10 ?to 100000000 ?k 1 ?multiplier 1)

    Probably best that you do indeed follow up with your support case as then we can see what's going on with your data. I wonder if it's related to a compatibility mode with the ADE setup having been created initially with an older version.

    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