Stats

  • Replies 2
  • Subscribers 125
  • Views 1311
  • Members are here 0

?suffixNotation input in noiseSummary

leok

Hi,

It's not a big deal, but I would like to have the suffixNotation enabled when I use the noiseSummary function in a script. But I cannot find out what the value should be for turning it "on".
And this is a rare case where even Google has exactly 0 hits Disappointed

The help only tells me to use "nil" which is default and the opposite behavior.

Best Regards,
leo

  • UPDATE:

    It's just a bug. Everything besides nil will set it to print with suffix. But for some reasons it's not working in one assembler testbench, but in the other(s) it does. Maybe it is connected to noise analysis during tran, but I have no time to further dig into it...

    Failing expression (selects noise from corner, two sweeps and time (10u):
    noiseSummary('integrated ?result 'noise ?from 20k ?to 100M ?noiseUnit "V" ?suffixNotation t ?truncateData 10 ?truncateType 'top ?output p_out ?paramValues list("nom" "nom" 4u 60 10u))

    Example for good one (selects noise from one sweep:
    noiseSummary('integrated ?result 'noise ?from 20k ?to 100M ?noiseUnit "V" ?suffixNotation t ?truncateData 10 ?truncateType 'top ?output nil ?paramValues list(5u))

  • in reply to leok
    leok said:
    It's just a bug. Everything besides nil will set it to print with suffix

    That's not a bug. That's how boolean values work in SKILL. nil is false, anything else is true (so t, 1, "hello" are all true). The documentation is misleading because of the t_suffixNotation (which suggests it's text/string) - I've given feedback on the docs to fix that.

    I can't really help with what's wrong in your Assembler setup - I suggest you contact support via http://support.cadence.com (use the case menu to submit a case) so we can investigate and help.

    Andrew 

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.