Stats

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

ADE-XL

analogy

Somehow I cannot plot my output in ADE-XL.This is what I see in my CIW :

*WARNING* (reader): illegal character '%' ignored at line 1 of string "..._noise_time:1" ?history %"

*Error* AbstractMethod: Needs to be implemented by the appropriate sub-class

  • What is the expression you're trying to plot?

  • Surprisingly I have disabled all expressions.
  • How can you plot the noise outputs if you've disabled all expressions? Please explain clearly what steps you're doing (and the version you're using) - including what kind of noise analysis setup. Otherwise there is little chance of being able to diagnose this. Or maybe going to customer support would be best. Andrew

  • I figured out where the problem was.

    My ADE-XL state was saved as PSS+PNoise-Accurate=Real-IndefinitePole


    Seems like Spectre (or APS) doesn't like the fact that my ADE-XL state has "+" operator.When I renamed this state to PNoise , it worked without errors.

    Andrew, what are the acceptable characters one can use for State names ?

  • There's not really a thing called an "ADE XL state" - or at least that's ambiguous. So are you referring to:

    1. The name of the ADE XL view?
    2. The name of a Setup State within ADE XL?
    3. The name of a test within ADE XL?

    I think this is a bug, regardless of where it is, because illegal characters should either be disallowed or should be mapped if they cause problems. There is some support by an env var to do mapping of some characters within the ADE XL view itself (this for strange historical reasons is not enabled by default), but that wouldn't help if this is the name of the ADE XL view itself.

    Personally I would stick to alphanumeric characters and underscore, and not begin with a number. That's generally a safe bet with most applications. However, as I said, we should be able to handle this regardless...

    Regards,

    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.