• 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. Print Noise summary and corresponding OCEAN noiseSummar...

Stats

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

Print Noise summary and corresponding OCEAN noiseSummary

AncisMichele
AncisMichele over 3 years ago

Hi,

the print/noise summary function available from ADE-L menu allows for hierarchical grouping of contributors, which is quite an handy feature.

I don't seem to find a programmatic way to obtain the same output within OCEAN's function noiseSummary()

Am I missing some parameter or it is just that the feature is not implemented?

Thanks!

Michele

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to AncisMichele

    Hi Michele,

    The ocnGenNoiseSummary function is essentially a wrapper that calls the noisesummary command under the hood (the SKILL function didn't exist when I replied to the older thread you found). For me it doesn't work properly when I try it with my data too - it's requiring a sweep number and no matter what I pass, it doesn't work. However, as I said, this was a very quick test and I didn't have the time to explore fully what might be going wrong.

    Anyway, you have a way forward. If anyone else has this problem, I'd definitely suggest contacting customer support so that we can improve this (I'm not likely to have the time in the next few days to explore further and debug what might be just a problem with my own test case only).

    Andrew 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • AncisMichele
    AncisMichele over 3 years ago in reply to Andrew Beckett

    Hi Andrew,

    no worries. Not sure I got you right: are you saying you couldn't make noisesummary cmd work with an underlying Jitter simulation (this is the origin of the "sweep number" requirement)?

    I did find a way out, it's just that the sweep number is not as in noiseSummary OCEAN function, where you need to pass the ?sweepValues a list with the actual sweep point.

    What worked for me was to pass "0".

    However, because of the mess this function does with logFiles, I perform a few actions afterwards (essentially moving the results to a sub directory and renaming the noiseSumLogFile)

    This way I can read from the results browser both the original and the noisesummary databases.

    Regards,

    Michele

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to AncisMichele
    AncisMichele said:
    What worked for me was to pass "0".

    I'd tried that too - but it fails with a segmentation fault.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AncisMichele
    AncisMichele over 3 years ago in reply to Andrew Beckett

    I did have the seg fault case too...

    It's been a couple of days I left that approach and tried (failing miserably) to use the other OCEAN functions, I'll make another couple of tests and report back.

    For sure it worked then.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AncisMichele
    AncisMichele over 3 years ago in reply to AncisMichele

    Hello again Andrew,

    just to confirm that on my side the command

    noisesummary . dataset_name 1 0

    where dataset_name is the (rather tricky to spot) name of the Jitter simulation, witht that "0"  at the end, correctly produces a psf.noisesummary database

    I then move the database and its log file to another directory, rename the log, and open it with results browser.

    It's a long way to the top, but we're rockers and accustomed to it ;)

    Regards,

    Michele

    • 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